| View previous topic :: View next topic | |||||||||||||||||||
| Author | Message | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vesperto n00b 
Joined: 21 May 2015 |
|
||||||||||||||||||
| Back to top |
|
||||||||||||||||||
 |
|||||||||||||||||||
| Roman_Gruber Advocate 
Joined: 03 Oct 2006 |
|
||||||||||||||||||
| Back to top |
|
||||||||||||||||||
|
|||||||||||||||||||
| vesperto n00b
Joined: 21 May 2015 |
|
||||||||||||||||||
| Back to top |
|
||||||||||||||||||
|
|||||||||||||||||||
| Roman_Gruber Advocate
Joined: 03 Oct 2006 |
|
||||||||||||||||||
| Back to top |
|
||||||||||||||||||
|
|||||||||||||||||||
| vesperto n00b
Joined: 21 May 2015 |
|
||||||||||||||||||
| Back to top |
|
||||||||||||||||||
|
|||||||||||||||||||
| Roman_Gruber Advocate
Joined: 03 Oct 2006 |
|
||||||||||||||||||
| Back to top |
|
||||||||||||||||||
|
|||||||||||||||||||
| vesperto n00b
Joined: 21 May 2015 |
|
||||||||||||||||||
| Back to top |
|
||||||||||||||||||
|
|||||||||||||||||||
|
— Linux man page|
You cannot post new topics in this forum |
This tutorial is for all of us that has done everything by the book with parted and still they receive an error when installing grub2 to the boot sector!
srv@local ~ # grub2-install /dev/sda Installing for i386-pc platform. grub2-install: error: disk `mduuid/613f3f0bb202bf03a5664e17b3d568a0' not found.
The solution is relatively simple:
Boot from a rescue disk and reinstall grub from there!
The problem is that currently loaded kernel remembers the old device, which was deleted, and probably you won’t be able to fresh the metadata in the memory. In fact, if you receive this error when booted in a rescue disc you probably have done some changes on the layout of the disks or the partitions or the RAID devices and you must reboot the machine again and then JUST reinstall the grub.
Such problems could have happened if you deleted partitions or made some disk layout changes (using parted?) on mounted or partitions in use and the kernel could loaded the partition changes in memory. The parted reports the changes will take effect after system reboot.
STEP 1) Check the devices and mount the root and boot
They might be on the same device here they are on different MD devices (in the case, software array). md1 is the boot and md2 is the root.
root@rescue ~ # cat /proc/mdstat
Personalities : [raid1]
md3 : active raid1 sda5[3] sdb5[2]
422716416 blocks super 1.2 [2/2] [UU]
bitmap: 0/4 pages [0KB], 65536KB chunk
md2 : active raid1 sda3[3] sdb3[2]
31440896 blocks super 1.2 [2/2] [UU]
md1 : active raid1 sda2[3] sdb2[2]
523712 blocks super 1.2 [2/2] [UU]
md0 : active raid1 sda1[3] sdb1[2]
33521664 blocks super 1.2 [2/2] [UU]
unused devices: <none>
root@rescue ~ # mount /dev/md2 /mnt/
root@rescue ~ # mount /dev/md1 /mnt/boot/
root@rescue ~ # ls -altr /mnt/
total 396K
drwxr-xr-x. 2 root root 4.0K Apr 11 2018 srv
drwxr-xr-x. 2 root root 4.0K Apr 11 2018 opt
drwxr-xr-x. 2 root root 4.0K Apr 11 2018 mnt
drwxr-xr-x. 2 root root 4.0K Apr 11 2018 media
drwxr-xr-x. 2 root root 4.0K Apr 11 2018 home
lrwxrwxrwx. 1 root root 8 May 14 2018 sbin -> usr/sbin
lrwxrwxrwx. 1 root root 9 May 14 2018 lib64 -> usr/lib64
lrwxrwxrwx. 1 root root 7 May 14 2018 lib -> usr/lib
lrwxrwxrwx. 1 root root 7 May 14 2018 bin -> usr/bin
drwxr-xr-x. 13 root root 4.0K May 14 2018 usr
drwx------. 2 root root 16K Feb 12 2019 lost+found
drwxr-xr-x 2 root root 4.0K Feb 12 2019 boot
drwxr-xr-x 2 root root 4.0K Feb 12 2019 storage1
drwxr-xr-x 2 root root 4.0K Feb 12 2019 sys
drwxr-xr-x 2 root root 4.0K Feb 12 2019 dev
drwxr-xr-x 2 root root 4.0K Feb 12 2019 prochttps://www.google.com/search?client=firefox-b-d&q=samsung+tab10+2020
drwxr-xr-x 3 root root 4.0K Feb 12 2019 run
-rw-r-----. 1 root root 575 Feb 12 2019 installimage.conf
-rw-r-----. 1 root root 13K Feb 12 2019 installimage.debug
drwxr-xr-x. 20 root root 4.0K Feb 12 2019 var
drwxr-xr-x. 85 root root 4.0K Nov 2 2019 etc
-rw-r--r--. 1 root root 291K Nov 2 2019 .readahead
drwxr-xr-x. 19 root root 4.0K Nov 2 2019 .
dr-xr-x---. 6 root root 4.0K May 4 19:24 root
drwxrwxrwt. 7 root root 4.0K May 8 14:14 tmp
drwxr-xr-x 1 root root 160 May 8 16:57 ..
root@rescue ~ # ls -altr /mnt/boot/
total 194M
drwxr-xr-x. 3 root root 1.0K Sep 18 2017 efi
-rw-------. 1 root root 49M Sep 18 2017 initramfs-0-rescue-9063ac396d784f4c997ceacdd0590c25.img
-rwxr-xr-x. 1 root root 5.7M Sep 18 2017 vmlinuz-0-rescue-9063ac396d784f4c997ceacdd0590c25
-rw-------. 1 root root 3.4M Feb 1 2019 System.map-3.10.0-957.5.1.el7.x86_64
-rw-r--r--. 1 root root 149K Feb 1 2019 config-https://www.google.com/search?client=firefox-b-d&q=samsung+tab10+20203.10.0-957.5.1.el7.x86_64
-rw-r--r--. 1 root root 170 Feb 1 2019 .vmlinuz-3.10.0-957.5.1.el7.x86_64.hmac
-rwxr-xr-x. 1 root root 6.4M Feb 1 2019 vmlinuz-3.10.0-957.5.1.el7.x86_64
-rw-r--r--. 1 root root 307K Feb 1 2019 symvers-3.10.0-957.5.1.el7.x86_64.gz
drwx------. 2 root root 12K Feb 12 2019 lost+found
drwxr-xr-x. 2 root root 1.0K Feb 12 2019 grub
-rw-------. 1 root root 3.5M Oct 18 2019 System.map-3.10.0-1062.4.1.el7.x86_64
-rw-r--r--. 1 root root 150K Oct 18 2019 config-3.10.0-1062.4.1.el7.x86_64
-rw-r--r--. 1 root root 171 Oct 18 2019 .vmlinuz-3.10.0-1062.4.1.el7.x86_64.hmac
-rwxr-xr-x. 1 root root 6.5M Oct 18 2019 vmlinuz-3.10.0-1062.4.1.el7.x86_64
-rw-r--r--. 1 root root 312K Oct 18 2019 symvers-3.10.0-1062.4.1.el7.x86_64.gz
-rw-------. 1 root root 13M Nov 2 2019 initramfs-3.10.0-957.5.1.el7.x86_64kdump.img
-rw-------. 1 root root 47M Nov 2md 2019 initramfs-3.10.0-1062.4.1.el7.x86_64.img
-rw-------. 1 root root 46M Nov 2 2019 initramfs-3.10.0-957.5.1.el7.x86_64.img
-rw-------. 1 root root 13M Nov 2 2019 initramfs-3.10.0-1062.4.1.el7.x86_64kdump.img
dr-xr-xr-x. 6 root root 1.0K Nov 2 2019 .
drwxr-xr-x. 19 root root 4.0K Nov 2 2019 ..
drwx------. 5 root root 1.0K May 4 16:11 grub2
STEP 2) mount the dev, proc and sys relative to the root mount above and chroot in the root.
After chroot it is recommended to
root@rescue ~ # mount -o bind /dev /mnt/dev root@rescue ~ # mount -o bind /proc /mnt/proc root@rescue ~ # mount -o bind /sys /mnt/sys root@rescue ~ # chroot /mnt/ root@rescue / # cd root@rescue ~ # . /etc/profile
STEP 3)Install grub2
Unmount all mounted directories above and reboot.
root@rescue ~ # grub2-install /dev/sda Installing for i386-pc platform. Installation finished. No error reported. root@rescue ~ # grub2-install /dev/sdb Installing for i386-pc platform. Installation finished. No error reported. root@rescue ~ # exit root@rescue ~ # umount /mnt/boot root@rescue ~ # umount /mnt/dev root@rescue ~ # umount /mnt/proc root@rescue ~ # umount /mnt/sys root@rescue ~ # umount /mnt/ root@rescue ~ # reboot
* If you are using UEFI enabled boot you probably need more options for the grub installation
Something like that for the grub2 installation (but it is specific for your distro – the path for efi directory, just find it under /boot and put the right path – nothing special!):
grub-install --recheck --target=x86_64-efi --efi-directory=/boot/efi/ /dev/sda
Where does this error come from?
If you search the ID by part of it you will discover it under /dev/disk/by-id/, which is a link to md1, but still there is an error for missing device, because the kernel loaded the device as md-name-rescue:1. And if you reboot the kernel the old and wrong name won’t exists. As mentioned above this could have happened if you deleted partitions or made some disk layout changes (using parted?) on mounted or partitions in use and the kernel could loaded the partition changes.
[root@srv47 ~]# cd /dev/disk/by-id/ [root@srv47 by-id]# ls -altr total 0 drwxr-xr-x. 5 root root 100 4 May 9,14 .. lrwxrwxrwx. 1 root root 9 4 May 10,14 md-uuid-e4023626:e09f7c39:20ed5720:2ef1b5af -> ../../md0 lrwxrwxrwx. 1 root root 9 4 May 10,14 md-uuid-ae63857c:b8d537f5:4c09ae48:48148f59 -> ../../md3 lrwxrwxrwx. 1 root root 9 4 May 10,14 md-uuid-4a28f3a7:94dc6dc7:a40a7084:c21463d7 -> ../../md2 lrwxrwxrwx. 1 root root 9 4 May 10,14 md-name-rescue:3 -> ../../md3 lrwxrwxrwx. 1 root root 9 4 May 10,14 md-name-rescue:2 -> ../../md2 lrwxrwxrwx. 1 root root 9 4 May 10,14 md-name-rescue:0 -> ../../md0 lrwxrwxrwx. 1 root root 9 4 May 10,14 md-uuid-613f3f0b:b202bf03:a5664e17:b3d568a0 -> ../../md1 lrwxrwxrwx. 1 root root 9 4 May 10,14 md-name-rescue:1 -> ../../md1 drwxr-xr-x. 2 root root 680 4 May 12,16 . lrwxrwxrwx. 1 root root 9 8 May 12,01 wwn-0x500a075116bd3e33 -> ../../sda lrwxrwxrwx. 1 root root 9 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_171416BD3E33 -> ../../sda lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a075116bd3e33-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_171416BD3E33-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a075116bd3e33-part5 -> ../../sda5 lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a075116bd3e33-part4 -> ../../sda4 lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a075116bd3e33-part3 -> ../../sda3 lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a075116bd3e33-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_171416BD3E33-part5 -> ../../sda5 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_171416BD3E33-part4 -> ../../sda4 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_171416BD3E33-part3 -> ../../sda3 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_171416BD3E33-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 9 8 May 12,01 wwn-0x500a07511bb48b38 -> ../../sdb lrwxrwxrwx. 1 root root 9 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_18081BB48B38 -> ../../sdb lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a07511bb48b38-part5 -> ../../sdb5 lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a07511bb48b38-part4 -> ../../sdb4 lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a07511bb48b38-part3 -> ../../sdb3 lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a07511bb48b38-part2 -> ../../sdb2 lrwxrwxrwx. 1 root root 10 8 May 12,01 wwn-0x500a07511bb48b38-part1 -> ../../sdb1 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_18081BB48B38-part5 -> ../../sdb5 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_18081BB48B38-part4 -> ../../sdb4 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_18081BB48B38-part3 -> ../../sdb3 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_18081BB48B38-part2 -> ../../sdb2 lrwxrwxrwx. 1 root root 10 8 May 12,01 ata-Micron_1100_MTFDDAK512TBN_18081BB48B38-part1 -> ../../sdb1
-
-
May 25 2018, 19:25
- IT
- Технологии
- Cancel
Однажды я устанавливал Ubuntu Server 16 на старинную платформу IBM SR1500, на базе материнской платы Intel S5000PAL.
Sata-контроллер поддерживает только «fake-raid», я решил его включить, но выяснилось, что дистрибутив Ubuntu не содержит соответствующих драйверов. Тогда ничего не оставалось, как использовать программный массив mdadm. Во время процесса установки, установщик Linux предложил использовать уже имеющуюся разметку от Intel:
One or more drives containing MDADM containers (Intel/DDF RAID) have been found. Do you wish to activate these RAID devices?
Я согласился чтобы, не конфигурировать вручную(как выяснилось, это было большой ошибкой). Установщик смотнировал этот массив, установил все компонетны системы, но не смог установить grub.
После перезагрузки сервер отрапортовал, что загрузочных дисков не найдено.
На форме serverfault.com главным советом в таком случае была зачистка дисков от следов Intel DDF, с последующей полной переустановкой системы.
Я загрузился с live-CD, подмотировал raid и выполнил chroot, чтобы установить загрузчик самостоятельно.
Не повезло:
grub-install /dev/sda
grub-install: error: disk ‘mduuid/XXXXXXXX:XXXXXXXX:XXXXXXXX:XXXXXXXX’ not found
update-grub
grub-probe: error: disk ‘mduuid/XXXXXXXX:XXXXXXXX:XXXXXXXX:XXXXXXXX’ not found
Установка загрузчика не увенчалась успехом, зато загрузка дошла до стадии grub-консоли.
При вводе правильных параметров загрузки, система оказалась способной к запуску.
В моем случае команды выглядели так:
root (hd0,msdos1)
linux (hd0,msdos1)/boot/vmlinuz-4.4.0-116-generic root=/dev/md126p1 rw
initrd (hd0,msdos1)/boot/initrd.img-4.4.0-116-generic
Информацию по командам консоли grub2 найти не трудно, я хочу остановиться только на паметре ядра root, это путь к корневой директории, без него загрузка невозможна. Получается он так: в файле mdadm.conf установщик задал имя устройства dm-raid, у меня оно было md126, в файле fstab корневой раздел на массиве идет первым номером, значит имя блочного устройства корневого раздела будет /dev/md126p1.
Чтобы система могла загружаться самостоятельно, я создал вручную файл /boot/grub/grub.cfg на основе проверенных параметров загрузки:
set timeout=10
set default=0
menuentry «Ubuntu» {
root (hd0,msdos1)
linux (hd0,msdos1)/boot/vmlinuz-4.4.0-116-generic root=/dev/md126p1 rw
initrd (hd0,msdos1)/boot/initrd.img-4.4.0-116-generic
}
На всякий случай продублировал это содержимое в файле /boot/grub2/grub.cfg.
Все, этого оказалось достаточно для корректной загрузки.
П.С.
Через некоторое время мне пришлось заменить систему на Ubuntu 14 по причинам не связанным с загрузкой, заодно я очистил диски от разметки DDF, создал штатный soft-raid.
Кое-что по тематике использования DDF:
https://raid.wiki.kernel.org/index.php/DDF_Fake_RAID
Когда я писал этот пост нашел вот такое решение, и судя по всему, оно наиболее правильное, но возможности его проверить уже нет.
«Не удалось установить GRUB [РЕШЕНО]» http://forum.ubuntu.ru/index.php?topic=254351.0
GRUB2 boots, but gives «drive not found» error when attempting update
Server edition — Ubuntu 16.04, XFCE desktop
RAID 1 configuration with 1 hot spare — mdstat:Code:
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sda1[3] sdb1[4] sdc1[2](S) 14324 blocks super 1.2 [2/2] [UU] md1 : active raid1 sdc2[2](S) sda2[3] sdb2[4] 976745336 blocks super 1.2 [2/2] [UU] unused devices: <none>Today I updated the system in order to install about 3 months of updates, which froze halfway into the update (systemd? system-journal? something like that)— I didn’t write it down, figuring to re-boot and complete the upgrade. Long story short, the system took about 10 minutes to shut down, and upon reboot began to re-sync the RAID drives. I attempted the usual ‘sudo dpkg —configure -a’ to continue the upgrade, which worked, except for grub-pc and 3 other packages, which returned this worrying error message:
Code:
Setting up grub-pc (2.02~beta2-36ubuntu3.20) ... Generating grub configuration file ... grub-probe: error: disk `mduuid/0b332fe0048b87be574e721ad520ca94' not found. dpkg: error processing package grub-pc (--configure): subprocess installed post-installation script returned error exit status 1 Setting up friendly-recovery (0.2.31ubuntu2) ... Generating grub configuration file ... grub-probe: error: disk `mduuid/0b332fe0048b87be574e721ad520ca94' not found.If I try ‘sudo grub-probe /boot/grub’ on the identical (working) backup server, I get the response ‘ext2’ When I try it on this server I get the same error as when upgrading:
Code:
grub-probe: error: disk `mduuid/0b332fe0048b87be574e721ad520ca94' not found.Running ‘blkid’ gives the following output:
Code:
/dev/sda1: UUID="84fb6a65-5556-b6c4-3a00-42d3bdbbca0d" UUID_SUB="650b5441-ec83-1c59-a8fc-246c1acdeb7c" LABEL="drupal-server:0" TYPE="linux_raid_member" /dev/sda2: UUID="0b332fe0-048b-87be-574e-721ad520ca94" UUID_SUB="94674221-2a5f-f02d-c6dc-6c65f0fc0059" LABEL="drupal-server:1" TYPE="linux_raid_member" /dev/sdb1: UUID="84fb6a65-5556-b6c4-3a00-42d3bdbbca0d" UUID_SUB="a9d57793-f19c-4127-b9d0-ec81bd26eb4b" LABEL="drupal-server:0" TYPE="linux_raid_member" /dev/sdb2: UUID="0b332fe0-048b-87be-574e-721ad520ca94" UUID_SUB="d661c1db-8f1f-cf34-0587-0095b4950b7f" LABEL="drupal-server:1" TYPE="linux_raid_member" /dev/sdc1: UUID="84fb6a65-5556-b6c4-3a00-42d3bdbbca0d" UUID_SUB="be529f27-5b81-1915-a811-b47125255e7e" LABEL="drupal-server:0" TYPE="linux_raid_member" /dev/sdc2: UUID="0b332fe0-048b-87be-574e-721ad520ca94" UUID_SUB="1c2844c4-6988-3aee-c7b5-4ea1b611b8e5" LABEL="drupal-server:1" TYPE="linux_raid_member" /dev/md1: UUID="2db88bd0-5338-47d9-b766-5131a31b1716" TYPE="ext4" /dev/md0: UUID="08cb30f9-fdaf-4eb3-b85f-ed56835e41da" TYPE="swap"which tells me that the UUID for sda2 and sdb2 match what GRUB says it cannot find. When I checked the grub.cfg file, I found that the system had attempted to create a new file, but failed with a truncated version (grub.cfg.new) that never got re-named to grub.cfg. Here is a snippet from the beginning of the old (working) grub.cfg
Code:
set root='mduuid/0b332fe0048b87be574e721ad520ca94' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/0b332fe0048b87be574e721ad520ca94' 2db88bd0-5338-47d9-b766-5131a31b1716 else search --no-floppy --fs-uuid --set=root 2db88bd0-5338-47d9-b766-5131a31b1716And finally, (with apologies for the length) here are the results of running the BootInfo script:
Code:
Boot Info Script 0.61 [1 April 2012] ============================= Boot Info Summary: =============================== => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of the same hard drive for core.img. core.img is at this location and looks in partition 112 for . => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of the same hard drive for core.img. core.img is at this location and looks in partition 97 for . => Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of the same hard drive for core.img. core.img is at this location and looks in partition 97 for . sda1: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sda2: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb1: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb2: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc1: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc2: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: md/1: __________________________________________________________________________ File system: ext4 Boot sector type: - Boot sector info: Mounting failed: mount: /dev/md1 is already mounted or /tmp/BootInfo-Z3rZ3W1z/MDRaid/md/1 busy /dev/md1 is already mounted on / md/0: __________________________________________________________________________ File system: swap Boot sector type: - Boot sector info: ============================ Drive/Partition Info: ============================= Drive: sda _____________________________________________________________________ Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Partition Boot Start Sector End Sector # of Sectors Id System /dev/sda1 2,048 30,719 28,672 fd Linux raid autodetect /dev/sda2 * 30,720 1,953,523,711 1,953,492,992 fd Linux raid autodetect Drive: sdb _____________________________________________________________________ Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Partition Boot Start Sector End Sector # of Sectors Id System /dev/sdb1 2,048 30,719 28,672 fd Linux raid autodetect /dev/sdb2 * 30,720 1,953,523,711 1,953,492,992 fd Linux raid autodetect Drive: sdc _____________________________________________________________________ Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Partition Boot Start Sector End Sector # of Sectors Id System /dev/sdc1 2,048 30,719 28,672 fd Linux raid autodetect /dev/sdc2 * 30,720 1,953,523,711 1,953,492,992 fd Linux raid autodetect "blkid" output: ________________________________________________________________ Device UUID TYPE LABEL /dev/md0 08cb30f9-fdaf-4eb3-b85f-ed56835e41da swap /dev/md1 2db88bd0-5338-47d9-b766-5131a31b1716 ext4 /dev/sda1 84fb6a65-5556-b6c4-3a00-42d3bdbbca0d linux_raid_member drupal-server:0 /dev/sda2 0b332fe0-048b-87be-574e-721ad520ca94 linux_raid_member drupal-server:1 /dev/sdb1 84fb6a65-5556-b6c4-3a00-42d3bdbbca0d linux_raid_member drupal-server:0 /dev/sdb2 0b332fe0-048b-87be-574e-721ad520ca94 linux_raid_member drupal-server:1 /dev/sdc1 84fb6a65-5556-b6c4-3a00-42d3bdbbca0d linux_raid_member drupal-server:0 /dev/sdc2 0b332fe0-048b-87be-574e-721ad520ca94 linux_raid_member drupal-server:1 ================================ Mount points: ================================= Device Mount_Point Type Options /dev/md1 / ext4 (rw,relatime,errors=remount-ro,data=ordered)So there appears to be an error — «Mounting failed: mount: /dev/md1 is already mounted or /tmp/BootInfo-Z3rZ3W1z/MDRaid/md/1 busy
/dev/md1 is already mounted on /» unless this is an error caused by running the script from within an already mounted drive rather than from a USB or repair disk.Many, many thanks for anyone who can point me towards a solution.
Best
Darrell Eifert
Lane Memorial Library
Hampton, NH
I just installed Arch on my shiny new ASUS Zenbook Pro UX501VW-DS71T but I can’t boot it 
. Grub is complaining with:
Welcome to grub
error: disk `' not found.
Entering rescue mode...
grub rescue> _I installed grub (from within my arch-chroot, with my EFI system partition mounted at /boot) with:
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub
grub-mkconfig -o /boot/grub/grub.cfgI made sure that everything looks good on my /boot partition. I see my vmlinux and initrd there as usual. I also verified that the UUID in my grub.cfg matches the one where my arch install lives.
Any ideas what could be going wrong here? I’ve tried re-installing and re-configuring grub several times. I’ve even tried re-installing everything from scratch again, but I get the same error message and grub rescue prompt.
Here’s the output of blkid (EFI system partition is on /dev/nvme0n1p1, Arch is on /dev/nvme0n1p5):
/dev/nvme0n1p1: LABEL="SYSTEM" UUID="DABA-72EF" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="fccfcb65-5287-4e24-909f-5b71ce084288"
/dev/nvme0n1p3: UUID="0666BC2966BC1AFF" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="bc9fc29c-277a-4c28-ad90-1f1870f8a70c"
/dev/nvme0n1p4: LABEL="RECOVERY" UUID="A6F0842AF0840333" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="183a2fd6-1755-4091-8df0-134f04769289"
/dev/nvme0n1p5: UUID="2873ccb1-735c-497f-ae0b-70b28f5b8809" TYPE="ext4" PARTLABEL="arch" PARTUUID="209c0fe6-da26-43b1-91d9-54e809f24356"
/dev/sda1: LABEL="ARCH_201605" UUID="E4EE-AB4E" TYPE="vfat" PARTLABEL="Microsoft Basic Data" PARTUUID="348adda9-6284-4e05-9718-18b23b9373ac"
/dev/loop0: TYPE="squashfs"
/dev/nvme0n1: PTUUID="d56f1514-5d43-4d70-8bf2-cda5d875f710" PTTYPE="gpt"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="d2ebf45d-4fd3-41a5-8b86-efac9f56f382"Here’s my full grub.cfg:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root 2873ccb1-735c-497f-ae0b-70b28f5b8809
else
search --no-floppy --fs-uuid --set=root 2873ccb1-735c-497f-ae0b-70b28f5b8809
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2873ccb1-735c-497f-ae0b-70b28f5b8809' {
load_video
set gfxpayload=keep
insmod gzio
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root DABA-72EF
else
search --no-floppy --fs-uuid --set=root DABA-72EF
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=2873ccb1-735c-497f-ae0b-70b28f5b8809 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
}
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-2873ccb1-735c-497f-ae0b-70b28f5b8809' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-2873ccb1-735c-497f-ae0b-70b28f5b8809' {
load_video
set gfxpayload=keep
insmod gzio
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root DABA-72EF
else
search --no-floppy --fs-uuid --set=root DABA-72EF
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=2873ccb1-735c-497f-ae0b-70b28f5b8809 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
}
menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-2873ccb1-735c-497f-ae0b-70b28f5b8809' {
load_video
set gfxpayload=keep
insmod gzio
insmod fat
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root DABA-72EF
else
search --no-floppy --fs-uuid --set=root DABA-72EF
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=2873ccb1-735c-497f-ae0b-70b28f5b8809 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###Last edited by mitch_feaster (2016-05-12 15:39:56)
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
/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
Total Devices : 14
Persistence : Superblock is persistent
Update Time : Thu Sep 18 19:44:56 2014
State : clean
Active Devices : 14
Working Devices : 14
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : media:0 (local to host media)
UUID : b1c40379:914e5d18:dddb893b:4dc5a28f
Events : 2319862
Number Major Minor RaidDevice State
13 8 82 0 active sync /dev/sdf2
15 8 130 1 active sync /dev/sdi2
14 8 98 2 active sync /dev/sdg2
21 8 194 3 active sync /dev/sdm2
16 8 226 4 active sync /dev/sdo2
12 8 162 5 active sync /dev/sdk2
18 8 50 6 active sync /dev/sdd2
17 8 146 7 active sync /dev/sdj2
20 8 210 8 active sync /dev/sdn2
19 8 66 9 active sync /dev/sde2
11 8 34 10 active sync /dev/sdc2
24 8 178 11 active sync /dev/sdl2
23 8 114 12 active sync /dev/sdh2
22 8 18 13 active sync /dev/sdb2
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"
/dev/sdc2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="ce717500-cadf-3b12-e893-48d43c1408e7" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdf2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="071afb12-f78f-4f15-f65a-a6298eadcfa7" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdb2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="822fd02b-454d-a94c-57f6-8535964996b1" LABEL="media:0" TYPE="linux_raid_member"
/dev/sde2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="de3f41b8-3016-870c-344f-2a92c08e1085" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdg2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="e319bdaa-22bc-1153-c43b-48788a9c1832" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdi2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="3dd1df1b-203c-6453-0964-ebad245b1670" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdh2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="f5477580-9435-7948-6e97-fe82c8805bcd" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdj2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="4a013330-37c5-65f9-cb76-1d357ce4ddb4" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdm2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="b750b4e4-2b1b-ac5f-cbd3-bde5eab657e7" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdk2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="d5521994-6c4f-04f9-f7ca-0dd9dff3c6cd" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdn2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="4670b36c-07cb-e661-20e3-d314f7c3fd42" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdl2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="c1514b9f-2461-6fed-324a-50fb9469043a" LABEL="media:0" TYPE="linux_raid_member"
/dev/sdo2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="6c33c472-af1f-fd8f-22d1-0ea39edc75bb" 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:**
http://pastebin.com/bPgGN68L
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.
**EDIT TO ADD**
I don’t have IPMI on this box so please forgive the embarrassing cell phone phone picture:
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.