Re: Updating superblock to reflect new disc locations

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

 



On Wednesday January 11, linux-raid@xxxxxxxxxxx wrote:
> 
> 
> Any suggestions would be greatly appreciated. The system's new and not 
> yet in production, so I can reinstall it if I have to, but I'd prefer to 
> be able to fix something as simple as this.

Debian's installer - the mkinitrd part in particular - is broken.
If you look in the "initrd" (it is just a compressed CPIO file) you
will find the mdadm command used to start the root array explicitly
lists the devices to use.  As soon as you change the devices, it stops
working :-(  Someone should tell them about uuids.

I think you can probably fix you situation by:
  Booting up and having a degraded array
  hot-add the missing device and wait for it to rebuilt
  rerun mkinitrd

The last bit might require some learning on your part.  I don't know
in Debian's mkinitrd requires and command line args, or where it puts
the result, or whether you have to tell lilo/grub about the new files.

I would try just running "mkinitrd" with no args, and the "lilo" - if
you are using lilo, and reboot.  See what happens....

NeilBrown
-
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