Re: booting into /dev/md0 after an upgrade to squeeze

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 18/10/10 19:14, Janek Kozicki wrote:
But, maybe do you have some experience with booting into raid1 /dev/md0
after upgrading to squeeze?

You can stop grub doing the root=uuid= thing by changing /etc/default/grub

If you can get someone to the keyboard, then you can probably get them to edit what grub is using as a one-off - i.e. change the root=uuid=xxx entry to root=/dev/md0 (or even just one half of the mirror if you need to get it working, then you can fix it later)...

It's also worth checking the contents of /etc/mdadm/mdadm.conf is sensible - maybe if you duplicated the partition (with dd maybe, if you said you duplicated the UUID), then it contains an incorrect uuid= line?

If it's incorrect, you may need to regenerate the initramfs having corrected it (a copy is placed in the initramfs files) with "update-initramfs -k all -u"

In a similar situations, where I have no remote console (IPMI SoL, Intel AMT etc.), I like to use "qemu -snapshot ..." to verify that a system will boot up correctly by pointing it at the real hard disks (see recent post to this list).

HTH,

Tim.

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux