Dolphin Won't mount partition

[hantechbl]

When I try to go into my lfs partition in dolphin it says: an error occurred while accessing lfs the system responded org.freedesktop.Hal.Device.Volume.PermissionDenied Device /dev/sda8 is listed in /etc/fstab. Refusing to mount. I even reformatted the partition and it still gave me that error. Can somebody help?

[vinnywright]

Re: Dolphin Won't mount partition

first whats lfs ?

second post your fstab file so we can see how it's mounted or if it is.

VINNY

[dibl]

Re: Dolphin Won't mount partition

Device /dev/sda8 is listed in /etc/fstab.

You'll need to post the /etc/fstab file, as well as answer vinny's question.

[hantechbl]

Re: Dolphin Won't mount partition

LFS is the name of the partition and my fstab is attached

[dibl]

Re: Dolphin Won't mount partition

OK, "LFS" is the label, I guess, and ext3 is the filesystem type.

You have some strange mount points scattered around your system -- normally drive partitions are mounted in /media for *buntu. So I would advise to make three new mount points:

sudo mkdir /media/LFS

and

sudo mkdir /media/VFAT

and

sudo mkdir /media/SDA9

Then, in Konsole, rename your present /etc/fstab file:

sudo mv /etc/fstab /etc/fstab_old

Then open kate, in root user mode Alt-F2 kdesudo kate, copy the following new fstab into kate, and then "Save As" in your /etc/ directory as "fstab" with no quote marks.

# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>  <type> <options>    <dump> <pass>
proc      /proc      proc  defaults    0    0
# / was on /dev/sda5 during installation
UUID=38759cc2-69a9-411f-9adb-96d8718af4b9 /     ext3  relatime,errors=remount-ro 0    1
# /dev/LFS was on /dev/sda8 during installation
UUID=cf7679f9-e247-4922-8f80-a5e9826e951f /media/LFS   ext3  auto,users,rw,exec,relatime    0    2
# /shared was on /dev/sda7 during installation
UUID=6B29-8313 /media/VFAT   vfat  utf8,umask=007,gid=46 0    2
# /usr was on /dev/sda9 during installation
UUID=6bfbc181-d9a8-4c34-8320-d9b86ce1fd23 /media/SDA9   ext3  auto,users,rw,exec,relatime    0    2
# swap was on /dev/sda6 during installation
UUID=f1b2f7ff-1f55-4505-a11c-7ecf22515e49 none      swap  sw       0    0
/dev/scd0    /media/cdrom0  udf,iso9660 user,noauto,exec,utf8 0    0
/dev/fd0    /media/floppy0 auto  rw,user,noauto,exec,utf8 0    0

Finally, and assuming you didn't get error messages along the way, in Konsole issue the following to unmount the partitions first:

sudo umount /dev/sda7

sudo umount /dev/sda8

sudo umount /dev/sda9

Then to remount them, issue

sudo mount -a

To verify that they are mounted as planned, issue

sudo mount

and observe the output.

Post back if you get any messages along the way that indicate there are problems.


Errrr -- I just notice you said you reformatted a partition. That will have changed the UUID. You'll need to run

blkid

first and make sure the UUID for each partition in the fstab file that I edited above is a match to the blkid output. If you reformatted LFS, then the UUID won't match, and you'll have to copy/paste it in to the fstab file over top of the one that is there now.

[hantechbl]

Re: Dolphin Won't mount partition

When I tried to mount them the konsole said: [mntent]: warning: no final newline at the end of /etc/fstab and I checked the sda9 uuid with and they matched up
I checked dolphin and i could load those partitions with no problem but is that warning thing mean anyting bad

[dibl]

Re: Dolphin Won't mount partition

Open /etc/fstab with kate in root mode and put a hard return at the end of the file, so the cursor comes down the first empty line below the text, then save it.

[hantechbl]

Re: Dolphin Won't mount partition

When I rebooted the computer the hung with a black screen.... so I reinstalled kubuntu and set the mount points in the /media/ folder during the setup and it works just fine now.