[Bug 128313] Re: /dev/md0 does not exist. Dropping to a shell.
Just wanted to add this also happened to me during the lucid release cycle. I followed Mark's instructions above. 1. Boot from ubuntu livecd (preferably the same version as you were running) 2. sudo apt-get install mdadm 3. sudo mdadm --assemble --scan 4. sudo mkdir /md0 5. sudo mount /dev/md0 /md0 6. sudo mv /boot /boot1 7. sudo ln -s /md0/boot /boot 8. uname -r 9. Use the output of step 8 to replace in the update-initramfs step; make sure the kernel you specify exist on your installation. You can check /md0/boot to see what kernels you have sudo update-initramfs -k 2.6.32-18-generic -c -t -- /dev/md0 does not exist. Dropping to a shell. https://bugs.launchpad.net/bugs/128313 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128313] Re: /dev/md0 does not exist. Dropping to a shell.
Ohh, also update-initramfs failed, giving a read-only media error. If this happens to you, do the following to replace the running version of update-initramfs and try again mv /usr/sbin/update-initramfs /usr/sbin/update-initramfs.old ln -s /rofs/usr/sbin/update-initramfs /usr/sbin/update-initramfs -- /dev/md0 does not exist. Dropping to a shell. https://bugs.launchpad.net/bugs/128313 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128313] Re: /dev/md0 does not exist. Dropping to a shell.
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find. ** Changed in: ubuntu Status: New = Invalid -- /dev/md0 does not exist. Dropping to a shell. https://bugs.launchpad.net/bugs/128313 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128313] Re: /dev/md0 does not exist. Dropping to a shell.
I've worked out the last steps: sudo mv /boot /boot1 sudo ln -s /md0/boot /boot sudo update-initramfs -k 2.6.22-14-generic -c -t sudo update-initramfs -k 2.6.22-14-386 -c -t I was confused because I did not have 2.6.20-22-generic, but guessed I should used the latest one. I can now boot from either one of the above kernels. -- /dev/md0 does not exist. Dropping to a shell. https://bugs.launchpad.net/bugs/128313 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128313] Re: /dev/md0 does not exist. Dropping to a shell.
I'm a little closer. [EMAIL PROTECTED]:~$ sudo apt-get install mdadm Reading package lists... Done Building dependency tree Reading state information... Done Recommended packages: mail-transport-agent The following NEW packages will be installed: mdadm 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 220kB of archives. After unpacking 627kB of additional disk space will be used. Get:1 http://archive.ubuntu.com gutsy/main mdadm 2.6.2-1ubuntu2 [220kB] Fetched 220kB in 4s (45.9kB/s) Preconfiguring packages ... Selecting previously deselected package mdadm. (Reading database ... 92004 files and directories currently installed.) Unpacking mdadm (from .../mdadm_2.6.2-1ubuntu2_i386.deb) ... Setting up mdadm (2.6.2-1ubuntu2) ... Generating array device nodes... done. Generating mdadm.conf... done. Removing any system startup links for /etc/init.d/mdadm-raid ... update-initramfs: deferring update (trigger activated) * Starting MD monitoring service mdadm --monitor [ OK ] Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.22-14-generic [EMAIL PROTECTED]:~$ sudo mdadm --assemble --scan mdadm: /dev/md0 has been started with 2 drives. mdadm: /dev/md1 has been started with 2 drives. [EMAIL PROTECTED]:~$ sudo mkdir /md0 [EMAIL PROTECTED]:~$ sudo mount /dev/md0 /md0 This gives me access to my original /dev/md0 What next? Mark -- /dev/md0 does not exist. Dropping to a shell. https://bugs.launchpad.net/bugs/128313 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128313] Re: /dev/md0 does not exist. Dropping to a shell.
I seem to have same problem, but I don't know how to apply this solution. I just updated 6.06 - 6.10 - 7.04 - 7.10 over the pass couple of days. This last update left me it this /dev/md0 does not exist. dropping to a shell state. I've download a 7.10 desktop cd, and have booted off this. The update-initramfs command fails cannot find /lib/modules/2.6.20-16-generic But also it appears that this live boot does not see /dev/md0, so how could create a new boot image on this raid. Mark -- /dev/md0 does not exist. Dropping to a shell. https://bugs.launchpad.net/bugs/128313 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128313] Re: /dev/md0 does not exist. Dropping to a shell.
I have now managed to resolve this issue with the help of the support forum http://ubuntuforums.org/showthread.php?t=515594 (many thanks Midahed). The main issue was that the article listed above uses the initrd tools to create a boot image but Ubuntu now uses initramfs-tools for this. Once I realised that instaling mdadm was actually creating a new boot image, I was able to copy this across to md0 and then select this at boot time to get into the system. Once booted from md0 I could then use update-initramfs -k 2.6.20-16-generic -c -t to create a boot image with the latest Kernel (live cd at 2.6.20-15). -- /dev/md0 does not exist. Dropping to a shell. https://bugs.launchpad.net/bugs/128313 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
