Linux Distributions
--
Questions
--
Followers
Top Experts
Ubuntu 14.04.5 LTS hangs at verifying dmi pool data
I've got a 14.04.5 system that had a drive fail in the RAID-5.
I've recovered the RAID-5 and its fully intact when I bring it up with SystemRescueCD here.
When I try to boot to Hard DIsk however the systems feezes at "verifying dmi pool data"
I've worked through the following articles to recover this with no success. It seems that it runs each recovery step but its still not booting after trying the recovery techniques. I'd love to run the Boot-Repair option but its an older system and apparently cant handle the graphics and trying to run it locks up the machine. Is there a command line way to run Boot-Repair??
Any help apperciated as this is a bckup email/app server. If I HAVE to rebuild it I can it would be just much easier to recover it since it seems like it's just about done.
The boot drive is /dev/sda with /boot on /dev/sda1 and the other 2 RIAD5 volumes are /dev/sdb and /dev/sdc. I've done the install of Boot Record on each and update-grub with no benefit. Still hangs. There are also a pair of External USB Hard Drives /dev/sdd and /dev/sde.
https://ubuntuforums.org/showthread.php?t=1635369
https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows
https://help.ubuntu.com/community/Grub2/Installing#Fixing_a_Broken_System
http://unix.stackexchange.com/questions/159118/using-bash-environment-from-an-external-os-partition
I've recovered the RAID-5 and its fully intact when I bring it up with SystemRescueCD here.
When I try to boot to Hard DIsk however the systems feezes at "verifying dmi pool data"
I've worked through the following articles to recover this with no success. It seems that it runs each recovery step but its still not booting after trying the recovery techniques. I'd love to run the Boot-Repair option but its an older system and apparently cant handle the graphics and trying to run it locks up the machine. Is there a command line way to run Boot-Repair??
Any help apperciated as this is a bckup email/app server. If I HAVE to rebuild it I can it would be just much easier to recover it since it seems like it's just about done.
The boot drive is /dev/sda with /boot on /dev/sda1 and the other 2 RIAD5 volumes are /dev/sdb and /dev/sdc. I've done the install of Boot Record on each and update-grub with no benefit. Still hangs. There are also a pair of External USB Hard Drives /dev/sdd and /dev/sde.
https://ubuntuforums.org/showthread.php?t=1635369
https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows
https://help.ubuntu.com/community/Grub2/Installing#Fixing_a_Broken_System
http://unix.stackexchange.com/questions/159118/using-bash-environment-from-an-external-os-partition
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Odd I just put a comment in and it isn't here. One more try.
Anyone want to tackle this? The data is intact - we can see and work with it on a SystemRescueCD with its mdadm to mount the RAID and we can mount /boot (/dev/sda1). We just can't get past the hang.
Anyone want to tackle this? The data is intact - we can see and work with it on a SystemRescueCD with its mdadm to mount the RAID and we can mount /boot (/dev/sda1). We just can't get past the hang.
Which drive failed that made up the raid5 and was replaced. Â When the drive failed for raid 5, did the system continue to run?
What steps were taken when the failure was discovered to remedy the situations?
Might it be that the wrong drive was placed in the sda position.
Using parted/fdisk/cfdisk which drive is marked as active for bootup?
Which volume does /boot/grub/grub.conf on the internal drives?
What steps were taken when the failure was discovered to remedy the situations?
Might it be that the wrong drive was placed in the sda position.
Using parted/fdisk/cfdisk which drive is marked as active for bootup?
Which volume does /boot/grub/grub.conf on the internal drives?
Check whether the delay relates to the USB drives, if they are not necessary for booting, remove the USB devices....
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Which drive failed that made up the raid5 and was replaced. Â /dev/sdc
 When the drive failed for raid 5, did the system continue to run? yes without any issues
What steps were taken when the failure was discovered to remedy the situations? obtained new disk overnight, shut down cleanly replaced hardware (mdadm showed that the /dec/sdc had failed out - attempts to resync it failed and we obtained the new disk overnight.
Might it be that the wrong drive was placed in the sda position. No fdisk shows /dec/sda correctly with the /boot on /dev/sda1 and
Using parted/fdisk/cfdisk which drive is marked as active for bootup?
Which volume does /boot/grub/grub.conf on the internal drives? /dev/sda1
Removing the 5TB and 1TB USB external disks gives gets a grub boot prompt up
I'm attaching grub.conf and a directory of boot below which looks odd as there is a boot directory under boot....
 When the drive failed for raid 5, did the system continue to run? yes without any issues
What steps were taken when the failure was discovered to remedy the situations? obtained new disk overnight, shut down cleanly replaced hardware (mdadm showed that the /dec/sdc had failed out - attempts to resync it failed and we obtained the new disk overnight.
Might it be that the wrong drive was placed in the sda position. No fdisk shows /dec/sda correctly with the /boot on /dev/sda1 and
Using parted/fdisk/cfdisk which drive is marked as active for bootup?
Which volume does /boot/grub/grub.conf on the internal drives? /dev/sda1
% fdisk -l
Disk /dev/loop0: 357.3 MiB, 374689792 bytes, 731816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000782ed
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1955172 1953125 953.7M 83 Linux
/dev/sda2 1955840 9766911 7811072 3.7G 82 Linux swap / Solaris
/dev/sda3 9768958 586072063 576303106 274.8G 5 Extended
/dev/sda5 9768960 586072063 576303104 274.8G fd Linux raid autodetect
Disk /dev/sdb: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0000a484
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 625141759 625139712 298.1G fd Linux raid autodetect
Disk /dev/sdc: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xbbb69ef5
Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 625142447 625140400 298.1G fd Linux raid autodetect
Disk /dev/md0: 549.4 GiB, 589864894464 bytes, 1152079872 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytesRemoving the 5TB and 1TB USB external disks gives gets a grub boot prompt up
I'm attaching grub.conf and a directory of boot below which looks odd as there is a boot directory under boot....
root@sysresccd /mnt/raid % ll boot
total 16K
drwxr-xr-x 4 root root 4.0K Jan 6 06:42 .
drwxr-xr-x 24 root root 4.0K Oct 29 22:47 ..
drwxr-xr-x 3 root root 4.0K Jan 6 06:34 boot
drwxr-xr-x 5 root root 4.0K Jan 6 06:43 grub
root@sysresccd /mnt/raid % ll boot/boot
total 12K
drwxr-xr-x 3 root root 4.0K Jan 6 06:34 .
drwxr-xr-x 4 root root 4.0K Jan 6 06:42 ..
drwxr-xr-x 2 root root 4.0K Jan 6 06:34 grub
root@sysresccd /mnt/raid % ll boot/boot/grub
total 252K
drwxr-xr-x 2 root root 4.0K Jan 6 06:34 .
drwxr-xr-x 3 root root 4.0K Jan 6 06:34 ..
-rw-r--r-- 1 root root 197 Jan 6 06:34 default
-rw-r--r-- 1 root root 90 Jan 6 06:34 device.map
-rw-r--r-- 1 root root 9.8K Jan 6 06:34 e2fs_stage1_5
-rw-r--r-- 1 root root 9.0K Jan 6 06:34 fat_stage1_5
-rw-r--r-- 1 root root 8.4K Jan 6 06:34 ffs_stage1_5
-rw-r--r-- 1 root root 8.4K Jan 6 06:34 iso9660_stage1_5
-rw-r--r-- 1 root root 10K Jan 6 06:34 jfs_stage1_5
-rw-r--r-- 1 root root 8.5K Jan 6 06:34 minix_stage1_5
-rw-r--r-- 1 root root 11K Jan 6 06:34 reiserfs_stage1_5
-rw-r--r-- 1 root root 512 Jan 6 06:34 stage1
-rw-r--r-- 1 root root 116K Jan 6 06:35 stage2
-rw-r--r-- 1 root root 8.7K Jan 6 06:34 ufs2_stage1_5
-rw-r--r-- 1 root root 8.0K Jan 6 06:34 vstafs_stage1_5
-rw-r--r-- 1 root root 11K Jan 6 06:34 xfs_stage1_5
root@sysresccd /mnt/raid % ll boot/grub
total 36K
drwxr-xr-x 5 root root 4.0K Jan 6 06:43 .
drwxr-xr-x 4 root root 4.0K Jan 6 06:42 ..
drwxr-xr-x 2 root root 4.0K Jan 6 06:42 fonts
-r--r--r-- 1 root root 3.8K Jan 6 06:43 grub.cfg
-rw-r--r-- 1 root root 1.0K Jan 6 06:42 grubenv
drwxr-xr-x 2 root root 12K Jan 6 06:43 i386-pc
drwxr-xr-x 2 root root 4.0K Jan 6 06:43 locale
root@sysresccd /mnt/raid % ll boot/grub/fonts
total 2.4M
drwxr-xr-x 2 root root 4.0K Jan 6 06:42 .
drwxr-xr-x 5 root root 4.0K Jan 6 06:43 ..
-rw-r--r-- 1 root root 2.3M Jan 6 06:43 unicode.pf2
root@sysresccd /mnt/raid % ll boot/grub/i386-pc
total 2.4M
drwxr-xr-x 2 root root 12K Jan 6 06:43 .
drwxr-xr-x 5 root root 4.0K Jan 6 06:43 ..
-rw-r--r-- 1 root root 7.8K Jan 6 06:43 915resolution.mod
-rw-r--r-- 1 root root 9.8K Jan 6 06:43 acpi.mod
-rw-r--r-- 1 root root 1.3K Jan 6 06:43 adler32.mod
-rw-r--r-- 1 root root 5.7K Jan 6 06:43 affs.mod
-rw-r--r-- 1 root root 6.6K Jan 6 06:43 afs.mod
-rw-r--r-- 1 root root 16K Jan 6 06:43 ahci.mod
-rw-r--r-- 1 root root 701 Jan 6 06:43 all_video.mod
-rw-r--r-- 1 root root 1.1K Jan 6 06:43 aout.mod
-rw-r--r-- 1 root root 2.9K Jan 6 06:43 archelp.mod
-rw-r--r-- 1 root root 5.6K Jan 6 06:43 ata.mod
-rw-r--r-- 1 root root 4.2K Jan 6 06:43 at_keyboard.mod
-rw-r--r-- 1 root root 1.6K Jan 6 06:43 backtrace.mod
-rw-r--r-- 1 root root 7.1K Jan 6 06:43 bfs.mod
-rw-r--r-- 1 root root 4.6K Jan 6 06:43 biosdisk.mod
-rw-r--r-- 1 root root 2.2K Jan 6 06:43 bitmap.mod
-rw-r--r-- 1 root root 3.6K Jan 6 06:43 bitmap_scale.mod
-rw-r--r-- 1 root root 2.2K Jan 6 06:43 blocklist.mod
-rw-r--r-- 1 root root 512 Jan 6 06:43 boot.img
-rw-r--r-- 1 root root 2.4K Jan 6 06:43 boot.mod
-rw-r--r-- 1 root root 30K Jan 6 06:43 bsd.mod
-rw-r--r-- 1 root root 15K Jan 6 06:43 btrfs.mod
-rw-r--r-- 1 root root 2.1K Jan 6 06:43 bufio.mod
-rw-r--r-- 1 root root 2.9K Jan 6 06:43 cat.mod
-rw-r--r-- 1 root root 3.7K Jan 6 06:43 cbfs.mod
-rw-r--r-- 1 root root 3.5K Jan 6 06:43 cbls.mod
-rw-r--r-- 1 root root 2.4K Jan 6 06:43 cbmemc.mod
-rw-r--r-- 1 root root 1.1K Jan 6 06:43 cbtable.mod
-rw-r--r-- 1 root root 2.5K Jan 6 06:43 cbtime.mod
-rw-r--r-- 1 root root 3.5K Jan 6 06:43 chain.mod
-rw-r--r-- 1 root root 3.0K Jan 6 06:43 cmdline_cat_test.mod
-rw-r--r-- 1 root root 1.2K Jan 6 06:43 cmosdump.mod
-rw-r--r-- 1 root root 1.8K Jan 6 06:43 cmostest.mod
-rw-r--r-- 1 root root 2.0K Jan 6 06:43 cmp.mod
-rw-r--r-- 1 root root 3.8K Jan 6 06:43 command.lst
-rw-r--r-- 1 root root 2.3K Jan 6 06:43 configfile.mod
-rw-r--r-- 1 root root 30K Jan 6 06:43 core.img
-rw-r--r-- 1 root root 2.7K Jan 6 06:43 cpio_be.mod
-rw-r--r-- 1 root root 2.6K Jan 6 06:43 cpio.mod
-rw-r--r-- 1 root root 1.7K Jan 6 06:43 cpuid.mod
-rw-r--r-- 1 root root 1.7K Jan 6 06:43 crc64.mod
-rw-r--r-- 1 root root 9.8K Jan 6 06:43 cryptodisk.mod
-rw-r--r-- 1 root root 936 Jan 6 06:43 crypto.lst
-rw-r--r-- 1 root root 4.9K Jan 6 06:43 crypto.mod
-rw-r--r-- 1 root root 3.9K Jan 6 06:43 cs5536.mod
-rw-r--r-- 1 root root 1.8K Jan 6 06:43 datehook.mod
-rw-r--r-- 1 root root 2.2K Jan 6 06:43 date.mod
-rw-r--r-- 1 root root 1.3K Jan 6 06:43 datetime.mod
-rw-r--r-- 1 root root 9.6K Jan 6 06:43 diskfilter.mod
-rw-r--r-- 1 root root 2.4K Jan 6 06:43 disk.mod
-rw-r--r-- 1 root root 3.8K Jan 6 06:43 div_test.mod
-rw-r--r-- 1 root root 1.8K Jan 6 06:43 dm_nv.mod
-rw-r--r-- 1 root root 5.3K Jan 6 06:43 drivemap.mod
-rw-r--r-- 1 root root 2.0K Jan 6 06:43 echo.mod
-rw-r--r-- 1 root root 7.3K Jan 6 06:43 efiemu32.o
-rw-r--r-- 1 root root 12K Jan 6 06:43 efiemu64.o
-rw-r--r-- 1 root root 24K Jan 6 06:43 efiemu.mod
-rw-r--r-- 1 root root 16K Jan 6 06:43 ehci.mod
-rw-r--r-- 1 root root 5.0K Jan 6 06:43 elf.mod
-rw-r--r-- 1 root root 1.5K Jan 6 06:43 eval.mod
-rw-r--r-- 1 root root 5.4K Jan 6 06:43 exfat.mod
-rw-r--r-- 1 root root 1.5K Jan 6 06:43 exfctest.mod
-rw-r--r-- 1 root root 5.5K Jan 6 06:43 ext2.mod
-rw-r--r-- 1 root root 4.5K Jan 6 06:43 extcmd.mod
-rw-r--r-- 1 root root 5.5K Jan 6 06:43 fat.mod
-rw-r--r-- 1 root root 16K Jan 6 06:43 file.mod
-rw-r--r-- 1 root root 13K Jan 6 06:43 font.mod
-rw-r--r-- 1 root root 2.7K Jan 6 06:43 freedos.mod
-rw-r--r-- 1 root root 2.6K Jan 6 06:43 fshelp.mod
-rw-r--r-- 1 root root 214 Jan 6 06:43 fs.lst
-rw-r--r-- 1 root root 88K Jan 6 06:43 functional_test.mod
-rw-r--r-- 1 root root 1.6K Jan 6 06:43 gcry_arcfour.mod
-rw-r--r-- 1 root root 8.0K Jan 6 06:43 gcry_blowfish.mod
-rw-r--r-- 1 root root 34K Jan 6 06:43 gcry_camellia.mod
-rw-r--r-- 1 root root 17K Jan 6 06:43 gcry_cast5.mod
-rw-r--r-- 1 root root 2.9K Jan 6 06:43 gcry_crc.mod
-rw-r--r-- 1 root root 19K Jan 6 06:43 gcry_des.mod
-rw-r--r-- 1 root root 2.3K Jan 6 06:43 gcry_dsa.mod
-rw-r--r-- 1 root root 3.0K Jan 6 06:43 gcry_idea.mod
-rw-r--r-- 1 root root 3.1K Jan 6 06:43 gcry_md4.mod
-rw-r--r-- 1 root root 3.7K Jan 6 06:43 gcry_md5.mod
-rw-r--r-- 1 root root 2.5K Jan 6 06:43 gcry_rfc2268.mod
-rw-r--r-- 1 root root 19K Jan 6 06:43 gcry_rijndael.mod
-rw-r--r-- 1 root root 8.0K Jan 6 06:43 gcry_rmd160.mod
-rw-r--r-- 1 root root 2.1K Jan 6 06:43 gcry_rsa.mod
-rw-r--r-- 1 root root 16K Jan 6 06:43 gcry_seed.mod
-rw-r--r-- 1 root root 16K Jan 6 06:43 gcry_serpent.mod
-rw-r--r-- 1 root root 7.3K Jan 6 06:43 gcry_sha1.mod
-rw-r--r-- 1 root root 4.3K Jan 6 06:43 gcry_sha256.mod
-rw-r--r-- 1 root root 7.9K Jan 6 06:43 gcry_sha512.mod
-rw-r--r-- 1 root root 13K Jan 6 06:43 gcry_tiger.mod
-rw-r--r-- 1 root root 39K Jan 6 06:43 gcry_twofish.mod
-rw-r--r-- 1 root root 25K Jan 6 06:43 gcry_whirlpool.mod
-rw-r--r-- 1 root root 25K Jan 6 06:43 gdb.mod
-rw-r--r-- 1 root root 5.8K Jan 6 06:43 geli.mod
-rw-r--r-- 1 root root 4.9K Jan 6 06:43 gettext.mod
-rw-r--r-- 1 root root 39K Jan 6 06:43 gfxmenu.mod
-rw-r--r-- 1 root root 2.8K Jan 6 06:43 gfxterm_background.mod
-rw-r--r-- 1 root root 5.0K Jan 6 06:43 gfxterm_menu.mod
-rw-r--r-- 1 root root 9.8K Jan 6 06:43 gfxterm.mod
-rw-r--r-- 1 root root 3.7K Jan 6 06:43 gptsync.mod
-rw-r--r-- 1 root root 8.1K Jan 6 06:43 gzio.mod
-rw-r--r-- 1 root root 4.3K Jan 6 06:43 halt.mod
-rw-r--r-- 1 root root 5.1K Jan 6 06:43 hashsum.mod
-rw-r--r-- 1 root root 7.1K Jan 6 06:43 hdparm.mod
-rw-r--r-- 1 root root 1.2K Jan 6 06:43 hello.mod
-rw-r--r-- 1 root root 2.6K Jan 6 06:43 help.mod
-rw-r--r-- 1 root root 3.1K Jan 6 06:43 hexdump.mod
-rw-r--r-- 1 root root 7.0K Jan 6 06:43 hfs.mod
-rw-r--r-- 1 root root 2.9K Jan 6 06:43 hfspluscomp.mod
-rw-r--r-- 1 root root 7.4K Jan 6 06:43 hfsplus.mod
-rw-r--r-- 1 root root 5.5K Jan 6 06:43 http.mod
-rw-r--r-- 1 root root 47K Jan 6 06:43 hwmatch.mod
-rw-r--r-- 1 root root 2.8K Jan 6 06:43 iorw.mod
-rw-r--r-- 1 root root 8.5K Jan 6 06:43 iso9660.mod
-rw-r--r-- 1 root root 6.1K Jan 6 06:43 jfs.mod
-rw-r--r-- 1 root root 6.1K Jan 6 06:43 jpeg.mod
-rw-r--r-- 1 root root 4.9K Jan 6 06:43 keylayouts.mod
-rw-r--r-- 1 root root 2.0K Jan 6 06:43 keystatus.mod
-rw-r--r-- 1 root root 6.8K Jan 6 06:43 ldm.mod
-rw-r--r-- 1 root root 30K Jan 6 06:43 legacycfg.mod
-rw-r--r-- 1 root root 15K Jan 6 06:43 legacy_password_test.mod
-rw-r--r-- 1 root root 7.8K Jan 6 06:43 linux16.mod
-rw-r--r-- 1 root root 13K Jan 6 06:43 linux.mod
-rw-r--r-- 1 root root 5.8K Jan 6 06:43 loadenv.mod
-rw-r--r-- 1 root root 3.0K Jan 6 06:43 loopback.mod
-rw-r--r-- 1 root root 4.7K Jan 6 06:43 lsacpi.mod
-rw-r--r-- 1 root root 2.3K Jan 6 06:43 lsapm.mod
-rw-r--r-- 1 root root 1.8K Jan 6 06:43 lsmmap.mod
-rw-r--r-- 1 root root 4.0K Jan 6 06:43 ls.mod
-rw-r--r-- 1 root root 4.8K Jan 6 06:43 lspci.mod
-rw-r--r-- 1 root root 6.6K Jan 6 06:43 luks.mod
-rw-r--r-- 1 root root 6.7K Jan 6 06:43 lvm.mod
-rw-r--r-- 1 root root 8.5K Jan 6 06:43 lzopio.mod
-rw-r--r-- 1 root root 3.3K Jan 6 06:43 macbless.mod
-rw-r--r-- 1 root root 7.4K Jan 6 06:43 macho.mod
-rw-r--r-- 1 root root 2.0K Jan 6 06:43 mda_text.mod
-rw-r--r-- 1 root root 2.0K Jan 6 06:43 mdraid09_be.mod
-rw-r--r-- 1 root root 2.0K Jan 6 06:43 mdraid09.mod
-rw-r--r-- 1 root root 2.0K Jan 6 06:43 mdraid1x.mod
-rw-r--r-- 1 root root 2.0K Jan 6 06:43 memdisk.mod
-rw-r--r-- 1 root root 2.8K Jan 6 06:43 memrw.mod
-rw-r--r-- 1 root root 3.4K Jan 6 06:43 minicmd.mod
-rw-r--r-- 1 root root 3.7K Jan 6 06:43 minix2_be.mod
-rw-r--r-- 1 root root 3.5K Jan 6 06:43 minix2.mod
-rw-r--r-- 1 root root 3.7K Jan 6 06:43 minix3_be.mod
-rw-r--r-- 1 root root 3.5K Jan 6 06:43 minix3.mod
-rw-r--r-- 1 root root 3.6K Jan 6 06:43 minix_be.mod
-rw-r--r-- 1 root root 3.5K Jan 6 06:43 minix.mod
-rw-r--r-- 1 root root 8.4K Jan 6 06:43 mmap.mod
-rw-r--r-- 1 root root 5.1K Jan 6 06:43 moddep.lst
-rw-r--r-- 1 root root 2.3K Jan 6 06:43 modinfo.sh
-rw-r--r-- 1 root root 2.4K Jan 6 06:43 morse.mod
-rw-r--r-- 1 root root 28K Jan 6 06:43 mpi.mod
-rw-r--r-- 1 root root 2.4K Jan 6 06:43 msdospart.mod
-rw-r--r-- 1 root root 13K Jan 6 06:43 multiboot2.mod
-rw-r--r-- 1 root root 13K Jan 6 06:43 multiboot.mod
-rw-r--r-- 1 root root 4.0K Jan 6 06:43 nativedisk.mod
-rw-r--r-- 1 root root 46K Jan 6 06:43 net.mod
-rw-r--r-- 1 root root 2.9K Jan 6 06:43 newc.mod
-rw-r--r-- 1 root root 6.6K Jan 6 06:43 nilfs2.mod
-rw-r--r-- 1 root root 114K Jan 6 06:43 normal.mod
-rw-r--r-- 1 root root 4.3K Jan 6 06:43 ntfscomp.mod
-rw-r--r-- 1 root root 9.7K Jan 6 06:43 ntfs.mod
-rw-r--r-- 1 root root 2.5K Jan 6 06:43 ntldr.mod
-rw-r--r-- 1 root root 2.7K Jan 6 06:43 odc.mod
-rw-r--r-- 1 root root 1.5K Jan 6 06:43 offsetio.mod
-rw-r--r-- 1 root root 11K Jan 6 06:43 ohci.mod
-rw-r--r-- 1 root root 1.7K Jan 6 06:43 part_acorn.mod
-rw-r--r-- 1 root root 1.9K Jan 6 06:43 part_amiga.mod
-rw-r--r-- 1 root root 2.1K Jan 6 06:43 part_apple.mod
-rw-r--r-- 1 root root 2.7K Jan 6 06:43 part_bsd.mod
-rw-r--r-- 1 root root 1.7K Jan 6 06:43 part_dfly.mod
-rw-r--r-- 1 root root 1.5K Jan 6 06:43 part_dvh.mod
-rw-r--r-- 1 root root 2.4K Jan 6 06:43 part_gpt.mod
-rw-r--r-- 1 root root 111 Jan 6 06:43 partmap.lst
-rw-r--r-- 1 root root 2.3K Jan 6 06:43 part_msdos.mod
-rw-r--r-- 1 root root 1.8K Jan 6 06:43 part_plan.mod
-rw-r--r-- 1 root root 1.5K Jan 6 06:43 part_sun.mod
-rw-r--r-- 1 root root 1.6K Jan 6 06:43 part_sunpc.mod
-rw-r--r-- 1 root root 17 Jan 6 06:43 parttool.lst
-rw-r--r-- 1 root root 4.6K Jan 6 06:43 parttool.mod
-rw-r--r-- 1 root root 1.9K Jan 6 06:43 password.mod
-rw-r--r-- 1 root root 2.8K Jan 6 06:43 password_pbkdf2.mod
-rw-r--r-- 1 root root 4.7K Jan 6 06:43 pata.mod
-rw-r--r-- 1 root root 1.5K Jan 6 06:43 pbkdf2.mod
-rw-r--r-- 1 root root 2.2K Jan 6 06:43 pbkdf2_test.mod
-rw-r--r-- 1 root root 2.5K Jan 6 06:43 pcidump.mod
-rw-r--r-- 1 root root 1.4K Jan 6 06:43 pci.mod
-rw-r--r-- 1 root root 6.1K Jan 6 06:43 plan9.mod
-rw-r--r-- 1 root root 2.4K Jan 6 06:43 play.mod
-rw-r--r-- 1 root root 7.3K Jan 6 06:43 png.mod
-rw-r--r-- 1 root root 1.6K Jan 6 06:43 priority_queue.mod
-rw-r--r-- 1 root root 2.7K Jan 6 06:43 probe.mod
-rw-r--r-- 1 root root 2.1K Jan 6 06:43 procfs.mod
-rw-r--r-- 1 root root 2.1K Jan 6 06:43 progress.mod
-rw-r--r-- 1 root root 2.7K Jan 6 06:43 pxechain.mod
-rw-r--r-- 1 root root 3.8K Jan 6 06:43 pxe.mod
-rw-r--r-- 1 root root 1.4K Jan 6 06:43 raid5rec.mod
-rw-r--r-- 1 root root 2.2K Jan 6 06:43 raid6rec.mod
-rw-r--r-- 1 root root 1.5K Jan 6 06:43 read.mod
-rw-r--r-- 1 root root 1.7K Jan 6 06:43 reboot.mod
-rw-r--r-- 1 root root 50K Jan 6 06:43 regexp.mod
-rw-r--r-- 1 root root 8.8K Jan 6 06:43 reiserfs.mod
-rw-r--r-- 1 root root 15K Jan 6 06:43 relocator.mod
-rw-r--r-- 1 root root 4.1K Jan 6 06:43 romfs.mod
-rw-r--r-- 1 root root 4.9K Jan 6 06:43 scsi.mod
-rw-r--r-- 1 root root 3.2K Jan 6 06:43 search_fs_file.mod
-rw-r--r-- 1 root root 3.2K Jan 6 06:43 search_fs_uuid.mod
-rw-r--r-- 1 root root 3.1K Jan 6 06:43 search_label.mod
-rw-r--r-- 1 root root 3.6K Jan 6 06:43 search.mod
-rw-r--r-- 1 root root 7.0K Jan 6 06:43 sendkey.mod
-rw-r--r-- 1 root root 7.6K Jan 6 06:43 serial.mod
-rw-r--r-- 1 root root 706 Jan 6 06:43 setjmp.mod
-rw-r--r-- 1 root root 1.7K Jan 6 06:43 setjmp_test.mod
-rw-r--r-- 1 root root 5.3K Jan 6 06:43 setpci.mod
-rw-r--r-- 1 root root 5.1K Jan 6 06:43 sfs.mod
-rw-r--r-- 1 root root 6.3K Jan 6 06:43 signature_test.mod
-rw-r--r-- 1 root root 2.3K Jan 6 06:43 sleep.mod
-rw-r--r-- 1 root root 2.3K Jan 6 06:43 sleep_test.mod
-rw-r--r-- 1 root root 2.1K Jan 6 06:43 spkmodem.mod
-rw-r--r-- 1 root root 6.8K Jan 6 06:43 squash4.mod
-rw-r--r-- 1 root root 18K Jan 6 06:43 syslinuxcfg.mod
-rw-r--r-- 1 root root 3.3K Jan 6 06:43 tar.mod
-rw-r--r-- 1 root root 202 Jan 6 06:43 terminal.lst
-rw-r--r-- 1 root root 4.4K Jan 6 06:43 terminal.mod
-rw-r--r-- 1 root root 12K Jan 6 06:43 terminfo.mod
-rw-r--r-- 1 root root 1.4K Jan 6 06:43 test_blockarg.mod
-rw-r--r-- 1 root root 2.7K Jan 6 06:43 testload.mod
-rw-r--r-- 1 root root 5.1K Jan 6 06:43 test.mod
-rw-r--r-- 1 root root 2.3K Jan 6 06:43 testspeed.mod
-rw-r--r-- 1 root root 5.2K Jan 6 06:43 tftp.mod
-rw-r--r-- 1 root root 4.4K Jan 6 06:43 tga.mod
-rw-r--r-- 1 root root 1.5K Jan 6 06:43 time.mod
-rw-r--r-- 1 root root 1.8K Jan 6 06:43 trig.mod
-rw-r--r-- 1 root root 2.4K Jan 6 06:43 tr.mod
-rw-r--r-- 1 root root 3.5K Jan 6 06:43 truecrypt.mod
-rw-r--r-- 1 root root 1.2K Jan 6 06:43 true.mod
-rw-r--r-- 1 root root 7.6K Jan 6 06:43 udf.mod
-rw-r--r-- 1 root root 5.8K Jan 6 06:43 ufs1_be.mod
-rw-r--r-- 1 root root 5.4K Jan 6 06:43 ufs1.mod
-rw-r--r-- 1 root root 5.5K Jan 6 06:43 ufs2.mod
-rw-r--r-- 1 root root 6.6K Jan 6 06:43 uhci.mod
-rw-r--r-- 1 root root 3.9K Jan 6 06:43 usb_keyboard.mod
-rw-r--r-- 1 root root 11K Jan 6 06:43 usb.mod
-rw-r--r-- 1 root root 6.9K Jan 6 06:43 usbms.mod
-rw-r--r-- 1 root root 2.1K Jan 6 06:43 usbserial_common.mod
-rw-r--r-- 1 root root 2.3K Jan 6 06:43 usbserial_ftdi.mod
-rw-r--r-- 1 root root 2.7K Jan 6 06:43 usbserial_pl2303.mod
-rw-r--r-- 1 root root 1.5K Jan 6 06:43 usbserial_usbdebug.mod
-rw-r--r-- 1 root root 3.6K Jan 6 06:43 usbtest.mod
-rw-r--r-- 1 root root 9.7K Jan 6 06:43 vbe.mod
-rw-r--r-- 1 root root 12K Jan 6 06:43 verify.mod
-rw-r--r-- 1 root root 5.0K Jan 6 06:43 vga.mod
-rw-r--r-- 1 root root 2.1K Jan 6 06:43 vga_text.mod
-rw-r--r-- 1 root root 5.6K Jan 6 06:43 video_bochs.mod
-rw-r--r-- 1 root root 6.0K Jan 6 06:43 video_cirrus.mod
-rw-r--r-- 1 root root 5.6K Jan 6 06:43 video_colors.mod
-rw-r--r-- 1 root root 23K Jan 6 06:43 video_fb.mod
-rw-r--r-- 1 root root 3.9K Jan 6 06:43 videoinfo.mod
-rw-r--r-- 1 root root 33 Jan 6 06:43 video.lst
-rw-r--r-- 1 root root 6.1K Jan 6 06:43 video.mod
-rw-r--r-- 1 root root 2.4K Jan 6 06:43 videotest_checksum.mod
-rw-r--r-- 1 root root 4.2K Jan 6 06:43 videotest.mod
-rw-r--r-- 1 root root 6.1K Jan 6 06:43 xfs.mod
-rw-r--r-- 1 root root 27K Jan 6 06:43 xnu.mod
-rw-r--r-- 1 root root 2.1K Jan 6 06:43 xnu_uuid.mod
-rw-r--r-- 1 root root 2.0K Jan 6 06:43 xnu_uuid_test.mod
-rw-r--r-- 1 root root 16K Jan 6 06:43 xzio.mod
-rw-r--r-- 1 root root 5.4K Jan 6 06:43 zfscrypt.mod
-rw-r--r-- 1 root root 6.5K Jan 6 06:43 zfsinfo.mod
-rw-r--r-- 1 root root 39K Jan 6 06:43 zfs.mod
root@sysresccd /mnt/raid % ll boot/grub/locale
total 24K
drwxr-xr-x 2 root root 4.0K Jan 6 06:43 .
drwxr-xr-x 5 root root 4.0K Jan 6 06:43 ..
-rw-r--r-- 1 root root 1.1K Jan 6 06:43 en_AU.mo
-rw-r--r-- 1 root root 587 Jan 6 06:43 en_CA.mo
-rw-r--r-- 1 root root 4.4K Jan 6 06:43 en_GB.mo
% cat /boot/grub/grub.conf
# This is a sample grub.conf for use with Genkernel, per the Gentoo handbook
# http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=10#doc_chap2
# If you are not using Genkernel and you need help creating this file, you
# should consult the handbook. Alternatively, consult the grub.conf.sample that
# is included with the Grub documentation.
default 0
timeout 30
#splashimage=(hd0,0)/boot/grub/splash.xpm.gz
#title Gentoo Linux 3.8.13
#root (hd0,0)
#kernel /boot/kernel-genkernel-x86-3.8.13-gentoo root=/dev/sda3
#initrd /boot/initramfs-genkernel-x86-3.8.13
# vim:ft=conf:
the way the Unix file system works, / is the root of the fielsystem tree /boot must exist within the root even though it is overlayed by the /dev/sda1 partition.
To boot a system, /boot must be on a bootable and a raw device, you can raid 1 (Mirror) but
For future reference to add redundancy to your setups,
/dev/sda1 and /dev/sdb1, sdc1 as an example can be partitioned as 1 Gb linux linux raid autodetect
/dev/md0 can be then created that is a RAID1/Mirror using the two /dev/sd[ab]1 with /dev/sdc1 as a possible hot swap.
/dev/md0 is then formated as extx and referenced as /boot
this way so long as either of the two disks remains, the system will boot. ( you would have to make sure during partitioning the /dev/sda1 and /dev/sdb1 have the boot setting set.)
In your case you lucked out that /dev/sdc failed and not /dev/sda.
usually, I would suggest that all drives be partitioned identically since RAID will use the smaller space ... meaning on your sdb1 and sdb2 20+GB of space goes unused/unallocated....
The item of importance is the /mnt/raid/etc/mdadm/mdamd.
this is where the definition of the md0 exist. the issue might be that since you recreated the md volume using the rescuedisk, the marker within the boot system md0 definition differs and that might be why it is not being allowed to proceed.
make sure you copy/backup the data from the system just in case...
You may have to repair grub. Â I am unclear on what happens when grub comes up and you tell it to proceed.
does it boot?
To boot a system, /boot must be on a bootable and a raw device, you can raid 1 (Mirror) but
For future reference to add redundancy to your setups,
/dev/sda1 and /dev/sdb1, sdc1 as an example can be partitioned as 1 Gb linux linux raid autodetect
/dev/md0 can be then created that is a RAID1/Mirror using the two /dev/sd[ab]1 with /dev/sdc1 as a possible hot swap.
/dev/md0 is then formated as extx and referenced as /boot
this way so long as either of the two disks remains, the system will boot. ( you would have to make sure during partitioning the /dev/sda1 and /dev/sdb1 have the boot setting set.)
In your case you lucked out that /dev/sdc failed and not /dev/sda.
usually, I would suggest that all drives be partitioned identically since RAID will use the smaller space ... meaning on your sdb1 and sdb2 20+GB of space goes unused/unallocated....
The item of importance is the /mnt/raid/etc/mdadm/mdamd.
this is where the definition of the md0 exist. the issue might be that since you recreated the md volume using the rescuedisk, the marker within the boot system md0 definition differs and that might be why it is not being allowed to proceed.
make sure you copy/backup the data from the system just in case...
You may have to repair grub. Â I am unclear on what happens when grub comes up and you tell it to proceed.
does it boot?
here is mdadm.conf
When grub comes up it not the menu but the
grub>
prompt nothing else. Holding left shift on boot gets the same and a tab gets screen fulls of commands
/mnt/raid % cat /mnt/raid/etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 UUID=9d671302:348388b7:d6b24a17:9c0edf05 name=eagle:0
# This file was auto-generated on Sun, 29 Dec 2013 02:01:22 -0600
# by mkconf $Id$When grub comes up it not the menu but the
grub>
prompt nothing else. Holding left shift on boot gets the same and a tab gets screen fulls of commands
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
This suggests that when you booted for the rescue CD you reinstalled/reinitiated the boot loader install, but pointed it to the wrong location.
look at the grub.conf within the mnt/raid//boot/boot/grub/g
look at the original grub.conf in /mnt/boot/grub/grub.conf and compare the root= lines.
at the grub prompt enter boot (hd0,0)
in the recovery CD, did you run grub-install on a location such as --root-directory=/mnt/boot
grub-install adds the boot/higherarchy
often when you boot from other, you have to mount //dev/md0 as /mnt/raid in this case and then mount /dev/sda1 as /mnt/raid/boot
then run grub-install --root-directory=/mnt/raid
....
look at the grub.conf within the mnt/raid//boot/boot/grub/g
look at the original grub.conf in /mnt/boot/grub/grub.conf and compare the root= lines.
at the grub prompt enter boot (hd0,0)
in the recovery CD, did you run grub-install on a location such as --root-directory=/mnt/boot
grub-install adds the boot/higherarchy
often when you boot from other, you have to mount //dev/md0 as /mnt/raid in this case and then mount /dev/sda1 as /mnt/raid/boot
then run grub-install --root-directory=/mnt/raid
....
I think you're correct in your assumption. Will try these in the morning and reply back. Thank you very much.
OK here's' whats in grub.cfg (file attached).
There is only one /boot/grub etc. I was looking at it with a crummy SSH program and it messed up the capture.
Here are the results of grub install you mentioned:
 grub-install --root-directory=/mnt/raid
install_device not specified.
Usage: grub-install [OPTION] install_device
Install GRUB on your drive.
Â
 -h, --help        print this message and exit
 -v, --version      print the version information and exit
 --root-directory=DIR   install GRUB images under the directory DIR
             instead of the root directory
 --grub-shell=FILE    use FILE as the grub shell
 --no-floppy       do not probe any floppy drive
 --force-lba       force GRUB to use LBA mode even for a buggy
             BIOS
 --recheck        probe a device map even if it already exists
Â
INSTALL_DEVICE can be a GRUB device name or a system device filename.
Â
grub-install copies GRUB images into the DIR/boot directory specfied by
--root-directory, and uses the grub shell to install grub into the boot
sector.
Â
Report bugs to <bug-grub@gnu.org>.
grub.cfg.txt
There is only one /boot/grub etc. I was looking at it with a crummy SSH program and it messed up the capture.
Here are the results of grub install you mentioned:
 grub-install --root-directory=/mnt/raid
install_device not specified.
Usage: grub-install [OPTION] install_device
Install GRUB on your drive.
Â
 -h, --help        print this message and exit
 -v, --version      print the version information and exit
 --root-directory=DIR   install GRUB images under the directory DIR
             instead of the root directory
 --grub-shell=FILE    use FILE as the grub shell
 --no-floppy       do not probe any floppy drive
 --force-lba       force GRUB to use LBA mode even for a buggy
             BIOS
 --recheck        probe a device map even if it already exists
Â
INSTALL_DEVICE can be a GRUB device name or a system device filename.
Â
grub-install copies GRUB images into the DIR/boot directory specfied by
--root-directory, and uses the grub shell to install grub into the boot
sector.
Â
Report bugs to <bug-grub@gnu.org>.
grub.cfg.txt
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
You are missing the /dev/sda in the end.
You posted the link, not sure you followed.
https://help.ubuntu.com/community/Grub2/Installing#Fixing_a_Broken_System
Not sure why or whether you ran the grub-install directive.
When a raid volume reflects a failed device but the system continues to run, there is absolutely no need to reset/alter the boot record.
The three first links you posted the first two deal with resetting the boot loader following a Windows system install. So would generally not apply to your situation.
The third which is referenced above deals with the current condition you find yourself in.
Your grub.conf is different than the one I expected.....(commonly, better familiar with RH,centos)
..
Thus far you still did not respond whether you took precautions and backup your data.......
I would advise/suggest you backup data..
You posted the link, not sure you followed.
https://help.ubuntu.com/community/Grub2/Installing#Fixing_a_Broken_System
Not sure why or whether you ran the grub-install directive.
When a raid volume reflects a failed device but the system continues to run, there is absolutely no need to reset/alter the boot record.
The three first links you posted the first two deal with resetting the boot loader following a Windows system install. So would generally not apply to your situation.
The third which is referenced above deals with the current condition you find yourself in.
Your grub.conf is different than the one I expected.....(commonly, better familiar with RH,centos)
..
Thus far you still did not respond whether you took precautions and backup your data.......
I would advise/suggest you backup data..
OH cr*p! So much for working with a migraine.
Yes the data is fully backed up. This is also a backup server to an identical primary server so at worst we could restore from the primary if our backup was bad and change IP, etc. I was sure I posted that last night..Sorry.
Success on the install.
 grub-install --root-directory=/mnt/raid
a
Probing devices to guess BIOS drives. This may take a long time.
Installation finished. No error reported.
This is the contents of the device map /mnt/raid//boot/grub/devic
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
Â
(fd0) Â /dev/fd0
(hd0) Â /dev/sda
(hd1) Â /dev/sdb
(hd2) Â /dev/sdc
Now the article referenced running this on each drive
/dev/sda
/dev/sdb
/dev/sdc
https://help.ubuntu.com/community/Grub2/Installing#Fixing_a_Broken_System
before update grub. I have only done sda should I proceed with sdb &Â sdc
Reinstall GRUB 2 (substitute the correct device with sda, sdb, etc. Do not specify a partition number):
grub-install /dev/sdX
If the system partitions are on a software RAID install GRUB 2 on all disks in the RAID. Example (software RAID using /dev/sda and /dev/sdb):
grub-install /dev/sda
grub-install /dev/sdb
Recreate the GRUB 2 menu file (grub.cfg)
update-grub
Yes the data is fully backed up. This is also a backup server to an identical primary server so at worst we could restore from the primary if our backup was bad and change IP, etc. I was sure I posted that last night..Sorry.
Success on the install.
 grub-install --root-directory=/mnt/raid
a
Probing devices to guess BIOS drives. This may take a long time.
Installation finished. No error reported.
This is the contents of the device map /mnt/raid//boot/grub/devic
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
Â
(fd0) Â /dev/fd0
(hd0) Â /dev/sda
(hd1) Â /dev/sdb
(hd2) Â /dev/sdc
Now the article referenced running this on each drive
/dev/sda
/dev/sdb
/dev/sdc
https://help.ubuntu.com/community/Grub2/Installing#Fixing_a_Broken_System
before update grub. I have only done sda should I proceed with sdb &Â sdc
Reinstall GRUB 2 (substitute the correct device with sda, sdb, etc. Do not specify a partition number):
grub-install /dev/sdX
If the system partitions are on a software RAID install GRUB 2 on all disks in the RAID. Example (software RAID using /dev/sda and /dev/sdb):
grub-install /dev/sda
grub-install /dev/sdb
Recreate the GRUB 2 menu file (grub.cfg)
update-grub
You can not since you do not have a /boot partition on sdb nor on sdc.
One would install grub/boot loader on sdb and sdc as well when your RAID the /boot ....
did the system boot after the update?
One would install grub/boot loader on sdb and sdc as well when your RAID the /boot ....
did the system boot after the update?
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Yes we are up here!! As long as the USB drive are disconnected it is fine otherwise we hang at the Verifying DMI.
That never has been an issue (obviously) until now.
What do we do to fix that? The devices are a pair of USB disks 1TB and 5TB Seagate.
That never has been an issue (obviously) until now.
What do we do to fix that? The devices are a pair of USB disks 1TB and 5TB Seagate.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Oh they wok fine here if connected after boot. Ill check the boot order etc. I might have moved them ahead of disj when trying to recover here etc. Will get vack with you later today.
You were precisely correct. I had USB firdt then CD-ROM then IDE. Put IDE 2nd then USB third and we're back to normal.
Thank you i think this closes the issue. You were a huge help. Have a great weekend.
Thank you i think this closes the issue. You were a huge help. Have a great weekend.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Fantastic help and knowledge. Excellent job.
Linux Distributions
--
Questions
--
Followers
Top Experts
A Linux distribution is an operating system made as a software collection based on the Linux kernel and, often, on a package management system and are available for a variety of systems. A typical Linux distribution comprises a Linux kernel, GNU tools and libraries, additional software, documentation, a window system (the most common being the X Window System), a window manager, and a desktop environment. Most Linux systems are open-source software made available both as compiled binaries and in source code form, allowing modifications to the original software. Over three hundred distributions are in active development, including commercially backed distributions (such as Fedora, openSUSE and Ubuntu) and community-driven distributions (such as Debian, Slackware, Gentoo and Arch Linux).