Feisty: updates on 3-29-07 royally messed up fstab

[Dane Mutters]

I have a lot of hard drives, including an ATA133 add-in card with 2 HDs, onboard ATA133 with 2 HDs, and one SATA HD. Upon updating all my packages to current (as of 3-29-07 at 9am Pacific), my fstab got really messed-up. Below is my fixed fstab, with the Ubuntu-generated lines commented out, and the correct lines beneath them. One should note that while everything did mount under the Ubuntu-generated configuration, all the drive letters for my SATA and ATA133 add-in card (sda1, etc) were wrong (ie the UUIDs appeared to be wrong).

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hdc1
UUID=5cb9b1f1-af20-40ec-a362-f2bd1e64e8c6 / ext3 defaults,errors=remount-ro 0 1
# /dev/hda1
UUID=63f0e2a3-b520-42d8-943b-94e4b4a381b1 /media/hda1 reiserfs defaults 0 2
# /dev/hda2
UUID=1981f215-6f5b-4d93-9216-55ba82e34427 /media/hda2 reiserfs defaults 0 2
# /dev/hda3
UUID=c9d191a9-54eb-4a49-a60c-f818818acaa0 /media/hda3 reiserfs defaults 0 2
# /dev/sda5
#UUID=88813472-f156-4ee6-b8e9-41540ff07486 /media/sda1 ext2 defaults 0 2
/dev/sda5 /media/sda5 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sdb5
#UUID=438E-1221 /media/sdb5 vfat defaults,utf8,umask=007,gid=46 0 1
/dev/sdb1 /media/sdb1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sdc1
#UUID=9240E4B240E49DEB /media/sdc1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
/dev/sdc1 /media/sdc1 ext2 defaults 0 2
# /dev/hda4
UUID=abfe74bc-4a48-496f-9f15-094d868d41fa none swap sw 0 0
# /dev/hdc2
UUID=0baa44d4-2bdc-4761-960d-5126e9c85217 none swap sw 0 0
/dev/hdb /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

Here is the output of "mount" under the correct configuration:

/dev/hdc1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.20-13-generic/volatile type tmpfs (rw)
/dev/hda1 on /media/hda1 type reiserfs (rw)
/dev/hda2 on /media/hda2 type reiserfs (rw)
/dev/hda3 on /media/hda3 type reiserfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/dev/sda5 on /media/sda5 type vfat (rw,utf8,umask=007,gid=46)
/dev/sdb1 on /media/sdb1 type ntfs (rw,nls=utf8,umask=007,gid=46)
/dev/sdc1 on /media/sdc1 type ext2 (rw)

Here is the output of "df -h" under the correct configuration:

/dev/hdc1 19G 3.9G 14G 22% /
varrun 506M 108K 506M 1% /var/run
varlock 506M 0 506M 0% /var/lock
procbususb 506M 144K 506M 1% /proc/bus/usb
udev 506M 144K 506M 1% /dev
devshm 506M 0 506M 0% /dev/shm
lrm 506M 28M 479M 6% /lib/modules/2.6.20-13-generic/volatile
/dev/hda1 957M 116M 842M 13% /media/hda1
/dev/hda2 120G 36G 84G 30% /media/hda2
/dev/hda3 113G 64G 49G 57% /media/hda3
/dev/sda5 75G 52G 24G 69% /media/sda5
/dev/sdb1 38G 23G 16G 60% /media/sdb1
/dev/sdc1 294G 58G 222G 21% /media/sdc1

...and the incorrect (Ubuntu-generated) configuration:

Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 19G 3.9G 14G 22% /
varrun 506M 108K 506M 1% /var/run
varlock 506M 0 506M 0% /var/lock
procbususb 506M 144K 506M 1% /proc/bus/usb
udev 506M 144K 506M 1% /dev
devshm 506M 0 506M 0% /dev/shm
lrm 506M 28M 479M 6% /lib/modules/2.6.20-13-generic/volatile
/dev/hda1 957M 116M 842M 13% /media/hda1
/dev/hda2 120G 36G 84G 30% /media/hda2
/dev/hda3 113G 64G 49G 57% /media/hda3
/dev/sdc1 294G 58G 222G 21% /media/sda1
/dev/sda5 75G 52G 24G 69% /media/sdb5
/dev/sdb1 38G 23G 16G 60% /media/sdc1

I'm not sure how to get the UUID of a hard drive, but if somebody tells me how, I'll post that too. Good luck!

[Dane Mutters (dmutters)]

One more thing:

Before this update, I believe that my HDs on the add-in card were seen as /dev/hdx, like they are in my Gentoo installation on a different partition.

[Susan Cragin (susancragin)]

I also had severe problems with 3/29 updates.
I have an Acer Ferrari with ATI Mobility Radeon 7000.
My video card no longer works.
I tried updating xorg. No luck.
I tried adding the following to the conf file;
Option "MonitorLayout" "LVDS,AUTO"
which has worked for the past 8 or so of my installs.
No luck.

Feisty does run from the command line. I have done apt-get update, apt-get install, and then apt-get upgrade.
All updates / upgrades are in place.

I'm not very technically proficient, but any test I can run to be of help I will willingly do.

Susan

[Dane Mutters (dmutters)]

Yet one more thing:

I figured out how to get UUIDs, and I edited my fstab accordingly. Now, upon boot, it seems that the kernel (or whatever) keeps mixing up my devices, even duplicating one of them where another should be.

dane@Orchestrator:~$ blkid
/dev/hda1: UUID="63f0e2a3-b520-42d8-943b-94e4b4a381b1" TYPE="reiserfs"
/dev/hda2: UUID="1981f215-6f5b-4d93-9216-55ba82e34427" TYPE="reiserfs"
/dev/hda3: UUID="c9d191a9-54eb-4a49-a60c-f818818acaa0" TYPE="reiserfs"
/dev/hda4: TYPE="swap" UUID="abfe74bc-4a48-496f-9f15-094d868d41fa"
/dev/hdc1: UUID="5cb9b1f1-af20-40ec-a362-f2bd1e64e8c6" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdc2: TYPE="swap" UUID="0baa44d4-2bdc-4761-960d-5126e9c85217"
/dev/sdc1: LABEL="PERSONAL" UUID="88813472-f156-4ee6-b8e9-41540ff07486" TYPE="ext2"
/dev/sdb1: TYPE="ntfs"
/dev/sda1: LABEL="PERSONAL" UUID="88813472-f156-4ee6-b8e9-41540ff07486" TYPE="ext2"
/dev/sdb5: LABEL="BACKUP" UUID="438E-1221" TYPE="vfat"

I hope that helps.

Also, Susan, thanks for your bug report. Please make a separate report for it instead of clumping it in with this report; it'll be more likely to be seen that way.

[Brian Murray (brian-murray)]

I am under the impression that you determined the UUIDs for the partitions and then updated your fstab and this did not work on reboot because "the kernel (or whatever) keeps mixing up my devices"? If this is correct what behaviour did your system exhibit on booting? Thanks in advance.

[Dane Mutters (dmutters)]

Thanks for your attention to this bug.

It's been a while, so I don't have any details to give you about the boot-up at that time, but I do recall that it did boot properly. The main problem (as far as I've figured it out) is that my Promise Ultra133TX2 PCI ATA133 card and my nVidia CK804 rev. f3 SATA controller keep getting their attached hard drives mixed-up. Here's what I mean:

dane@Orchestrator:~$ sudo blkid
/dev/hda1: UUID="63f0e2a3-b520-42d8-943b-94e4b4a381b1" TYPE="reiserfs"
/dev/hda2: UUID="1981f215-6f5b-4d93-9216-55ba82e34427" TYPE="reiserfs"
/dev/hda3: UUID="c9d191a9-54eb-4a49-a60c-f818818acaa0" TYPE="reiserfs"
/dev/hda4: UUID="abfe74bc-4a48-496f-9f15-094d868d41fa" TYPE="swap"
/dev/sda1: LABEL="BACKUP" UUID="63ed91b2-a8c2-417c-b93f-985bbf1e93fb" TYPE="ext2"
/dev/hdc1: UUID="ecb2eafe-3009-478f-84bb-70faea5115bc" SEC_TYPE="ext2" TYPE="ext3"
/dev/hdc5: UUID="877dcd40-e70c-4cec-81fc-bb44dbd81f12" TYPE="swap"
/dev/sdb1: TYPE="ntfs"
/dev/sdc1: LABEL="PERSONAL" UUID="88813472-f156-4ee6-b8e9-41540ff07486" TYPE="ext2"

dane@Orchestrator:~$ sudo mount
/dev/hdc1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.20-16-generic/volatile type tmpfs (rw)
/dev/hda1 on /media/hda1 type reiserfs (rw)
/dev/hda2 on /media/hda2 type reiserfs (rw)
/dev/hda3 on /media/hda3 type reiserfs (rw)
/dev/sdc1 on /media/sda1 type ext2 (rw)
/dev/sda1 on /media/sdb1 type ext2 (rw)
/dev/sdb1 on /media/sdc1 type ntfs (rw,nls=utf8,umask=007,gid=46)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

dane@Orchestrator:~$ sudo df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 18G 16G 1.7G 91% /
varrun 502M 116K 502M 1% /var/run
varlock 502M 0 502M 0% /var/lock
procbususb 502M 140K 502M 1% /proc/bus/usb
udev 502M 140K 502M 1% /dev
devshm 502M 0 502M 0% /dev/shm
lrm 502M 39M 464M 8% /lib/modules/2.6.20-16-generic/volatile
/dev/hda1 957M 128M 830M 14% /media/hda1
/dev/hda2 120G 41G 79G 34% /media/hda2
/dev/hda3 113G 107G 6.0G 95% /media/hda3
/dev/sdc1 294G 81G 199G 29% /media/sda1
/dev/sda1 74G 73G 0 100% /media/sdb1
/dev/sdb1 38G 28G 9.4G 76% /media/sdc1

As you can see, /dev/sda1, according to blkid, is an 80GB drive labeled "BACKUP", /dev/sdb1 is my 40GB Windows XP installation on NTFS (which, incidentally does not have a UUID, as NTFS usually doesn't), and /dev/sdc1 is a 300GB drive labeled "PERSONAL". In the blkid information in my April 4th, 2007 post, the aforementioned drives are as follows:

/dev/sdc1: LABEL="PERSONAL" UUID="88813472-f156-4ee6-b8e9-41540ff07486" TYPE="ext2"
/dev/sdb1...

[Przemek K. (azrael)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The version of Ubuntu that you were using has reached its End Of Life. Please test the latest Ubuntu version (9.10) and report a new bug if necessary.
https://help.ubuntu.com/community/ReportingBugs