Jump to content
Guest jenney75

cannot access files on sdb1 after system crash

Recommended Posts

Guest jenney75

I was moving files from sdd1 to sdb1 when I had a system freeze and after several minutes when it didn't resolve itself, I had to reboot. I ran a fsck and sdb1 came up clean. Drive shows as mounted and I can get to it in Dolphin only under /mnt/sdb1 , but it shows no files or folders there. However, sdb1 shows it is 96% full which is accurate when I look at it w/ df command. I mounted it at /sdb1 originally and I could manipulate files there before the crash, but not now.

I checked permissions,user set to root w/no write access to Groups or Others. I opened Dolphin as root then attempted to make the changes to allow rw to all users,and changed ownership to myself. Dolphin acts like the change has been made but the permissions revert back when I reopen its properties and look at the permissions again . I would like to use this as my multimedia storage drive with read write access to all. /home is on a separate partition .

I appreciate any advice anyone could give me as I have been googling it since last evening and am stumped. https://mandrivausers.org/style_emoticons/default/wall.gif

 

Below is the output of df and my fstab file, please let me know if any other output is requested

 

df shows

[root@localhost ~]# df

Filesystem Size Used Avail Use% Mounted on

/dev/sda5 18G 547M 17G 4% /

/dev/sda1 1.2G 48M 1.1G 5% /boot

/dev/sda9 54G 14G 40G 25% /home

/dev/sdb1 147G 134G 6.3G 96% /sdb1

/dev/sda7 3.9G 75M 3.6G 3% /tmp

/dev/sda8 200G 3.3G 186G 2% /usr

/dev/sda10 3.4G 236M 3.0G 8% /var

/dev/sdd1 459G 59G 378G 14% /media/disk

 

Here is my fstab

 

# Entry for /dev/sda5 :

UUID=b4b2b7d8-54a2-47f3-9c43-a7b65c09040b / ext3 relatime 1 1

# Entry for /dev/sda1 :

UUID=dea6943c-5e7b-47a4-a8ed-97ed90280179 /boot ext3 relatime 1 2

# Entry for /dev/sda9 :

UUID=04c87d10-2fcf-4b53-ac87-1283e9637c73 /home ext3 relatime 1 2

/dev/cdrom /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0

none /proc proc defaults 0 0

# Entry for /dev/sdb1 :

UUID=63dda21d-eaff-45db-96fb-beab40b36404 /sdb1 ext3 defaults 1 2[/b]

# Entry for /dev/sda7 :

UUID=1fc97a85-cc69-4185-9976-aa8c8d9af7a7 /tmp ext3 relatime 1 2

# Entry for /dev/sda8 :

UUID=8bf183e4-6036-49d6-ae99-cfe0ef79a049 /usr ext3 relatime 1 2

# Entry for /dev/sda10 :

UUID=6bea1224-468b-418b-b2a2-35097c3cd77c /var ext3 relatime 1 2

# Entry for /dev/sda6 :

UUID=b38589cb-aeca-485d-801c-c9d072c24e77 swap swap defaults 0 0

 

I appreciate any advice you could give me as I have been googling it since last evening and am stumped.

Share this post


Link to post
Share on other sites
# Entry for /dev/sdb1 :

UUID=63dda21d-eaff-45db-96fb-beab40b36404 /sdb1 ext3 defaults 1 2[/b]

The only odd thing I see is the [/b] at the end. If it is really there and not a typo, try removing it.

 

Ken

Share this post


Link to post
Share on other sites

Welcome to MUB

My actions would be to attempt to access this drive by using a command line (console) as root. If you can access it you should be able to check the permissions and change them to your requirements. As Ken suggests if the [/b] is not a typo try removing it, although I suspect you missed the at the beginning of the line.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...