UPDATE: Got it sorted.Display All
- set params 'Debian GNU/Linux'
- insmod gzip
- if_[ x$grub_platform = xxen ]; then ismod xzio; ismod lzopio; fi
- ismod part_msdos
- ismod ext2
- set root='hd7,msdos1'
- if [ x$feature_platform_search_hint = xy ]; then
- search --no-floppy --fs-uuid --set-root --hint-bios=hd7,msdos1 --hint-efi=hd7,msdos1 --hint-baremetal=ahci7,msdos1 89cc63e0-dbae-427e-973e-411ab11bd160
- seach --no-floppy --fs-uuid --set-root 89cc63e0-dbae-427e-973e-411ab11bd160
- echo 'loading Linux 4.14.0-0.bpo.3-amd64 ...'
- linux /boot/vmlinuz-4.14.0-0.bpo.3-amd64 root=/dev/sdh1 ro quiet
- echo 'Loading initial ramdisk ...'
- initrd /boot/initrd.img-4.14.0-0.bpo.3-amd64
Boot up - when the terminal stops loading the error and gives you the mdadm prompt, type 'blkid'
This should show you all attached disks. You're looking for the one toward the bottom (arrarys/sata disk should be at top). For me it was a bit ambiguous - there were two that my boot USB could have been so I just remembered both (happened to be sdg1 and sdh1).
Reboot, and when you see the bluescrren GRUB hit 'e'
In the above code block change line #15 - so mine became 'root=/dev/sdg1'
Then hit F10 to boot. If it does, you've got the right one - if not, go back and try another disk name/id.
You should not have a 'login' prompt. Login in, then type 'update-grub'. This will make your change to the GRUB permanent.
Most of the above has been said in one form or anything by others, I just had trouble following it as a newb, so hopefully my elongated writeup will help another newb!
Yes, thank you for giving us the "long" version. Many times on the forums people say "do this, or do that", but without the foundation behind it, it's not helpful. For myself, I have rarely, if ever toyed with or modified grub.
A noob question though, how to issue the "blkid" command and get it to pause? I have 12 drives plus the boot drive on this system and the first items disappear off the screen pretty quickly.
you can just use blkid | moreI'm on Dialup !!!
I googled this issue and it brought me here, as I see this warning all the time now, not just at boot but any time I run package updates.
I also found another thread
which mentions using an edit in /etc/mdadm/mdadm.conf
ARRAY <ignore> devices=/dev/sda
as a solution. Anyone tried this? Seems pretty simple.
I had this exact same issue on my HP N40L microserver after I upgraded the boot HDD to an SSD (240GB).
I then partitioned the SDD (using gparted) and shrunk the boot partition to 20GB and created a data partition for the rest (minus a small Swap partition). So now I have 5 data HDD's plus one data partition on teh boot SSD.
On boot I now have 36 "mdadm: no arrays found in config file or automatically" messages taking around 40 secs and eventually boots.
The system is fine but those annoying messages delays the boot.
Lot of googling resulted in no good reason as to WHY.
In the end I "solved" (or got rid of those warnings) with the suggestion here.
Edited /etc/mdadm/mdadm.conf and added:
That is, one line of EACH drive.
and the, ran update-initramfs -u command
Now, after BIOS post, OMV boots in 30 secs.
(BTW,Adding just one line for/dev/sda did nothing.)HP Microserver N40L; OMV 4.1.18-2;
It might sound crazy but i did something and it worked for me.
Problem is caused by drives that changes paths after installation.
Using the CD drive as installation medium seems to work for few people.
What I did is, In Bios of my CPU, I have put the Sata Mode into IDE Mode instead of AHCI.
Then the problem disappeared and everything worked just fine.
Hope this helps.
Just adding _ I experienced the same thing just now installing 4.1.23-1 ( I am using a server that has limited SATA ports (everything is in a cage) and I wanted to use SSD drives for the OS outside of the cage). So I had to take the DVD drive stat port and use it for my SSD drive. Which in turn also forced me to use a USB thumbdrive to install the OS (from the OMV ISO) - OS installed fine, upon pulling the USB drive and rebooting - the server failed to boot giving the mdadm: no arrays found in config file - over and over again then dropping to initramfs prompt - there was also an error about /dev/sdj1 not exisiting.
While in initramfs I ran blkid which listed my boot drive as /dev/sdi1 so I rebooted, entered grub and edited the grub file and changed /dev/sji1 to /dev/sdi1 and it booted fine.
I use ZFS, so my next step after the clean boot was to change the kernel to a proxmox kernel any way, which I hoped should rewrite the Grub entries and possibly correct anything else. Added the proxmox kernel and rebooted again, worked fine - used the web interface to remove any other kernels and its running fine.
Kinda weird - didnt seem to happen when I ran the Debain 9 installer and then manually added OMV - only happened when I used the OMV ISO.
I'm guessing the installer told grub to write to the wrong disk. Installing the proxmox kernel would update that info. There isn't a good way to fix this other than exposing the menu in the installer that lets you pick the disk grub is installed on. But that may expose too much.
Its really odd - cause now that everything is up and running, the proxmox kernel is the boot, in omv web interface disks - the boot disk is /dev/sda - not sdj or sdi.
Is there any plan to fix this? I cannot install OMV 3 because half way through install it says it cannot connect. I cannot install 4 because of this issue and I cannot use 5 because there are no Extras etc.
Its really frustrating. I have aquired 4 new drives and wanted to put togther the final system config and cannot get anywhere. I tried FreeNAS which is soo complicated, I like OMV but I cannot use it!
For me, I think it was cleaner, easier and just worked out better to install Debian and then add OpenMediaVault. Things were getting squirrely when I used the OMV ISO and got worse when I tried to use the ISO from a thumb drive. If I recall correctly the issue was with drive labels switching around for some reason from /dev/sdi to dev/sdj - anyway I ended up just install Debian on the server, and got everything running how I wanted it (it was nice as well cause I could control the size of the boot partitions better than how it was getting calculated (I have large RAM, and was ending up with a very small boot partition).
couchpotatoes instructions but none of the listed drives works
Dont know about those steps, but this is what worked for me:
And I install Debian first, got everything as I wanted it - then used the steps to install OMV.
I finally got there. All I could do was pull all the other drives and do a clean install. Not ideal but it works now.
I thought I read somewhere that was the procedure? Nevertheless, glad ya got it going! So far I've been very happy with the move from freeBSD - and been very happy with the ZFS.