Debian Installation :: Grub Rescue - Will Not Boot From Mdadm RAID - No Such Disk
Sep 19, 2014
I am running a 14 disk RAID 6 on mdadm behind 2 LSI SAS2008's in JBOD mode (no HW raid) on Debian 7 in BIOS legacy mode.
Grub2 is dropping to a rescue shell complaining that "no such device" exists for "mduuid/b1c40379914e5d18dddb893b4dc5a28f".
Output from mdadm:
Code: Select all # mdadm -D /dev/md0
Version : 1.2
Creation Time : Wed Nov 7 17:06:02 2012
Raid Level : raid6
Array Size : 35160446976 (33531.62 GiB 36004.30 GB)
Used Dev Size : 2930037248 (2794.30 GiB 3000.36 GB)
Raid Devices : 14
Output from blkid:
Code: Select all # blkid
/dev/md0: UUID="2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb" TYPE="xfs"
/dev/md/0: UUID="2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb" TYPE="xfs"
/dev/sdd2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="09a00673-c9c1-dc15-b792-f0226016a8a6" LABEL="media:0" TYPE="linux_raid_member"
The UUID for md0 is `2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb` so I do not understand why grub insists on looking for `b1c40379914e5d18dddb893b4dc5a28f`.
**Here is the output from `bootinfoscript` 0.61. This contains alot of detailed information, and I couldn't find anything wrong with any of it: [URL] .....
During the grub rescue an `ls` shows the member disks and also shows `(md/0)` but if I try an `ls (md/0)` I get an unknown disk error. Trying an `ls` on any member device results in unknown filesystem. The filesystem on the md0 is XFS, and I assume the unknown filesystem is normal if its trying to read an individual disk instead of md0.
I have come close to losing my mind over this, I've tried uninstalling and reinstalling grub numerous times, `update-initramfs -u -k all` numerous times, `update-grub` numerous times, `grub-install` numerous times to all member disks without error, etc.
I even tried manually editing `grub.cfg` to replace all instances of `mduuid/b1c40379914e5d18dddb893b4dc5a28f` with `(md/0)` and then re-install grub, but the exact same error of no such device mduuid/b1c40379914e5d18dddb893b4dc5a28f still happened.
One thing I noticed is it is only showing half the disks. I am not sure if this matters or is important or not, but one theory would be because there are two LSI cards physically in the machine.
This last screenshot was shown after I specifically altered grub.cfg to replace all instances of `mduuid/b1c40379914e5d18dddb893b4dc5a28f` with `mduuid/2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb` and then re-ran grub-install on all member drives. Where it is getting this old b1c* address I have no clue.
I even tried installing a SATA drive on /dev/sda, outside of the array, and installing grub on it and booting from it. Still, same identical error.
I accidently deleted my ubuntu partition, and when boot I get this message:GRUB loading.error:unknown filesystemgrub rescue>I can't get into my bios options either... I just see the MSI splash screen and it cuts right to this error message.
I am fresh to Ubuntu and am having trouble getting it to boot on my system. I normally run XP, but recently added a second internal hard drive and installed Ubuntu on it. The installation went fine and upon initial reboot I received -
GRUB loading. error: no such disk grub rescue>
I am wondering if there is an issue between two different operating systems upon boot. I am not familiar with GRUB commands.
Downloaded Ubuntu 10.04.1 Desktop AMD64, tried to install it to a cleand HDD using the whole HDD, i.e. gave it permission to use the whole HDD. Installation process appeared to run OK but when it came to the restart it just fired up the message
error: out of disk grub rescue>
I've searched this forum and found numerous references to these error messages but cannot make head nor tail of the diagnostic suggestions. Apart from anything else they suggest strings of command lines which I don't understand and can't enter anyway since they don't correspond to my keyboard layout (if I hit > or ) something completely different appears on the screen). Is there someone here who can provide a step-by-step solution in lay language ? Or is there such a thing as a bootable file which can be downloaded and inserted into my CD drive to correct this problem ?
I'm inexperienced in Debian. I have a dual-boot machine (64-bit, Debian 7.3, Windows 7, legacy boot) and encouter a problem at boot ever since I completed the installation of Debian 7.3 alongside the exising Windows 7. This machine has six hard drives: two are intended for ntfs storage of general data (raided together by RAID1); two more are intended for ext4 storage of general data (also raided together by RAID1); the fifth contains the Windows OS files and the sixth contains the Debian OS files. The problem is that I arrive to the grub_rescue each time at boot, seeing the message:
GRUB loading. Welcome to GRUB!
error: no such device: e081517b-3399-4067-9294-8f0686f753ca. Entering rescue mode... grub_rescue>
I have a raid5 on 10 disk, 750gb and it have worked fine with grub for a long time with ubuntu 10.04 lts. A couple of days ago I added a disk to the raid, growd it and then resized it.. BUT, I started the resize-process on a terminal on another computer, and after some time my girlfriend powered down that computer! So the resize process cancelled in the middle and i couldn't acess any of the HDDs so I rebooted the server.
Now the problem, the system is not booting up, simple black with a blinking line. Used a rescue CD to boot it up, finised the resize-process and the raid seems to be working fine so I tried to boot normal again. Same problem. Rescue cd, updated grub, got several errors: error: unsupported RAID version: 0.91. I have tried to purge grub, grub-pc, grub commmon, removed /boot/grub and installed grub again. Same problem.
I have tried to erased mbr (# dd if=/dev/null of=/dev/sdX bs=446 count=1) on sda (ide disk, system), sdb (sata, new raid disk). Same problem. Removed and reinstalled ubuntu 11.04 and is now getting error: no such device: (hdd id). Again tried to reinstall grub on both sda and sdb, no luck. update-grub is still generating error about raid id 0.91 and is back on a blinking line on normal boot. When you'r resizeing a raid MDADM changed the ID from 0.90 to 0.91 to prevent something that happend happened. But since I have completed the resize-process MDADM have indeed changed the ID back to 0.90 on all disks.
I have also tried to follow a howto on a similar problem with a patch on [URL] But I cant compile, various error about dpkg. So my problem is, I cant get grub to work. It just gives me a blinking line and unsupported RAID version: 0.91.
I had Ubuntu installed, i installed Debian and there was no dual boot. So i formated all the hard disk to install only Debian. It installed but at boot i get error: no such device and the grub rescue> prompt. i googled for a solution and nothing worked:
- i tryed reinstalling grub, not worked - i did the windows cd fixmbr trick, not worked - reinstalled debian with fixmbr the first step and nothing - tryed deleting with dd the mbr, not worked - reinstalled grub from debian rescue, not worked
what should i do? i can't access my computer? please tell me how should i fix it? the google guys will kill me because i put their servers on fire
Trying to do a new install of ubuntu 10.10 to my laptop. Installation and all works fine, but upon rebooting, after the bios screen i get:
Code: error: out of disk. grub rescue> I tried using following some instructions i found after googling for the problem: Code: ls (displays the partitions and devices Grub can see) set prefix=(hdX,Y)/boot/grub
but after the 5th step, i get another "error: out of disk" message. The odd thing is that I had an install of 10.10 on this laptop a month ago, and it worked fine. As a side note, I installed fedora 14 after this happened, which worked fine. Reinstalled ubuntu, and it was back to the same problem. I also tried installing with a kubuntu cd I had, to make sure it wasnt the install media, and had the same problem.
Recently, one the SMART utility said that one of the drives had failed and another drive was about to fail. I downed the box and hooked them up to my windows machine to run sea tools on them (They are all seagate drives). Sea Tools said that the drives were fine, while ubuntu said they were failing/dead. Yesterday I decided to try to fix one of the drives in the raid. I turned the server off, took the failed drive out, and restarted. Of course the raid didn't work because only 2 of the 3 drives were there, however it had been working w/ only 2 of the 3 drives for a couple months now (I'm a lazy college student). I turned it back off and back on with the drive there just to see if I could get the raid up again, but I havn't been able to get it to go. So far I've tried:
mdadm --assemble /dev/md0 /dev/sd[b,c,d] mdadm: no recogniseable superblock on /dev/sdb mdadm: /dev/sdb has no superblock - assembly aborted
I'm looking for a way to trick the raid into working with just 2 drives until I can warranty the seagate and buy an external 1.5 TB drive to use as another backup. how to remove the bad drive from the array and replace it with a fresh drive, without data loss.
I have a fileserver which is running Ubuntu Server 6.10. I had a RAID5 array consisting of the following disks:
Code: /dev/sda1 /dev/sdb1 /dev/sdd1 /dev/md0 -
the raid drive for the above three disks. The sda1 disk has failed and the array is running on 2 of 3 disks
/dev/sdc (OS disk) /dev/sde (new 2tb disk - unused) /dev/sdf (new 2tb disk - unused)
My plan was to rebuild the array using the two new disks as RAID1. Would the best way to do this be to create a new RAID1 disk on /dev/md1 then copy all data over from /dev/md0? Also - this may sound stupid but since all 3 drives in md0 are identical i'm not sure physically which disk is bad. I tried disconnecting each disk one-by-one then rebooting but the system doesn't appear to want to boot without the bad drive connected. I've already failed the disk in the array with mdadm but i'm unsure of how to remove it properly.
I updated yesterday and now when I start my laptop it goes in to grub rescue mode. I have booted from a 'live cd' and thought I could repair grub from there. In gparted however the partition with ubuntu (sda1) is seen as unknown file system, in terminal when I list the partition table it shows up as FAT16 type. When I try a grub-install it gives this error message:
We have some servers that run in very harsh environments (research vessel) that need to have high-availability.We have software RAID 1 for some measure of resiliency, along with proper data backups (tapes etc), however we would like to be able to break out a new server and re-image it (including RAID setup) from a known good copy if the hardware completely fails on the production box. Simplicity of the process is a big plus.I am interested in any advice on the best way to approach this. My current approach (relatively new to Linux administration, totally new to MDADM) is to use DD to take a complete gzipped copy of one of the RAID'ed devices (from a live CD): ode: dd if=/dev/sda bs=4096 | gzip -c > /mnt/external/image/test.img then reverse the process on the new PC, finally using Code:mdadm --assemble to re-create and re-build the array.
My system doesn't boot anymore, when I turn on the laptop, instead of the normal grub screen, i get the following:
"error: file not found Entering rescue mode... grub rescue> _"
I tried also to make a bootable usb w/ unetbootin but all the distros failed to load w/ a syslinux boot error message so I really need to fix the existing debian installation to get access to my files i need for the university, it's debian stable (6.0.4) on hp mini 210 ....
I've got Ubuntu 10.04 installed on one partition, and Windows Vista on another. I was messing around with my partitions, and now I can't boot to either one. I just get an error when I boot up on GRUB which says "error: no such partition", and then a prompt saying 'grub rescue>'. I've read up on other people's posts, and they said that I should reinstall GRUB from a livecd, but that doesn't look like it does anything. It seems that GRUB is trying to boot from hd0,8, and that doesn't exist anymore. I can change the 'root' and 'prefix' variables to the right partitions, but the 'boot' or 'chainloader' command doesn't work. You should be able to boot from 'grub rescue>', because that's what it's for, right?
I just want to be able to boot into Ubuntu, not Windows.
PS: Sorry if I'm specifying way too much information(or not enough), I'm fairly new to forums.
I'm experimenting a bit with my fedora, so I need to enter rescue mode very often. Every time I want to enter rescue mode, I need to insert fedora DVD Is there a way to install rescue mode on my hard drive so I could boot into rescue mode from GRUB?
So I had Ubuntu Server installed and I decided to make some new partitions using gparted via a live usb of Ubuntu desktop. And so I think messed up pretty badly. Ubuntu Server won't boot and I get the following error followed by a grub rescue promt:
Code:Diskette drive 0 seek failure error: file not found grub rescue > To me, it seems like some boot files may be missing if not the whole system. After I made the partitions, the live USB of Ubuntu was still working fine until I rebooted.So here is the bigger issue, I figured I would just reinstall everything all over again, but instead I can't.
So earlier today I was running out of space on my regular Windows 7 partition and I played around with extending it. I ended up somehow deleting grub and messing up my entire system. I've spent the last 2 hours looking for the answer to this and everyone has been saying to boot from a live disk and fix it that way.
Well, I've tried everything, the only way I can boot right now is via USB and it will NOT allow me to. I checked on other computers and even re-installed and formatted by external hard drive to try and get it to work and it refuses. I've changed my BIOS to boot from USB so I have no idea as to why this is happening. Also, I've tried using the "ls" command to find my partition via "ls (hdX,Y)/" and all of them come up as unknown filesystems.
I have a SONY VAIO CW26 laptop. I got a Windows-7 version prepacked with the laptop.I installed Ubuntu Karmic 9.10 over a new partition that i created using the inbuiltfacility in windows7. Both the operatings systems i.e windows7 and ubuntu karmic 9.1 were working nicely.Today i created 2 more partition within the partition inside windows.Once I rebooted after creation of the new partitions my laptop is just showing a black screen with following message.
First time poster and recent Ubuntu adopter. I recently installed 10.10 on my main HD alongside a separate windows (xp) partition (it worked perfectly). Then I decided to get fancy and installed 10.10 to a flash drive directly from a live cd. I attempted to boot from the flash drive, and got a black screen with a blinking underscore for about 10 minutes, then I forcefully rebooted. Now, whenever I attempt to boot at all from my main HD I get "error: no such device and a ton of misc numbers. And the flash drive will not allow me to boot from it. Currently, I'm working within the Live CD.
I have a few projects I need to complete with Dreamweaver inside XP, so recovering it completely would be nice.
Code: Boot Info Script 0.55 dated February 15th, 2010 ============================= Boot Info Summary: ============================== => Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #1 for (,msdos1)/boot/grub. => No boot loader is installed in the MBR of /dev/sdf
I set up my Dell Inspiron Laptop as Dual Boot -> Xp / Ubuntu 10.04. - all worked well. I had 2 installations of XP on this machine and I removed one - all worked well. I then went into XP and deleted the partion (4) that the old XP had resided on (using Easeus Partition Master) All NOT working well !! Now when booting the machine I get grub rescue> I did ls and got ....
I was dual-booting XP and Ubuntu 10.10 for a while, but as I never used Ubuntu it was just taking up space, so I figured I'd get rid of it. I used a partitioning tool from inside XP to remove the Ubuntu partition, forgetting that I used GRUB2 every time I booted to select which OS to load. Now when I start my computer I get stuck at the "grub rescue>" screen.After searching for solutions to this problem all of them said to either use the Windows XP CD to fix the Master Boot Record or reinstall Ubuntu, but I dont have my XP CD and there isnt enough room on my hard drive anymore for a Ubuntu install. Is there anything else I can do to fix this?
My home-backup server, with 8*2TB disks won't boot anymore. Two disks failed at the same time and i rebuilt the raid 6 array without any problem, but now i can't boot the os. I'm using ubuntu server, 10.10. I've made screens of the displays to don't copy everything here. The problem at the boot:
And the Grub config: It's not a production server, but i would like to have it online. I've tried for the lasts 2 days (just a couple hours a day) but without success. I was suggested to do "mount -o remount,rw /" and than edit /etc/fstab, but it get the file don't exist error.
I attempted to upgrade from 10.04 to 10.10. Upon restarting, I was presented this message:
error: the symbol 'grub_xputs' not found. grub rescue>
I poked around the forums and found several posts that would probably be helpful but... I am unable to boot from a USB nor can I burn a Live CD as my other computer is a netbook. I made USB first boot in BIOS, but no luck.
Installed Ubuntu 10.04 a week ago or so (using wubi.)Tried to upgrade to 10.10 from within Ubuntu using the update manager.Now the PC will only boot to grub rescue.When booting, this is what i get:error: no such device: cd200414-0606-4d7d-8c08-004e9b5dc92d.grub rescue>Three commands work: ls, set and insmod.The ls command only yields: (hd0)(no partitions like (hd0,1), (hd0,5), etc.)
I had 250gb hard disk with dual boot, xp and ubuntu 10.10.Yesterday, i tried to upgarde my ubuntu 10 to 11 from a live cd....b4 doing so, i used a win software EasyBCD to fix the mbr but it didn't work properly..and i ignored it(my biggest mistake)and deleted the ubuntu partion from the windows device manager. It just displays "Booting from Live CD" for few minutes and again displyas the same above error.What should i do now?Its ok if i m not able to recover my data back...i hv sycnd my docs on the internet.
I newly installed debian squeeze with software raid. The way I did was, as also given in this thread.
- I have 2 HDD with 500 GB each. For each of them, I created 3 partitions (/boot, / and swap) - I selected the hard drive and created a new partition table - I created a new partition that was 1GB. I then specified to use the partition as a Physical Volume for RAID. and used for /boot and enabled bootable. - Created another partition, which is of 480 GB, and then specified to use the partition as a Physical Volume for RAID. and used for /. - Created another partion and used for swap
Then RAID configuration: Through Configure RAID menu -> create MD device -> (2 for the number of drives, 0 for spare devices) Next select the partitions you want to be members of /dev/MD0. I selected /dev/sda1 and /dev/sdb1 (for /boot) Next select the partitions you want to be members of /dev/MD1. I selected /dev/sda6 and /dev/sdb6 (for /) And no RAID for swap partitions
'Finish Partitioning and write changes to disk' --> Finish the rest of the install like normal. Everything is ok now, except I am not sure how to test my raid config. When I pull the power of the HDD, it only boots from one disk. I read in some forum that I may have to install GRUB manually on the other. In Debian Squeeze, there is no grub command. Not sure how to make my software raid bootable from both disk. I configured /boot partitions of both disks to be boot=yes. Not sure whether that is ok.