*** This bug is a duplicate of bug 221210 ***
https://bugs.launchpad.net/bugs/221210
The problem has been fixed like this :
(1) use of "sudo dumpe2fs -h /dev/sd** |grep UUID" to collect all UUID of my HD
partitions,
(2) edition of "/etc/ftab" to replace hardware ID of device suche as
"/dev/sd**" by their corresponding UUID.
note : apparently it is not possible to collect with (1) the UUID of a swap
partition ; ie here "sda7" when trying ; I collect this error message :
dumpe2fs: Bad magic number in super-block lors de la tentative d'ouverture de
/dev/sda7
Now from past construction my fstab has this line the sawp partition :
UUID=a296c745-3387-46b1-be48-c30b6dd7d3ec none swap sw
0 0
So can I say that this UUID is linked to my "sda7" swap partition but that (1)
cannot retrieve the UUID !
Going this way at the end of the day I can safely boot both kernels :
- 2.6.24-16-generic
- 2.6.22-14-generic
BUT :
- with the first kernel Qtparted shows 2 devices mounted : "sdb" and "sdc".
- With the first kernel Qtparted shows 2 devices mounted : "sda" and "sdb".
All this does not make sense as there is no objective reason for one
kernel to see hardware devices differently from another on the same
machine ; if one has implemented UUID to reach this stage it is worse as
it means that if you add a HD device to temporarily retrieve data YOU DO
NOT KNOW WHICH DEVICE TO MOUNT with : mount _device _location
Regards.
--
[Hardy 64 bits]no correct boot with kernel
https://bugs.launchpad.net/bugs/221212
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
