Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[Solved] Cannot boot from new ssd after restore ( Grub issue ? )
[Solved] Cannot boot from new ssd after restore ( Grub issue ? )
Hello,
I would like to ask a question on how to troubleshoot booting.
I am admin for a small server that mainly runs file sharing (over fuse-ssh), gitlab-ce and mail for a small work group.
Main hardware is from supermicro (X11SCL-IF), 4 hard drives in a Raid array for file storage, and a SSD to run the os.
Os has been Debian, for the last 15years or so, works flawlessly for this purpose so far .
The machine runs well, with the exception of the m.2 nvme drive.
I first used a Kingston m.2 SSD, which started to generate a lot of read / write errors after one or two months.
Brought it back to the store, they could not find anything wrong with the drive, but offered a Samsung replacement
So ran the Samsung m.2 SSD, which also started to generate errors. Switched to a Western Digital SSD.
The idea behind this is that there may be something odd with the nvme hardware, so switching to sata would help.
And it seems it did, system is running fine for several months, no issue... no read/write errors... however.
During updates, I find it still boots in a very old kernel. After a short search it seems like something odd is going on.
The system is still (partially) booting from the m.2 disk, to remedy this I tried the following:
- checked bios settings
-> set to 'dual' meaning both uefi/mbr boot. ( tried setting this to 'legacy/mbr' did not make a difference).
-> check that sata ssd is the first boot option, it is.
- checked grub
-> did 'grub-mkconfig", "update-grub" and "grub-install /dev/sde"
-> reboot, this did not help the situation.
- reinstall grub bootloader from usb on /dev/sde using rescue mode.
-> reboot, this did not help the situation either.
- check for mbr using "file -s /dev/sde" -> "/dev/sde: Dos/mbr boot sector" (? dos no grub ?)
- check for mbr using "file -s /dev/sde1" -> "/dev/sde1: Dos/mbr boot sector ... " (? same question as above ...)
- check for mbr using "file -s /dev/sde5" -> "/dev/sde5: Linux rev 1.0 ... " (? no boot sector ?)
- check for boot flag using fdisk /dev/sde:
- boot flag on /dev/sde5 ( where I think it should be ).
-> ?? This is puzzling to me, "file" shows boot sectors where "fdisk" does not show boot flags and the other way around.
I am assuming there is a difference between a mbr and a bootable flag...
- check for mbr using "file -s /dev/nvme0n1" -> "/dev/nvme0n1: Dos/mbr boot sector" (? dos no grub ?)
I cannot see what is wrong, unless the 'dos/mbr boot sector' flag is wrong.
But that would be odd, there has been no dos or windows installed on this system.
I have come up with two theories... I would like to ask help in testing them...
What may be a factor is that I have moved the system from one drive to another using 'dd' (i.e. clone).
That way, I thought, the system should be transferred nicely, but things like drive UUID's are also the same.
I wonder if that might have something to do with it, how I could check? and if so fix?
The other idea is that for some reason, the MBR on /dev/sde is not pointing to /dev/sde5/boot/.
Or for some reason not running the grub on the sde drive.
But is there a way to check what is in the MBR? can you check what is happening?
I am hesitant to just reinstall everything as that typically takes a significant amount of time and testing.
And I am pretty sure I am not the only one with this problem, how to switch hardware on the drive the system runs on?
So I request help, any hints very much appreciated!
Boris
I would like to ask a question on how to troubleshoot booting.
I am admin for a small server that mainly runs file sharing (over fuse-ssh), gitlab-ce and mail for a small work group.
Main hardware is from supermicro (X11SCL-IF), 4 hard drives in a Raid array for file storage, and a SSD to run the os.
Os has been Debian, for the last 15years or so, works flawlessly for this purpose so far .
The machine runs well, with the exception of the m.2 nvme drive.
I first used a Kingston m.2 SSD, which started to generate a lot of read / write errors after one or two months.
Brought it back to the store, they could not find anything wrong with the drive, but offered a Samsung replacement
So ran the Samsung m.2 SSD, which also started to generate errors. Switched to a Western Digital SSD.
The idea behind this is that there may be something odd with the nvme hardware, so switching to sata would help.
And it seems it did, system is running fine for several months, no issue... no read/write errors... however.
During updates, I find it still boots in a very old kernel. After a short search it seems like something odd is going on.
The system is still (partially) booting from the m.2 disk, to remedy this I tried the following:
- checked bios settings
-> set to 'dual' meaning both uefi/mbr boot. ( tried setting this to 'legacy/mbr' did not make a difference).
-> check that sata ssd is the first boot option, it is.
- checked grub
-> did 'grub-mkconfig", "update-grub" and "grub-install /dev/sde"
-> reboot, this did not help the situation.
- reinstall grub bootloader from usb on /dev/sde using rescue mode.
-> reboot, this did not help the situation either.
- check for mbr using "file -s /dev/sde" -> "/dev/sde: Dos/mbr boot sector" (? dos no grub ?)
- check for mbr using "file -s /dev/sde1" -> "/dev/sde1: Dos/mbr boot sector ... " (? same question as above ...)
- check for mbr using "file -s /dev/sde5" -> "/dev/sde5: Linux rev 1.0 ... " (? no boot sector ?)
- check for boot flag using fdisk /dev/sde:
- boot flag on /dev/sde5 ( where I think it should be ).
-> ?? This is puzzling to me, "file" shows boot sectors where "fdisk" does not show boot flags and the other way around.
I am assuming there is a difference between a mbr and a bootable flag...
- check for mbr using "file -s /dev/nvme0n1" -> "/dev/nvme0n1: Dos/mbr boot sector" (? dos no grub ?)
I cannot see what is wrong, unless the 'dos/mbr boot sector' flag is wrong.
But that would be odd, there has been no dos or windows installed on this system.
I have come up with two theories... I would like to ask help in testing them...
What may be a factor is that I have moved the system from one drive to another using 'dd' (i.e. clone).
That way, I thought, the system should be transferred nicely, but things like drive UUID's are also the same.
I wonder if that might have something to do with it, how I could check? and if so fix?
The other idea is that for some reason, the MBR on /dev/sde is not pointing to /dev/sde5/boot/.
Or for some reason not running the grub on the sde drive.
But is there a way to check what is in the MBR? can you check what is happening?
I am hesitant to just reinstall everything as that typically takes a significant amount of time and testing.
And I am pretty sure I am not the only one with this problem, how to switch hardware on the drive the system runs on?
So I request help, any hints very much appreciated!
Boris
-
- df -h | grep > 20TiB
- Posts: 1418
- Joined: 2012-10-06 05:31
- Location: /dev/chair
- Has thanked: 80 times
- Been thanked: 191 times
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Indeed. The "boot" partition flag is a value within a boot record, hinting the BIOS and/or bootloader which boot record to use.
"dos/mbr" is a reference to the partition table and boot sector format on the disk.
The "DOS compatible PC" and all the baggage that goes with it long predates GNU/Linux. Whether it was actual DOS that wrote the partiton table is irrelevant, if you're booting in "legacy" mode, that's how the BIOS will look for an OS to boot.
Quite possibly. Probably, even.
Unless you have configured things otherwise, both grub and initrd/fstab will be using UUIDs... Potentially leading to entertainingly random combinations of kernel image/initrd, boot and root partitions on startup.
Compare output of blkid [device of interest] to contents of fstab, grub.cfg, and output of mount.
For filesystem UUIDs, something like: 'tune2fs -U [new UUID or "random"] [partition]' (for ext4), or equivalent if you are running some other filesystem. See relevant command manual page.
For (GPT) partition UUIDs, look in fdisk's "expert" menu.
Or just, ya know, pull or nuke the disk you're not using.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Hello,
I just checked the output of blkid with:
- fstab -> contains a UUID that corresponds to the UUID on both the old nvme and the new ssd drive.
- grub.cfg -> same here, UUID that corresponds to both.
- mount -> shows / mounted on /dev/sde5 ( which is the new ssd ).
I did pull the disk I dont want to use already, but then the system will not boot.
I cannot troubleshoot why the old drive is still in use, hence not correct it so it is not required for booting, then pull it.
So all hints very welcome!
Thanks for the quick reply...
Boris
I just checked the output of blkid with:
- fstab -> contains a UUID that corresponds to the UUID on both the old nvme and the new ssd drive.
- grub.cfg -> same here, UUID that corresponds to both.
- mount -> shows / mounted on /dev/sde5 ( which is the new ssd ).
I did pull the disk I dont want to use already, but then the system will not boot.
I cannot troubleshoot why the old drive is still in use, hence not correct it so it is not required for booting, then pull it.
So all hints very welcome!
Thanks for the quick reply...
Boris
-
- Posts: 444
- Joined: 2023-02-07 13:35
- Been thanked: 105 times
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Please install the boot-info-script package and share the output of
Be sure to use code tags for the output, it will be lengthy.
Code: Select all
/usr/sbin/bootinfoscript
Jeder nach seinen Fähigkeiten, jedem nach seinen Bedürfnissen.
-
- df -h | grep > 20TiB
- Posts: 1418
- Joined: 2012-10-06 05:31
- Location: /dev/chair
- Has thanked: 80 times
- Been thanked: 191 times
Re: Cannot boot from new ssd after resture ( Grub issue ? )
This^, also more information on exactly what "the system will not boot" means - i.e. where exactly the boot process stops, and what, if any, error messages are displayed. Does it get as far as loading GRUB's stage-1 from the MBR on the SATA drive?
Full output of blkid, grub-install with the --verbose flag, and a dump of the partition layout may also be of interest.
From your repeated mentions of MBRs and boot sectors, I assume you are running msdos partition tables and MBR boot (i.e. no GPT or UEFI shenanigans). That's good, I hate dealing with UEFI... It's also a little odd though, as IME very few BIOSes can boot NVME drives in "legacy" mode. I'm guessing the X11 series (still running X9 / Sandybridge-EP boards here) might be in just the right spot WRT the industry UEFI transition to support both, but I wouldn't be surprised if it comes with it's own quirks WRT boot order and such.
Full output of blkid, grub-install with the --verbose flag, and a dump of the partition layout may also be of interest.
From your repeated mentions of MBRs and boot sectors, I assume you are running msdos partition tables and MBR boot (i.e. no GPT or UEFI shenanigans). That's good, I hate dealing with UEFI... It's also a little odd though, as IME very few BIOSes can boot NVME drives in "legacy" mode. I'm guessing the X11 series (still running X9 / Sandybridge-EP boards here) might be in just the right spot WRT the industry UEFI transition to support both, but I wouldn't be surprised if it comes with it's own quirks WRT boot order and such.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Hello,
Below the requested output of #grub-install --verbose /dev/sde
Pls note, I edited out a bit of the message to make it fit in the max allowed numver of characters limit.
Something is not going well here, I didn't use the --verbose flag before, so just saw the 'installation finished. No error reported' message at the end.
Which sounds encouraging, but maybe was not.
Hope this, together with the previous message, contains all the info
Good weekend!
Boris
Below the requested output of #grub-install --verbose /dev/sde
Pls note, I edited out a bit of the message to make it fit in the max allowed numver of characters limit.
Something is not going well here, I didn't use the --verbose flag before, so just saw the 'installation finished. No error reported' message at the end.
Which sounds encouraging, but maybe was not.
Code: Select all
root@srv:~# grub-install --verbose /dev/sde
grub-install: info: executing modprobe efivars 2>/dev/null.
grub-install: info: Looking for /sys/firmware/efi ...
grub-install: info: ... not found.
grub-install: info: Looking for /proc/device-tree ...
grub-install: info: ... not found.
Installing for i386-pc platform.
grub-install: info: cannot open `/boot/grub/device.map': No such file or directory.
grub-install: info: copying `/usr/share/locale/kg/LC_MESSAGES/grub.mo' -> `/boot/grub/locale/kg.mo'.
grub-install: info: cannot open `/usr/share/locale/kg/LC_MESSAGES/grub.mo': No such file or directory.
grub-install: info: copying `/usr/share/locale/ce/LC_MESSAGES/grub.mo' -> `/boot/grub/locale/ce.mo'.
grub-install: info: cannot open `/usr/share/locale/ce/LC_MESSAGES/grub.mo': No such file or directory.
grub-install: info: copying `/usr/share/locale/iu/LC_MESSAGES/grub.mo' -> `/boot/grub/locale/iu.mo'.
grub-install: info: cannot open `/usr/share/locale/iu/LC_MESSAGES/grub.mo': No such file or directory.
grub-install: info: copying `/usr/share/locale/kok/LC_MESSAGES/grub.mo' -> `/boot/grub/locale/kok.mo'.
Edit... something is not going well here I think, but there are so many messages that I removed some.
If I dont, the message exceeds the max number of allowed characters by quite a margin...
If I removed something that is still required, I'll send the file through wetransfer or something.
grub-install: info: copying `/usr/lib/grub/i386-pc/partmap.lst' -> `/boot/grub/i386-pc/partmap.lst'.
grub-install: info: copying `/usr/lib/grub/i386-pc/parttool.lst' -> `/boot/grub/i386-pc/parttool.lst'.
grub-install: info: copying `/usr/lib/grub/i386-pc/video.lst' -> `/boot/grub/i386-pc/video.lst'.
grub-install: info: copying `/usr/lib/grub/i386-pc/crypto.lst' -> `/boot/grub/i386-pc/crypto.lst'.
grub-install: info: copying `/usr/lib/grub/i386-pc/terminal.lst' -> `/boot/grub/i386-pc/terminal.lst'.
grub-install: info: copying `/usr/lib/grub/i386-pc/modinfo.sh' -> `/boot/grub/i386-pc/modinfo.sh'.
grub-install: info: copying `/usr/share/grub/unicode.pf2' -> `/boot/grub/fonts/unicode.pf2'.
grub-install: info: /dev/sde5 is not present.
grub-install: info: Looking for /dev/sde5.
grub-install: info: /dev/sde is a parent of /dev/sde5.
grub-install: info: /dev/sde5 starts from 2048.
grub-install: info: opening the device hostdisk//dev/sde.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Partition 4 starts from 2048.
grub-install: info: /dev/sde5 is present.
grub-install: info: Looking for /dev/sde5.
grub-install: info: /dev/sde is a parent of /dev/sde5.
grub-install: info: /dev/sde5 starts from 2048.
grub-install: info: opening the device hostdisk//dev/sde.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Partition 4 starts from 2048.
grub-install: info: /dev/sde5 is present.
grub-install: info: Looking for /dev/sde5.
grub-install: info: /dev/sde is a parent of /dev/sde5.
grub-install: info: /dev/sde5 starts from 2048.
grub-install: info: opening the device hostdisk//dev/sde.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Partition 4 starts from 2048.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: /dev/sde is present.
grub-install: info: Looking for /dev/sde.
grub-install: info: /dev/sde is a parent of /dev/sde.
grub-install: info: /dev/sde is present.
grub-install: info: Looking for /dev/sde.
grub-install: info: /dev/sde is a parent of /dev/sde.
grub-install: info: /dev/sde is present.
grub-install: info: Looking for /dev/sde.
grub-install: info: /dev/sde is a parent of /dev/sde.
grub-install: info: grub-mkimage --directory '/usr/lib/grub/i386-pc' --prefix '(,msdos5)/boot/grub' --output '/boot/grub/i386-pc/core.img' --dtb '' --sbat '' --format 'i386-pc' --compression 'auto' 'ext2' 'part_msdos' 'biosdisk'
.
grub-install: info: the total module size is 0x3ed0.
grub-install: info: reading /usr/lib/grub/i386-pc/kernel.img.
grub-install: info: locating the section .text at 0x0.
grub-install: info: locating the section .rodata at 0x59a0.
grub-install: info: locating the section .data at 0x6aa0.
grub-install: info: locating the section .bss at 0x72e0.
grub-install: info: reading /usr/lib/grub/i386-pc/fshelp.mod.
grub-install: info: reading /usr/lib/grub/i386-pc/ext2.mod.
grub-install: info: reading /usr/lib/grub/i386-pc/part_msdos.mod.
grub-install: info: reading /usr/lib/grub/i386-pc/biosdisk.mod.
grub-install: info: kernel_img=0x5640064f4d50, kernel_size=0x72c8.
grub-install: info: the core size is 0x5b5a.
grub-install: info: reading /usr/lib/grub/i386-pc/lzma_decompress.img.
grub-install: info: reading /usr/lib/grub/i386-pc/diskboot.img.
grub-install: info: writing 0x200 bytes.
grub-install: info: writing 0x667a bytes.
grub-install: info: copying `/usr/lib/grub/i386-pc/boot.img' -> `/boot/grub/i386-pc/boot.img'.
grub-install: info: grub-bios-setup --verbose --directory='/boot/grub/i386-pc' --device-map='/boot/grub/device.map' '/dev/sde'.
grub-install: info: reading /boot/grub/i386-pc/boot.img.
grub-install: info: reading /boot/grub/i386-pc/core.img.
grub-install: info: Opening dest `hostdisk//dev/sde'.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: /dev/sde5 is present.
grub-install: info: Looking for /dev/sde5.
grub-install: info: /dev/sde is a parent of /dev/sde5.
grub-install: info: /dev/sde5 starts from 2048.
grub-install: info: opening the device hostdisk//dev/sde.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Partition 4 starts from 2048.
grub-install: info: /dev/sde5 is present.
grub-install: info: Looking for /dev/sde5.
grub-install: info: /dev/sde is a parent of /dev/sde5.
grub-install: info: /dev/sde5 starts from 2048.
grub-install: info: opening the device hostdisk//dev/sde.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Scanning for DISKFILTER devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid1x devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09_be devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for mdraid09 devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for dmraid_nv devices on disk hostdisk//dev/sde.
grub-install: info: Scanning for ldm devices on disk hostdisk//dev/sde.
grub-install: info: scanning hostdisk//dev/sde for LDM.
grub-install: info: no LDM signature found.
grub-install: info: Scanning for lvm devices on disk hostdisk//dev/sde.
grub-install: info: no LVM signature found.
grub-install: info: Partition 4 starts from 2048.
grub-install: info: drive = 0.
grub-install: info: the size of hostdisk//dev/sde is 1953525168.
grub-install: info: guessed root_dev `hostdisk//dev/sde' from dir `/boot/grub/i386-pc'.
grub-install: info: setting the root device to `hostdisk//dev/sde,msdos5'.
grub-install: info: saving <1,0,512>.
grub-install: info: saving <2,0,512>.
grub-install: info: saving <3,0,512>.
grub-install: info: saving <4,0,512>.
grub-install: info: saving <5,0,512>.
grub-install: info: saving <6,0,512>.
grub-install: info: saving <7,0,512>.
grub-install: info: saving <8,0,512>.
grub-install: info: saving <9,0,512>.
grub-install: info: saving <10,0,512>.
grub-install: info: saving <11,0,512>.
grub-install: info: saving <12,0,512>.
grub-install: info: saving <13,0,512>.
grub-install: info: saving <14,0,512>.
grub-install: info: saving <15,0,512>.
grub-install: info: saving <16,0,512>.
grub-install: info: saving <17,0,512>.
grub-install: info: saving <18,0,512>.
grub-install: info: saving <19,0,512>.
grub-install: info: saving <20,0,512>.
grub-install: info: saving <21,0,512>.
grub-install: info: saving <22,0,512>.
grub-install: info: saving <23,0,512>.
grub-install: info: saving <24,0,512>.
grub-install: info: saving <25,0,512>.
grub-install: info: saving <26,0,512>.
grub-install: info: saving <27,0,512>.
grub-install: info: saving <28,0,512>.
grub-install: info: saving <29,0,512>.
grub-install: info: saving <30,0,512>.
grub-install: info: saving <31,0,512>.
grub-install: info: saving <32,0,512>.
grub-install: info: saving <33,0,512>.
grub-install: info: saving <34,0,512>.
grub-install: info: saving <35,0,512>.
grub-install: info: saving <36,0,512>.
grub-install: info: saving <37,0,512>.
grub-install: info: saving <38,0,512>.
grub-install: info: saving <39,0,512>.
grub-install: info: saving <40,0,512>.
grub-install: info: saving <41,0,512>.
grub-install: info: saving <42,0,512>.
grub-install: info: saving <43,0,512>.
grub-install: info: saving <44,0,512>.
grub-install: info: saving <45,0,512>.
grub-install: info: saving <46,0,512>.
grub-install: info: saving <47,0,512>.
grub-install: info: saving <48,0,512>.
grub-install: info: saving <49,0,512>.
grub-install: info: saving <50,0,512>.
grub-install: info: saving <51,0,512>.
grub-install: info: saving <52,0,512>.
grub-install: info: saving <53,0,512>.
grub-install: info: saving <54,0,512>.
grub-install: info: saving <55,0,512>.
grub-install: info: saving <56,0,512>.
grub-install: info: saving <57,0,512>.
grub-install: info: saving <58,0,512>.
grub-install: info: saving <59,0,512>.
grub-install: info: saving <60,0,512>.
grub-install: info: saving <61,0,512>.
grub-install: info: saving <62,0,512>.
grub-install: info: saving <63,0,512>.
grub-install: info: saving <64,0,512>.
grub-install: info: saving <65,0,512>.
grub-install: info: saving <66,0,512>.
grub-install: info: saving <67,0,512>.
grub-install: info: saving <68,0,512>.
grub-install: info: saving <69,0,512>.
grub-install: info: saving <70,0,512>.
grub-install: info: saving <71,0,512>.
grub-install: info: saving <72,0,512>.
grub-install: info: saving <73,0,512>.
grub-install: info: saving <74,0,512>.
grub-install: info: saving <75,0,512>.
grub-install: info: saving <76,0,512>.
grub-install: info: saving <77,0,512>.
grub-install: info: saving <78,0,512>.
grub-install: info: saving <79,0,512>.
grub-install: info: saving <80,0,512>.
grub-install: info: saving <81,0,512>.
grub-install: info: saving <82,0,512>.
grub-install: info: saving <83,0,512>.
grub-install: info: saving <84,0,512>.
grub-install: info: saving <85,0,512>.
grub-install: info: saving <86,0,512>.
grub-install: info: saving <87,0,512>.
grub-install: info: saving <88,0,512>.
grub-install: info: saving <89,0,512>.
grub-install: info: saving <90,0,512>.
grub-install: info: saving <91,0,512>.
grub-install: info: saving <92,0,512>.
grub-install: info: saving <93,0,512>.
grub-install: info: saving <94,0,512>.
grub-install: info: saving <95,0,512>.
grub-install: info: saving <96,0,512>.
grub-install: info: saving <97,0,512>.
grub-install: info: saving <98,0,512>.
grub-install: info: saving <99,0,512>.
grub-install: info: saving <100,0,512>.
grub-install: info: saving <101,0,512>.
grub-install: info: saving <102,0,512>.
grub-install: info: saving <103,0,512>.
grub-install: info: saving <104,0,512>.
grub-install: info: saving <105,0,512>.
grub-install: info: saving <106,0,512>.
Installation finished. No error reported.
root@srv:~#
Good weekend!
Boris
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Hello,
Something went wrong with my previous message, dont know why, but will send again...
results.txt from #/usr/sbin/bootinfoscript
What I mean with 'the system will not boot', in a bit of detail:
If I try to boot the system with the old nvme m.2 physically removed, the system goes through its normal supermicro boot screens.
Then waits for about 1-2 minutes with just an underscore in the top left corner of the screen...
Afther the 1-2 minutes it tries to boot of the network.
If I try to boot the system with the old nvme m.2 physically present, the system goes through its normal boot screens.
Then waits for a few seconds with an underscore in the top left corner, then starts a non-updated grub.
The system boots and everything works.
I cannot see any error messages, and I dont think it gets to grubs stage-1 on the sata disk (although I am not 100% on that).
Output of #blkid:
Output of partition layout: ? is fstab sufficient?
About the mbr vs uefi question, I am pretty sure the system boots using mbr, but not 100%
The supemicro offers a 'both' option (mbr & uefi) that was set as default and I did not change on install.
I did try setting it to 'legacy' (mbr only), but that did not change anything I could see.
It is entirely possible that some quirks are present, that can perhaps be handled by using a sata drive?
Ok, hope this message makes it.
I will start going through this info as well, there is a lot more to chew on...
Hope someone finds something obviously wrong and easy to fix
If not, many thanks for the help! & have a good weekend!
Boris
Something went wrong with my previous message, dont know why, but will send again...
results.txt from #/usr/sbin/bootinfoscript
Code: Select all
Boot Info Script 0.78 [09 October 2019]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
=> No boot loader is installed in the MBR of /dev/sdb.
=> No boot loader is installed in the MBR of /dev/sdc.
=> No boot loader is installed in the MBR of /dev/sdd.
=> Grub2 (v2.00) is installed in the MBR of /dev/sde and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos5)/boot/grub. It also embeds following components:
modules
---------------------------------------------------------------------------
fshelp ext2 part_msdos biosdisk
---------------------------------------------------------------------------
sda1: __________________________________________________________________________
File system: linux_raid_member
Boot sector type: -
Boot sector info:
sdb1: __________________________________________________________________________
File system: linux_raid_member
Boot sector type: -
Boot sector info:
sdc1: __________________________________________________________________________
File system: linux_raid_member
Boot sector type: -
Boot sector info:
sdd1: __________________________________________________________________________
File system: linux_raid_member
Boot sector type: -
Boot sector info:
sde1: __________________________________________________________________________
File system: Extended Partition
Boot sector type: -
Boot sector info:
sde5: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Debian GNU/Linux 12 (bookworm)
Boot files: /boot/grub/grub.cfg /etc/fstab
/boot/grub/i386-pc/core.img
sde6: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
md/0: __________________________________________________________________________
File system: LVM2_member
Boot sector type: -
Boot sector info:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000VN004-2M21
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 4,294,967,295 4,294,967,295 ee GPT
GUID Partition Table detected.
Partition Attrs Start Sector End Sector # of Sectors System
/dev/sda1 2,04815,628,052,47915,628,050,432 RAID partition (Linux)
Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000VN004-2M21
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 1 4,294,967,295 4,294,967,295 ee GPT
GUID Partition Table detected.
Partition Attrs Start Sector End Sector # of Sectors System
/dev/sdb1 2,04815,628,052,47915,628,050,432 RAID partition (Linux)
Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
Drive: sdc _____________________________________________________________________
Disk /dev/sdc: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000VN004-2M21
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdc1 1 4,294,967,295 4,294,967,295 ee GPT
GUID Partition Table detected.
Partition Attrs Start Sector End Sector # of Sectors System
/dev/sdc1 2,04815,628,052,47915,628,050,432 RAID partition (Linux)
Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
Drive: sdd _____________________________________________________________________
Disk /dev/sdd: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000VN004-2M21
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdd1 1 4,294,967,295 4,294,967,295 ee GPT
GUID Partition Table detected.
Partition Attrs Start Sector End Sector # of Sectors System
/dev/sdd1 2,04815,628,052,47915,628,050,432 RAID partition (Linux)
Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
Drive: sde _____________________________________________________________________
Disk /dev/sde: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WDS100T1R0A
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sde1 2,046 488,396,799 488,394,754 5 Extended
/dev/sde5 * 2,048 439,453,695 439,451,648 83 Linux
/dev/sde6 439,455,744 488,396,799 48,941,056 82 Linux swap / Solaris
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/mapper/Raid5_lv_group-Raid5_lv_name e49077ef-fcf0-4528-bb8e-b35744376d9a ext4
/dev/md0 HFoF0H-STax-U8yl-JRvf-lUHd-ZymR-iRC9I3 LVM2_member
/dev/nvme0n1p5 02fa313b-9fed-44f1-aa07-94b287507c8d ext4
/dev/nvme0n1p6 f7e9ad82-4fec-4606-818c-a1ad663e62a0 swap
/dev/sda1 4e830ac0-e487-afae-dae8-a8657adb04e7 linux_raid_member srv:0
/dev/sdb1 4e830ac0-e487-afae-dae8-a8657adb04e7 linux_raid_member srv:0
/dev/sdc1 4e830ac0-e487-afae-dae8-a8657adb04e7 linux_raid_member srv:0
/dev/sdd1 4e830ac0-e487-afae-dae8-a8657adb04e7 linux_raid_member srv:0
/dev/sde5 02fa313b-9fed-44f1-aa07-94b287507c8d ext4
/dev/sde6 f7e9ad82-4fec-4606-818c-a1ad663e62a0 swap
========================= "ls -l /dev/disk/by-id" output: ======================
total 0
lrwxrwxrwx 1 root root 9 May 17 11:14 ata-ST8000VN004-2M2101_WSD07N9X -> ../../sda
lrwxrwxrwx 1 root root 10 May 17 11:14 ata-ST8000VN004-2M2101_WSD07N9X-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 May 17 11:14 ata-ST8000VN004-2M2101_WSD0R2KW -> ../../sdb
lrwxrwxrwx 1 root root 10 May 17 11:14 ata-ST8000VN004-2M2101_WSD0R2KW-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 May 17 11:14 ata-ST8000VN004-2M2101_WSD0R2NF -> ../../sdc
lrwxrwxrwx 1 root root 10 May 17 11:14 ata-ST8000VN004-2M2101_WSD0R2NF-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 May 17 11:14 ata-ST8000VN004-2M2101_WSD0ZPPE -> ../../sdd
lrwxrwxrwx 1 root root 10 May 17 11:14 ata-ST8000VN004-2M2101_WSD0ZPPE-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 9 May 17 14:25 ata-WDC_WDS100T1R0A-68A4W0_22196L800352 -> ../../sde
lrwxrwxrwx 1 root root 10 May 17 14:25 ata-WDC_WDS100T1R0A-68A4W0_22196L800352-part1 -> ../../sde1
lrwxrwxrwx 1 root root 10 May 17 14:25 ata-WDC_WDS100T1R0A-68A4W0_22196L800352-part5 -> ../../sde5
lrwxrwxrwx 1 root root 10 May 17 14:25 ata-WDC_WDS100T1R0A-68A4W0_22196L800352-part6 -> ../../sde6
lrwxrwxrwx 1 root root 10 May 17 11:14 dm-name-Raid5_lv_group-Raid5_lv_name -> ../../dm-0
lrwxrwxrwx 1 root root 10 May 17 11:14 dm-uuid-LVM-MLbb301aYRWq9J1Irio9CgFnHKm1awxMLzO2lyQid92Pi2BFeKISk1Vf519zvzL1 -> ../../dm-0
lrwxrwxrwx 1 root root 9 May 17 11:14 lvm-pv-uuid-HFoF0H-STax-U8yl-JRvf-lUHd-ZymR-iRC9I3 -> ../../md0
lrwxrwxrwx 1 root root 9 May 17 11:14 md-name-srv:0 -> ../../md0
lrwxrwxrwx 1 root root 9 May 17 11:14 md-uuid-4e830ac0:e487afae:dae8a865:7adb04e7 -> ../../md0
lrwxrwxrwx 1 root root 13 May 17 11:14 nvme-eui.002538d211409cb6 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 May 17 11:14 nvme-eui.002538d211409cb6-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 May 17 11:14 nvme-eui.002538d211409cb6-part5 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 May 17 11:14 nvme-eui.002538d211409cb6-part6 -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 13 May 17 11:14 nvme-Samsung_SSD_980_250GB_S64BNJ0R208131L -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 May 17 11:14 nvme-Samsung_SSD_980_250GB_S64BNJ0R208131L-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 May 17 11:14 nvme-Samsung_SSD_980_250GB_S64BNJ0R208131L-part5 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 May 17 11:14 nvme-Samsung_SSD_980_250GB_S64BNJ0R208131L-part6 -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 9 May 17 11:14 wwn-0x5000c500d569065b -> ../../sdd
lrwxrwxrwx 1 root root 10 May 17 11:14 wwn-0x5000c500d569065b-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 9 May 17 11:14 wwn-0x5000c500d5691813 -> ../../sdc
lrwxrwxrwx 1 root root 10 May 17 11:14 wwn-0x5000c500d5691813-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 May 17 11:14 wwn-0x5000c500d5692757 -> ../../sdb
lrwxrwxrwx 1 root root 10 May 17 11:14 wwn-0x5000c500d5692757-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 May 17 11:14 wwn-0x5000c500d56c36c0 -> ../../sda
lrwxrwxrwx 1 root root 10 May 17 11:14 wwn-0x5000c500d56c36c0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 May 17 14:25 wwn-0x5001b448b0824d3f -> ../../sde
lrwxrwxrwx 1 root root 10 May 17 14:25 wwn-0x5001b448b0824d3f-part1 -> ../../sde1
lrwxrwxrwx 1 root root 10 May 17 14:25 wwn-0x5001b448b0824d3f-part5 -> ../../sde5
lrwxrwxrwx 1 root root 10 May 17 14:25 wwn-0x5001b448b0824d3f-part6 -> ../../sde6
========================= "ls -R /dev/mapper/" output: =========================
/dev/mapper:
control
Raid5_lv_group-Raid5_lv_name
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/mapper/Raid5_lv_group-Raid5_lv_name /home ext4 (rw,relatime,stripe=384)
/dev/sde5 / ext4 (rw,relatime,errors=remount-ro)
=========================== sde5/boot/grub/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 ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
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 part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
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=C
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
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
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 6.1.0-9-amd64 ...'
linux /boot/vmlinuz-6.1.0-9-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.1.0-9-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-02fa313b-9fed-44f1-aa07-94b287507c8d' {
menuentry 'Debian GNU/Linux, with Linux 6.1.0-9-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-9-amd64-advanced-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 6.1.0-9-amd64 ...'
linux /boot/vmlinuz-6.1.0-9-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.1.0-9-amd64
}
menuentry 'Debian GNU/Linux, with Linux 6.1.0-9-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-9-amd64-recovery-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 6.1.0-9-amd64 ...'
linux /boot/vmlinuz-6.1.0-9-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.1.0-9-amd64
}
menuentry 'Debian GNU/Linux, with Linux 6.1.0-1-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-1-amd64-advanced-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 6.1.0-1-amd64 ...'
linux /boot/vmlinuz-6.1.0-1-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.1.0-1-amd64
}
menuentry 'Debian GNU/Linux, with Linux 6.1.0-1-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.1.0-1-amd64-recovery-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 6.1.0-1-amd64 ...'
linux /boot/vmlinuz-6.1.0-1-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.1.0-1-amd64
}
menuentry 'Debian GNU/Linux, with Linux 6.0.0-6-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.0.0-6-amd64-advanced-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 6.0.0-6-amd64 ...'
linux /boot/vmlinuz-6.0.0-6-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.0.0-6-amd64
}
menuentry 'Debian GNU/Linux, with Linux 6.0.0-6-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.0.0-6-amd64-recovery-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 6.0.0-6-amd64 ...'
linux /boot/vmlinuz-6.0.0-6-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-6.0.0-6-amd64
}
menuentry 'Debian GNU/Linux, with Linux 5.18.0-3-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.18.0-3-amd64-advanced-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 5.18.0-3-amd64 ...'
linux /boot/vmlinuz-5.18.0-3-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.18.0-3-amd64
}
menuentry 'Debian GNU/Linux, with Linux 5.18.0-3-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.18.0-3-amd64-recovery-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 5.18.0-3-amd64 ...'
linux /boot/vmlinuz-5.18.0-3-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.18.0-3-amd64
}
menuentry 'Debian GNU/Linux, with Linux 4.19.0-17-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-17-amd64-advanced-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 4.19.0-17-amd64 ...'
linux /boot/vmlinuz-4.19.0-17-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.19.0-17-amd64
}
menuentry 'Debian GNU/Linux, with Linux 4.19.0-17-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-17-amd64-recovery-02fa313b-9fed-44f1-aa07-94b287507c8d' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd4,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 02fa313b-9fed-44f1-aa07-94b287507c8d
else
search --no-floppy --fs-uuid --set=root 02fa313b-9fed-44f1-aa07-94b287507c8d
fi
echo 'Loading Linux 4.19.0-17-amd64 ...'
linux /boot/vmlinuz-4.19.0-17-amd64 root=UUID=02fa313b-9fed-44f1-aa07-94b287507c8d ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.19.0-17-amd64
}
}
### 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/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### 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 ###
--------------------------------------------------------------------------------
=============================== sde5/etc/fstab: ================================
--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p5 during installation, now on /dev/sde5
UUID=02fa313b-9fed-44f1-aa07-94b287507c8d / ext4 errors=remount-ro 0 1
# swap was on /dev/nvme0n1p6 during installation, now on /dev/sde6
UUID=f7e9ad82-4fec-4606-818c-a1ad663e62a0 none swap sw 0 0
# home mounted as raid array
/dev/mapper/Raid5_lv_group-Raid5_lv_name /home ext4 defaults 0 2
--------------------------------------------------------------------------------
=================== sde5: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
198.159191132 = 212.771811328 boot/grub/grub.cfg 1
198.167655945 = 212.780900352 boot/grub/i386-pc/core.img 1
0.658241272 = 0.706781184 boot/vmlinuz-4.19.0-17-amd64 1
15.742443085 = 16.903319552 boot/vmlinuz-5.18.0-3-amd64 2
142.887153625 = 153.423912960 boot/vmlinuz-6.0.0-6-amd64 1
136.516662598 = 146.583650304 boot/vmlinuz-6.1.0-1-amd64 1
186.508388519 = 200.261857280 boot/vmlinuz-6.1.0-9-amd64 2
186.508388519 = 200.261857280 vmlinuz 2
136.516662598 = 146.583650304 vmlinuz.old 1
72.321285248 = 77.654388736 boot/initrd.img-4.19.0-17-amd64 3
11.166645050 = 11.990093824 boot/initrd.img-5.18.0-3-amd64 1
12.674446106 = 13.609082880 boot/initrd.img-6.0.0-6-amd64 1
13.227535248 = 14.202957824 boot/initrd.img-6.1.0-1-amd64 3
13.454238892 = 14.446379008 boot/initrd.img-6.1.0-9-amd64 1
13.454238892 = 14.446379008 initrd.img 1
13.227535248 = 14.202957824 initrd.img.old 3
=============================== StdErr Messages: ===============================
/usr/sbin/bootinfoscript: line 2553: 46883348480S: value too great for base (error token is "46883348480S")
If I try to boot the system with the old nvme m.2 physically removed, the system goes through its normal supermicro boot screens.
Then waits for about 1-2 minutes with just an underscore in the top left corner of the screen...
Afther the 1-2 minutes it tries to boot of the network.
If I try to boot the system with the old nvme m.2 physically present, the system goes through its normal boot screens.
Then waits for a few seconds with an underscore in the top left corner, then starts a non-updated grub.
The system boots and everything works.
I cannot see any error messages, and I dont think it gets to grubs stage-1 on the sata disk (although I am not 100% on that).
Output of #blkid:
Code: Select all
root@srv:~# blkid
/dev/nvme0n1p5: UUID="02fa313b-9fed-44f1-aa07-94b287507c8d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ed4c874d-05"
/dev/nvme0n1p6: UUID="f7e9ad82-4fec-4606-818c-a1ad663e62a0" TYPE="swap" PARTUUID="ed4c874d-06"
/dev/sdd1: UUID="4e830ac0-e487-afae-dae8-a8657adb04e7" UUID_SUB="3fa4c5bf-ef3a-b20e-a29c-f1fb7681b2e4" LABEL="srv:0" TYPE="linux_raid_member" PARTLABEL="Raid_Disk4" PARTUUID="650f4640-50c2-4470-a670-f45492f3bc8d"
/dev/sdb1: UUID="4e830ac0-e487-afae-dae8-a8657adb04e7" UUID_SUB="62647794-96c0-badd-9b9b-7b7a70895ec3" LABEL="srv:0" TYPE="linux_raid_member" PARTLABEL="Raid_disk3" PARTUUID="42c0f3bd-8457-44d6-841d-3b25a7210215"
/dev/md0: UUID="HFoF0H-STax-U8yl-JRvf-lUHd-ZymR-iRC9I3" TYPE="LVM2_member"
/dev/mapper/Raid5_lv_group-Raid5_lv_name: UUID="e49077ef-fcf0-4528-bb8e-b35744376d9a" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sde5: UUID="02fa313b-9fed-44f1-aa07-94b287507c8d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ed4c874d-05"
/dev/sde6: UUID="f7e9ad82-4fec-4606-818c-a1ad663e62a0" TYPE="swap" PARTUUID="ed4c874d-06"
/dev/sdc1: UUID="4e830ac0-e487-afae-dae8-a8657adb04e7" UUID_SUB="daa2fa23-9c7b-c3ee-8efa-3b7fbda5a2df" LABEL="srv:0" TYPE="linux_raid_member" PARTLABEL="Raid_Disk1" PARTUUID="b58b7db0-55f8-44df-88f4-e510b4ef30c9"
/dev/sda1: UUID="4e830ac0-e487-afae-dae8-a8657adb04e7" UUID_SUB="f222e6cf-aa77-1ee8-4fa8-6b9d72321865" LABEL="srv:0" TYPE="linux_raid_member" PARTLABEL="Raid_Disk2" PARTUUID="2c76a169-b843-4825-b665-6c392c898648"
Output of partition layout: ? is fstab sufficient?
Code: Select all
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p5 during installation, now on /dev/sde5
UUID=02fa313b-9fed-44f1-aa07-94b287507c8d / ext4 errors=remount-ro 0 1
# swap was on /dev/nvme0n1p6 during installation, now on /dev/sde6
UUID=f7e9ad82-4fec-4606-818c-a1ad663e62a0 none swap sw 0 0
# home mounted as raid array
/dev/mapper/Raid5_lv_group-Raid5_lv_name /home ext4 defaults 0 2
The supemicro offers a 'both' option (mbr & uefi) that was set as default and I did not change on install.
I did try setting it to 'legacy' (mbr only), but that did not change anything I could see.
It is entirely possible that some quirks are present, that can perhaps be handled by using a sata drive?
Ok, hope this message makes it.
I will start going through this info as well, there is a lot more to chew on...
Hope someone finds something obviously wrong and easy to fix
If not, many thanks for the help! & have a good weekend!
Boris
-
- df -h | grep > 20TiB
- Posts: 1418
- Joined: 2012-10-06 05:31
- Location: /dev/chair
- Has thanked: 80 times
- Been thanked: 191 times
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Neither do I. In fact it sounds to me like the BIOS isn't trying to boot (or isn't finding) the MBR on that disk at all.PanToffel wrote: ↑2023-05-19 09:58 If I try to boot the system with the old nvme m.2 physically removed, the system goes through its normal supermicro boot screens.
Then waits for about 1-2 minutes with just an underscore in the top left corner of the screen...
Afther the 1-2 minutes it tries to boot of the network...
I cannot see any error messages, and I dont think it gets to grubs stage-1 on the sata disk.
I'd be thinking this is probably a BIOS issue, and if it were me, at this point I'd double check legacy boot, boot device order etc. in BIOS, then yank a known-bootable SSD from another machine (or more likely my pile of random trash) and see if it will at least try to boot that...
Or see if your problem disk will boot in another box for that matter.
Other random thoughts:
If this board has many SATA ports (e.g. onboard RAID/HBA), it's possible not all of them are directly BIOS bootable.
You're trying to boot an extended partition (sde5). While this should work, it's not technically a supported configuration as far as certain *other* OSes are concerned. It's vaguely possible the BIOS doesn't like this, and ignores the drive because it doesn't have a primary partition with the boot flag set. That's a pretty anachronistic thing to do, but hey, maybe.
Not what I was looking for, but nevermind, boot-info-script appears to collect it ("Drive/Partition Info" section).
Kinda difficult to offer much help on a "no boot, no messages" case without being physically in front of the machine TBH. That said I'm not exactly an expert on this, and there are wiser heads around here (subtly invokes @p.H) who may have some ideas.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
-
- Posts: 444
- Joined: 2023-02-07 13:35
- Been thanked: 105 times
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Configuration looks fine, with the obvious exception of the duplicated filesystem UUIDs. Did you try changing those?
Can we eliminate hardware failure here? Are the cables and/or connectors sound?
Can we eliminate hardware failure here? Are the cables and/or connectors sound?
Jeder nach seinen Fähigkeiten, jedem nach seinen Bedürfnissen.
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Hello,
I will try swapping hardware ( known bootable drive in server, not booting server drive in other pc etc, to further isolate / check against hardware / bios issues ).
Will have to do that on Monday though, I cannot get to the hardware easily over the weekend.
Will also check if supermicro published newer versions of the bios for this board, or if there are known issues that may explain this.
I don't think there is something really wrong with the cabling or connectors, the sata ssd works well as system drive for over a year now, no smart or other apparent errors.
If the hardware checks out ok, I will try to change the UUID's ... I have been hesitant to do that because I may end up with a not booting system that is in use.
Reporting back on Monday,
Have a good weekend & thanks for the help
Boris
I will try swapping hardware ( known bootable drive in server, not booting server drive in other pc etc, to further isolate / check against hardware / bios issues ).
Will have to do that on Monday though, I cannot get to the hardware easily over the weekend.
Will also check if supermicro published newer versions of the bios for this board, or if there are known issues that may explain this.
I don't think there is something really wrong with the cabling or connectors, the sata ssd works well as system drive for over a year now, no smart or other apparent errors.
If the hardware checks out ok, I will try to change the UUID's ... I have been hesitant to do that because I may end up with a not booting system that is in use.
Reporting back on Monday,
Have a good weekend & thanks for the help
Boris
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Hello,
Swapped some hardware... looks like my work pc boots fine using the sata ssd (with the ssd directly plugged into the motherboard).
So I just ordered a usb3 to sata III converter, to see if the sata ssd will boot over usb3.
If that works, I think the problem might have been the delock pcie to sata expansion card that was used to connect the sata ssd to the supermicro board.
Is strange though, this is a quite standard pcie card (marvell chip), cant find or expect many issues with it.
I am hesitant to use sata ports 1-4 as they are in use for the raid array and I don't want to mess that up (as well).
Will take a while for the converter to arrive, perhaps results on wednesday.
Many thanks for the help,
Boris
Swapped some hardware... looks like my work pc boots fine using the sata ssd (with the ssd directly plugged into the motherboard).
So I just ordered a usb3 to sata III converter, to see if the sata ssd will boot over usb3.
If that works, I think the problem might have been the delock pcie to sata expansion card that was used to connect the sata ssd to the supermicro board.
Is strange though, this is a quite standard pcie card (marvell chip), cant find or expect many issues with it.
I am hesitant to use sata ports 1-4 as they are in use for the raid array and I don't want to mess that up (as well).
Will take a while for the converter to arrive, perhaps results on wednesday.
Many thanks for the help,
Boris
-
- df -h | grep > 20TiB
- Posts: 1418
- Joined: 2012-10-06 05:31
- Location: /dev/chair
- Has thanked: 80 times
- Been thanked: 191 times
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Well, if you'd mentioned that this was connected to a cheap PCIE SATA card rather than the onboard ports, I'd have gone for that straight away.
Aside, if your HBA is indeed bootable, it'll have it's own option ROM. That may need to be enabled in the BIOS (and there may be int13 related options as well).
Personally I hate marvel based cards with a passion, those that I have used have been thoroughly unreliable. I'll take an ebay server-pull LSI HBA over any number of them.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Hi Steve,
Sorry I did not mention that right away then, might have saved some time.
When I was assembling the system I never planned to use the pcie sata adapter for daily use, only when e.g. having to copy stuff from m.2 or to/from the individual raid disks in case of problems.
Then the m.2 failed twice and there are only 4 sata ports natively on the board. Tried the sata ssd through the cheap pcie adapter and it looked fine, guess that was not the full story.
Actually forgot the exact hardware situation until I pulled the drive out for testing in the other machine...
If the system boots using the usb trick, I'll hunt for a LSI HBA, test that and use it for 'daily use'.
I have been using linux for a long time, but my experience with 'cheap' is not necessarily 'poor', sometimes its the other way around (network cards from 3m spring to mind, not cheap...).
But if LSI HBA's 'just work' I go for that instantly... anything else I have to look for?
Many thanks for the help and the time.
Boris
Sorry I did not mention that right away then, might have saved some time.
When I was assembling the system I never planned to use the pcie sata adapter for daily use, only when e.g. having to copy stuff from m.2 or to/from the individual raid disks in case of problems.
Then the m.2 failed twice and there are only 4 sata ports natively on the board. Tried the sata ssd through the cheap pcie adapter and it looked fine, guess that was not the full story.
Actually forgot the exact hardware situation until I pulled the drive out for testing in the other machine...
If the system boots using the usb trick, I'll hunt for a LSI HBA, test that and use it for 'daily use'.
I have been using linux for a long time, but my experience with 'cheap' is not necessarily 'poor', sometimes its the other way around (network cards from 3m spring to mind, not cheap...).
But if LSI HBA's 'just work' I go for that instantly... anything else I have to look for?
Many thanks for the help and the time.
Boris
-
- df -h | grep > 20TiB
- Posts: 1418
- Joined: 2012-10-06 05:31
- Location: /dev/chair
- Has thanked: 80 times
- Been thanked: 191 times
Re: Cannot boot from new ssd after resture ( Grub issue ? )
My leaning toward LSI HBAs is heavily influenced by my use of ZFS and their popularity for FreeNAS builds, along with the exceptional port/price ratio to be found with used server cards. I've been running a pair of IBM M1015 (SAS2008) 8-port HBAs in my home fileserver (for 26 SATA ports in total ) nearly 10 years now, and they're still serving well. The other obvious advantage of a SAS HBA is of course support for SAS (drives, backplanes etc.) as well as SATA.
My dislike of consumer "SATA cards" is mostly down to experience with earlier iterations of the same build, namely a bunch of marvel and asmedia based 4-port cards dropping drives at random inconvenient times.
That may well all be old news at this point of course, as hardware has likely improved. Many grains of salt required.
My 2c? Poke about on servethehome and their forum. See what everyone else is using. The place is a goldmine for storage-related information.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
Re: Cannot boot from new ssd after resture ( Grub issue ? )
Hello,
It took a little while, bank holiday and longer delivery time for stuff... but continued hardware swapping & testing today...
I think I pretty much found the issue, booting the sata ssd disk with a sata to usb3 adapter works.
So I think the boot issue is pretty much narrowed down to the marvel pcie-sata adapter board from delock ( as predicted by @steve_v ).
I have no idea why the sata ssd did not boot over that adapter board, just that the sata to usb3 adapter worked, and it did not.
I removed both the pcie-sata adapter board and the m.2 drive, still booting ok... they will not return to the machine
I will hunt for a good lsi hba, and use that for production / longer time use, as I've heard that this setup may not be the most stable.
But it works, the immediate problem is solved! Thanks a lot for all the help!
Boris
MODERATOR EDIT (Aki) Wed Jun 7 16:46:38 UTC 2023: added [Solved] tag to the first post.
It took a little while, bank holiday and longer delivery time for stuff... but continued hardware swapping & testing today...
I think I pretty much found the issue, booting the sata ssd disk with a sata to usb3 adapter works.
So I think the boot issue is pretty much narrowed down to the marvel pcie-sata adapter board from delock ( as predicted by @steve_v ).
I have no idea why the sata ssd did not boot over that adapter board, just that the sata to usb3 adapter worked, and it did not.
I removed both the pcie-sata adapter board and the m.2 drive, still booting ok... they will not return to the machine
I will hunt for a good lsi hba, and use that for production / longer time use, as I've heard that this setup may not be the most stable.
But it works, the immediate problem is solved! Thanks a lot for all the help!
Boris
MODERATOR EDIT (Aki) Wed Jun 7 16:46:38 UTC 2023: added [Solved] tag to the first post.
Re: Cannot boot from new ssd after resture ( Grub issue ? )
I found some reports of people booting from this card.
as @steve_v mentioned above, there might be an option in motherboard's BIOS that you need to enable in order to boot from a PCIe card. still worth to get a proper HBA card but for now this might be the more stable solution between that and using the USB-to-SATA adapter.
in particular, you could check these BIOS options:
"Storage Option ROM/UEFI Driver" (select "Legacy")
"CPU SLOT1 PCI-E 3.0 X16 OPROM" (if the card is connected to the corresponding slot then select "Legacy")
"Native PCIE Enable" (select "Enable")
I'm not sure that any of that will actually help with your boot issue and if you try that, probably you should write down what each option was set to initially, just in case.
as @steve_v mentioned above, there might be an option in motherboard's BIOS that you need to enable in order to boot from a PCIe card. still worth to get a proper HBA card but for now this might be the more stable solution between that and using the USB-to-SATA adapter.
in particular, you could check these BIOS options:
"Storage Option ROM/UEFI Driver" (select "Legacy")
"CPU SLOT1 PCI-E 3.0 X16 OPROM" (if the card is connected to the corresponding slot then select "Legacy")
"Native PCIE Enable" (select "Enable")
I'm not sure that any of that will actually help with your boot issue and if you try that, probably you should write down what each option was set to initially, just in case.
Re: [Solved] Cannot boot from new ssd after resture ( Grub issue ? )
Hello,
Its been awhile, but I was rereading this, and I thought it might be useful for others to know what did finally work in a stable way.
I got hold of a lsi sas 9341-4i made by broadcom + cable and installed that in the pci-e slot, and connected the sata ssd to the lsi hba card.
Physically removed the m.2 ssd card so that could not be in the way anymore ( no more identical uuid's present ).
Powered on, went through the hba card setup and supermicro bios, initially left things on default.
Tried to boot, and that worked partially. It got to the grub bootloading stage, but debian did not boot straight away.
Found a post ( https://www.thomas-krenn.com/de/wiki/Me ... atus_reg_3 )
where its mentioned that I should add:
intel_iommu=on and iommu=pt to the boot parameters in /etc/default/grub, then do #update-grub.
Did that, reboot, and this boots fine! Has been running without issues for almost a month now.
Hope this is useful to someone,
Many thanks for the help troubleshooting this!
Boris
Its been awhile, but I was rereading this, and I thought it might be useful for others to know what did finally work in a stable way.
I got hold of a lsi sas 9341-4i made by broadcom + cable and installed that in the pci-e slot, and connected the sata ssd to the lsi hba card.
Physically removed the m.2 ssd card so that could not be in the way anymore ( no more identical uuid's present ).
Powered on, went through the hba card setup and supermicro bios, initially left things on default.
Tried to boot, and that worked partially. It got to the grub bootloading stage, but debian did not boot straight away.
Found a post ( https://www.thomas-krenn.com/de/wiki/Me ... atus_reg_3 )
where its mentioned that I should add:
intel_iommu=on and iommu=pt to the boot parameters in /etc/default/grub, then do #update-grub.
Did that, reboot, and this boots fine! Has been running without issues for almost a month now.
Hope this is useful to someone,
Many thanks for the help troubleshooting this!
Boris