Comment 0 for bug 203704

Revision history for this message
Andrew Reusch (areusch) wrote : vol_id

Binary package hint: volumeid

Hi,

Here's the issue:

I'm running Feisty with the latest updates.

During the boot it will come up to "Checking local filesystems" at which point it will try and do a check on /dev/sda3, which has fstab entry as follows:
# Entry for /dev/sda3 :
UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa /home reiserfs defaults 0 2

Unfortunately, upon boot, I get this (/var/log/fsck/checkfs):
Log of fsck -C -R -A -a
Tue Mar 18 13:38:16 2008

fsck 1.40-WIP (14-Nov-2006)
Failed to open the device 'UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa': No such file or directory

fsck died with exit status 8

Tue Mar 18 13:38:16 2008
----------------

At this point, it drops to a maintenence shell with a very screwy path (just /bin or something useless like that).

Running sudo blkid /dev/sda3 will report:
/dev/sda3: UUID="a1a4ee27-950c-4439-9ce8-e69b4795c5c3" TYPE="reiserfs"

Running blkid reports the correct value; running vol_id reports a swap partition with UUID=ef5542e4-9a86-4504-a4f0-1edc56bc30aa

The problem was that the partition used to be a swap partition, and mkreiserfs did not overwrite the first 64 KB of the partition.

IMHO, vol_id should check for other filesystem headers first and they should override whatever swap signature found. If the swap partition was actually being used, wouldn't the use overwrite whatever filesystem header is there?

Thanks,
Andrew