Bugzilla – Bug 115827
Updater does not recognize exiting linux partitions
Last modified: 2005-09-14 14:41:08 UTC
So far I updated quite a few times from betaN to betaN+1 and the updater always found the root partition. However, this didn't happen with RC1. I'll set this to critical, because this could prevent easy updating from SL93 to SL10.0. As soon as I get y2log files, I'll attach them.
Created attachment 49182 [details] y2log
According to log, all detected partitions have in their target map set: "detected_fs":`unknown Thomas, Arvin?
The command blkid to detect the filesystems returns -127 (seg. fault?). Please run as root the command "BLKID_SKIP_CHECK_MDRAID=1 /sbin/blkid -c /dev/null" and provide the output (best done in the inst-sys).
Doing this gives no output, just a Floating Point Exception.
So it's a blkid problem.
Maybe you can also try without the BLKID_SKIP_CHECK_MDRAID=1. But it's unlikely this changes anything.
i need more info. can i access that machine somewhere?
Of course. Its name is "testbox". Standard root pwd. If you want physical access, it's on 2nd floor, room next to the garbage can.
the machine is offline. cant do anything now......
It's online again.
its failing on reiserfs with a blocksize of 512
mason/jeff please have a look at this patch. its just skipping the check if the blocksize is smaller then 1024. Were not sure what that check is for.
Created attachment 49356 [details] patch for probe_reiserfs
wtf
The check is because reiserfs 3.5.x and higher disks have the super block at offset 64k. The older disk format has the super block at 16k and, and 64k into the disk is the journal. If there is a copy of the super block logged at offset 64k on an old format disk, the detection code will incorrectly think it is a newer format FS. So the check compares the block number of the super block found with the journal parameters of the FS and makes sure the superblock isn't inside its own journal. We need to keep the check.
But does the patch in Comment #13 hurt?
Thinking harder, it doesn't hurt. The older filesystems don't support a blocksize of 512 bytes, so you can't possibly find a 512 byte super in the log of an older FS. The patch is fine.
It's checked in for RC2