Benta
August 24th, 2008, 03:16 AM
Friends,
I have two extra controllers for hard disks on my machine, besides the one that the booting drive is on.
On those I have a couple of drives used for storage of a lot of data that I use across the network with samba.
Those drives have previously been shared drives in samba. I mount them through fstab. This is very convenient and has worked well.
After the upgrade, something has changed in the way ubuntu deals with the drives.
When I boot, the boot process stops at one point late in the process and gives some errors and leaves the stuff below in the log. I have to restart the booting process with ctrl-D, but then it boots OK.
First, I thought that the was a problem with reading the fstab. But I don't think so. Because the drives are listed under the "removable devices" with the correct name (label), and if I click on them, they mount to the place in the files system that is given in fstab.
Interesting is also that the devices no longer show up under dev (as /dev/hdd1 and so on). They are never there.
Does anyone know how I can get rid if these issues?
-------
Log of fsck -C3 -R -A -a
Sun Aug 24 02:34:33 2008
fsck 1.40.8 (13-Mar-2008)
fsck.ext3: No such file or directory while trying to open /dev/hdd1
/dev/hdd1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
fsck died with exit status 8
I have two extra controllers for hard disks on my machine, besides the one that the booting drive is on.
On those I have a couple of drives used for storage of a lot of data that I use across the network with samba.
Those drives have previously been shared drives in samba. I mount them through fstab. This is very convenient and has worked well.
After the upgrade, something has changed in the way ubuntu deals with the drives.
When I boot, the boot process stops at one point late in the process and gives some errors and leaves the stuff below in the log. I have to restart the booting process with ctrl-D, but then it boots OK.
First, I thought that the was a problem with reading the fstab. But I don't think so. Because the drives are listed under the "removable devices" with the correct name (label), and if I click on them, they mount to the place in the files system that is given in fstab.
Interesting is also that the devices no longer show up under dev (as /dev/hdd1 and so on). They are never there.
Does anyone know how I can get rid if these issues?
-------
Log of fsck -C3 -R -A -a
Sun Aug 24 02:34:33 2008
fsck 1.40.8 (13-Mar-2008)
fsck.ext3: No such file or directory while trying to open /dev/hdd1
/dev/hdd1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
fsck died with exit status 8