<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-15" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Matthias Brennwald wrote: <blockquote cite="mid:F366BA08-2CED-4411-B5AC-D660885C90B8@brennwald.org" type="cite"> <pre wrap="">On 6. Jul 2010, at 9:08, Matthias Brennwald wrote: </pre> <blockquote type="cite"> <pre wrap="">On 6. Jul 2010, at 3:26, Christopher Chan <a class="moz-txt-link-rfc2396E" href="mailto:christopher.chan@bradbury.edu.hk"><christopher.chan@bradbury.edu.hk></a> wrote: </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">I am able to boot using a rescue CD (I used the Ubuntu alternate installer disk, because the Live CD does not have md/softraid support), but I don't really know how to proceed in order to fix things. I would greatly appreciate any hints on how to get the machine up and running again. For instance, which commands should I try after booting into the Ubuntu rescue CD? </pre> </blockquote> <pre wrap=""> mdadm --assemble --scan </pre> </blockquote> <pre wrap=""> Result: "No arrays found in config file" On 6. Jul 2010, at 8:26, Luis Paulo <a class="moz-txt-link-rfc2396E" href="mailto:luis.barbas@gmail.com"><luis.barbas@gmail.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""># apt-get install mdadm # mdadm --auto-detect </pre> </blockquote> <pre wrap=""> I skipped the "apt-get install" because I am using the Ubuntu Alternate Disk which already has mdadm. Then I ran "mdadm --auto-detect", which gave no result. Do I have to specifiy the md devices explicitly somehow? These would be /dev/sdb1, /dev/sdc1 and /dev/sdd1 (plus the spare /dev/sde1) Just a note that might be important (but I am not sure): before entering the shell of the alternate disk I was asked about the root file system and where I wanted to execute the shell. I chose "do not use a root file system" and "execute shell in installer environment". Thanks for your help! Matthias </pre> </blockquote> <pre wrap=""> I tried a little more (inspired by <a class="moz-txt-link-freetext" href="http://fts.ifac.cnr.it/cgi-bin/dwww/usr/share/doc/mdadm/README.recipes.gz">http://fts.ifac.cnr.it/cgi-bin/dwww/usr/share/doc/mdadm/README.recipes.gz</a> ): mdadm --assemble --auto=yes --force /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sdd1 Result: mdadm: cannot open device /dev/sdb1: No such file or directoy mdadm: /dev/sdb1 has no superblock - assembly aborted </pre> </blockquote> Do you have or have you ever had a fakeraid on these drives? I had a similar message recently with the Live CD attempting to activate some non-existent fakeraid. The "nodmraid" option eliminated the problem. I'm not sure if that option is available on the alternate install disk. Look in /dev/mapper and see if there is anything odd in there. Try running mdadm from inside the initramfs shell if you can assemble them there you can probably boot from that point, or try booting the Live CD with the F6 nodmraid option. <blockquote cite="mid:F366BA08-2CED-4411-B5AC-D660885C90B8@brennwald.org" type="cite"> <pre wrap="">Then I looked at /dev/sdb using "fdisk -l". The output of this is too long to copy it (I am typing everything manually here, because I have no clue how to transfer a file from the machine running the rescue disk). Here are the last two lines (the rest does not mean much to me): Device Boot Start End Blocks Id System /dev/sdb1 1 243202 1953514583+ ee GPT What do you guys think? Matthias </pre> </blockquote> <div class="moz-signature">-- <meta content="text/html; charset=ISO-8859-15" http-equiv="content-type"> <title>Signature</title> Robert Steinmetz, AIA Principal Steinmetz & Associates </div> </body> </html>