booting with kernel .35-19 error /etc/fstab

[Mikel Artaso]

After updating to ubuntu 10.10 from 10.04 and when trying to boot with the .35-19 kernel the system does not what established in the /etc/fstab file. With the kernel .32-14 it works well.

/etc/fstab

# /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/sda6 during installation
UUID=a611cb24-0bb3-4d8f-bc61-efddee60206a / ext4 relatime,errors=remount-ro 0 1
/dev/sda7 /home ext4 nodev,nosuid 0 2
/dev/sda5 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/sda2 /media/cwindows ntfs defaults 0 0
/dev/sda3 /media/datos_windows ntfs defaults 0 0

[Mikel Artaso (mikel-artaso)]

Also happens with kernel .35-20

The system says that is unable to mount /home/mikel and that it doesn't find /dev/sda5

[Mikel Artaso (mikel-artaso)]

The problem has been solved changing to UUID the method to locate the media. When I have launched the blkid command I have obtained this:

/dev/sdb1: LABEL="WinRE" UUID="4072D79C72D7954E" TYPE="ntfs"
/dev/sdb2: LABEL="System" UUID="6E646A89646A53BD" TYPE="ntfs"
/dev/sdb3: LABEL="Data" UUID="EAF0F1A3F0F175E3" TYPE="ntfs"
/dev/sdb5: UUID="edeecaf2-4cef-4ce1-9aba-e6e10085c2c7" TYPE="swap"
/dev/sdb6: UUID="a611cb24-0bb3-4d8f-bc61-efddee60206a" TYPE="ext4"
/dev/sdb7: LABEL="datos_home" UUID="f384692c-dcef-40d2-a4a0-d3af9a83280d" TYPE="ext4"

So something has changed /dev/sdax to /dev/sdbx

[David Tenty (daltenty)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Mounting in fstab by UUID is preferred as it prevents this issue and that is why the Ubuntu installer creates UUID based mounts in fstab. If you still have issues after switching to UUID based fstab entries please reopen this bug.