Felix, et al -- ...and then Felix Miata said... % [quote] % The BIOS boot partition is a partition on a data storage device that GNU GRUB uses ... % sometimes referred to as BIOS/GPT boot.[/quote] % https://en.wikipedia.org/wiki/BIOS_boot_partition Well, yeah. That makes sense. But ... I'm not using one. % % With disk partitioning, we need to see output from a partitioner. A narrative % alone won't do. Things like: Fair enough. I was hopeful it would be an easy answer :-)/2 % % bootinfoscript output % fdisk -l % parted -l % lsblk -f % cat /etc/fstab % etc. I can give you that sort of thing from my web server box, which is the exact same model with the exact same /dev/sda but without all of the other storage. So let's dig in, and maybe you can figure out how grub is actually doing anything here. jpo:~ # which bootinfoscript which: no bootinfoscript in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/home/local/sbin:/home/local/bin ) jpo:~ # fdisk -l /dev/sda Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors Disk model: SAMSUNG MZ7LN128 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: gpt Disk identifier: 13E41642-343B-4ECC-9D6D-E71607F98BC9 Device Start End Sectors Size Type /dev/sda1 2048 69208063 69206016 33G Linux swap /dev/sda2 69208064 136316927 67108864 32G Linux filesystem /dev/sda3 136316928 203425791 67108864 32G Linux filesystem /dev/sda4 203425792 250069646 46643855 22.2G Linux filesystem jpo:~ # parted /dev/sda u MiB p free Model: ATA SAMSUNG MZ7LN128 (scsi) Disk /dev/sda: 122104MiB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 0.02MiB 1.00MiB 0.98MiB Free Space 1 1.00MiB 33793MiB 33792MiB linux-swap(v1) jpo-swap swap 2 33793MiB 66561MiB 32768MiB xfs jposuse 3 66561MiB 99329MiB 32768MiB xfs jpoalt legacy_boot 4 99329MiB 122104MiB 22775MiB xfs jpo-ssd jpo:~ # df -kh | grep sda /dev/sda2 32G 11G 22G 32% / /dev/sda4 23G 20G 2.9G 87% /mnt/ssd jpo:~ # sudo lsblk -f | egrep 'NAME|sda' NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda sda1 swap jpo-swap aafd8c10-b00c-48bc-9566-57ea73f3a126 [SWAP] sda2 xfs jposuse 22fad8b5-8b95-4e26-bd39-d22d1f10a22e 21.8G 32% / sda3 xfs 8e904f43-38c5-4350-8fdb-a1eea8e4a560 sda4 xfs jpo-ssd d2692bbe-de41-4ddb-8975-4f69596994a7 2.9G 87% /mnt/ssd jpo:~ # egrep 'LABEL=jpo|swap' /etc/fstab LABEL=jposuse / xfs defaults 0 1 LABEL=jpo-ssd /mnt/ssd xfs defaults 0 2 UUID=aafd8c10-b00c-48bc-9566-57ea73f3a126 swap swap defaults 0 0 jpo:~ # ls -gohA /boot/grub2/ total 32K -rw-r--r-- 1 15 Jun 28 2021 device.map drwxr-xr-x 2 25 Jun 28 2021 fonts -rw------- 1 9.0K Jun 7 02:13 grub.cfg -rw-r--r-- 1 1.0K Jun 28 2021 grubenv drwxr-xr-x 2 8.0K Jun 28 2021 i386-pc drwxr-xr-x 3 22 Jun 28 2021 themes jpo:~ # cat /boot/grub2/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -f ${config_directory}/grubenv ]; then load_env -f ${config_directory}/grubenv elif [ -s $prefix/grubenv ]; then load_env fi if [ "${env_block}" ] ; then set env_block="(${root})${env_block}" export env_block load_env -f "${env_block}" fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry if [ "${env_block}" ] ; then save_env -f "${env_block}" next_entry fi set boot_once=true else set default="${saved_entry}" 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}" if [ "${env_block}" ] ; then save_env -f "${env_block}" saved_entry else save_env saved_entry fi 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_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi font="/usr/share/grub2/unicode.pf2" fi if loadfont $font ; then if [ "${grub_platform}" = "efi" ]; then echo "Please press 't' to show the boot menu on this console" fi set gfxmode=auto load_video insmod gfxterm fi terminal_input console terminal_output gfxterm insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi insmod gfxmenu loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans-Bold14.pf2 loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans10.pf2 loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans12.pf2 loadfont ($root)/boot/grub2/themes/openSUSE/ascii.pf2 insmod png set theme=($root)/boot/grub2/themes/openSUSE/theme.txt export theme if [ x${boot_once} = xtrue ]; then set timeout=0 elif [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=2 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=2 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/00_tuned ### set tuned_params="" set tuned_initrd="" ### END /etc/grub.d/00_tuned ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'openSUSE Leap 15.2' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.106-default ...' linux /boot/vmlinuz-5.3.18-lp152.106-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e splash=silent quiet mitigations=auto echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.106-default } submenu 'Advanced options for openSUSE Leap 15.2' --hotkey=1 $menuentry_id_option 'gnulinux-advanced-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.106-default' --hotkey=2 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.106-default-advanced-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.106-default ...' linux /boot/vmlinuz-5.3.18-lp152.106-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e splash=silent quiet mitigations=auto echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.106-default } menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.106-default (recovery mode)' --hotkey=3 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.106-default-recovery-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.106-default ...' linux /boot/vmlinuz-5.3.18-lp152.106-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.106-default } menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.78-default' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.78-default-advanced-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.78-default ...' linux /boot/vmlinuz-5.3.18-lp152.78-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e splash=silent quiet mitigations=auto echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.78-default } menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.78-default (recovery mode)' --hotkey=1 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.78-default-recovery-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.78-default ...' linux /boot/vmlinuz-5.3.18-lp152.78-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.78-default } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_memtest86+ ### ### END /etc/grub.d/20_memtest86+ ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### ### BEGIN /etc/grub.d/80_suse_btrfs_snapshot ### ### END /etc/grub.d/80_suse_btrfs_snapshot ### ### BEGIN /etc/grub.d/90_persistent ### ### END /etc/grub.d/90_persistent ### ### BEGIN /etc/grub.d/95_textmode ### if [ "${grub_platform}" = "efi" ]; then # On EFI systems we can only have graphics *or* serial, so allow the user # to switch between the two hiddenentry 'Text mode' --hotkey 't' { set textmode=true terminal_output console } fi ### END /etc/grub.d/95_textmode ### % % Long output can be susepasted with URI thereto provided. The problem is creating the long output; at that box I'm at a plain text console with no GUI support and no other computer nearby. I miss serial consoles and remote access! Thanks again! :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

Felix, et al -- ...and then Felix Miata said... % David T-G composed on 2022-10-17 21:59 (UTC): % % > The problem is creating the long output; at that box I'm at a plain text % > console with no GUI support and no other computer nearby. I miss serial % > consoles and remote access! % % # sudo zypper in susepaste unzip % # wget https://github.com/arvidjaar/bootinfoscript/archive/refs/heads/master.zip % # unzip master.zip % # sudo sh ./bootinfoscript-master/bootinfoscript | susepaste -n DavidTG -e 40320 I've done this for jpo, the working host: https://paste.opensuse.org/47504170 Of course, diskfarm is horked up, so it wouldn't be too helpful to go there. I suppose I might try a chroot from the rescue system to look like it's alive if you think there's anything useful ... % ... % I was under the impression that non-UEFI booting with GPT partitioned disks could % only be done from Grub2 installed to a BIOS boot partition. From what I can see in Same here. When the install worked I thought, hey, wow, it figured out what it needed :-) % the program output provided, you must be booting from Grub installed to a native % Linux partition on a GPT disk. I've never seen that before, and didn't know it was % possible. On MBR disks, it's what I've always done, never Grub purposely on any % MBR here. Somehow, though, I made it through an install and it Just Works -- twice! Yes, I'm very confused ... Thanks again :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

David T-G composed on 2022-10-18 03:48 (UTC):

I don't know why that didn't work. I just double-checked the previous run and confirmed the URL. But I get an error when I test the results ...

Another workaround (logged in as root): # opi pastebinit (agree) # sh ./bootinfoscript-master/bootinfoscript | pastebinit I tested pastebinit, and the URI worked. I didn't know it was in openSUSE repos (repositories/network:/utilities), as its origin AFAIK is *buntu or Debian. susepaste has persistence options that are not apparent in the pastebinit man page. Otherwise it's pretty much the same thing. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

Felix, et al -- ...and then Felix Miata said... % Felix Miata composed on 2022-10-18 00:22 (UTC-0400): % % > Another workaround (logged in as root): % % > # opi pastebinit I don't have opi installed, either. But I don't think that's critical here. ... % > I tested pastebinit, and the URI worked. I didn't know it was in openSUSE repos % % Actually this isn't the whole story. Apparently bootinfoscript behavior isn't the % same as I remember. It writes the relevant output to a file in spite of the pipe, Yep. I used --stdout on my first run, and I loaded from RESULTS.txt on my second. The bootinfoscript run seems to be fine. % and the file needs to be susepasted or pastebinited separately. I retested using % the output file from bootinfoscript, and pastebinit failed, but susepaste % succeeded. :p Gaaah! Not yet for me *sigh* I'll just read in the RESULTS.txt content here between your name and my signature. It's a little long, but not horrible. Meanwhile ... davidtg@jpo:~> sudo parted /dev/sda p Model: ATA SAMSUNG MZ7LN128 (scsi) Disk /dev/sda: 128GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 1 1049kB 35.4GB 35.4GB linux-swap(v1) jpo-swap swap 2 35.4GB 69.8GB 34.4GB xfs jposuse 3 69.8GB 104GB 34.4GB xfs jpoalt legacy_boot 4 104GB 128GB 23.9GB xfs jpo-ssd I wonder how I set "pmbr_boot" since that is the only thing that makes this look like we could have an MBR boot record on a GPT disk ... % ... % % Felix Miata Boot Info Script 0.78 [09 October 2019] ============================= Boot Info Summary: =============================== => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 105657120 of the same hard drive for core.img. core.img is at this location and looks for (,gpt2)/boot/grub2. It also embeds following components: modules --------------------------------------------------------------------------- fshelp xfs part_gpt biosdisk --------------------------------------------------------------------------- => No boot loader is installed in the MBR of /dev/sdb. => No boot loader is installed in the MBR of /dev/sdc. sda1: __________________________________________________________________________ File system: swap Boot sector type: - Boot sector info: sda2: __________________________________________________________________________ File system: xfs Boot sector type: - Boot sector info: Operating System: openSUSE Leap 15.2 Boot files: /boot/grub2/grub.cfg /etc/fstab /boot/grub2/i386-pc/core.img sda3: __________________________________________________________________________ File system: xfs Boot sector type: - Boot sector info: Operating System: Boot files: sda4: __________________________________________________________________________ File system: xfs Boot sector type: - Boot sector info: Operating System: Boot files: sdb1: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb2: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb4: __________________________________________________________________________ File system: ext2 Boot sector type: - Boot sector info: Operating System: Boot files: sdc1: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc2: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc4: __________________________________________________________________________ File system: vfat Boot sector type: FAT16 Boot sector info: According to the info in the boot sector, sdc4 starts at sector -775899136. But according to the info from fdisk, sdc4 starts at sector 7814035456. According to the info in the boot sector, sdc4 has 0 sectors. Operating System: Boot files: md/md41: _______________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: md/md42: _______________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: md/40: _________________________________________________________________________ File system: Boot sector type: - Boot sector info: ============================ Drive/Partition Info: ============================= Drive: sda _____________________________________________________________________ Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors Disk model: SAMSUNG MZ7LN128 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/sda1 * 1 250,069,679 250,069,679 ee GPT GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sda1 2,048 69,208,063 69,206,016 Swap partition (Linux) /dev/sda2 69,208,064 136,316,927 67,108,864 Data partition (Linux) /dev/sda3 B 136,316,928 203,425,791 67,108,864 Data partition (Linux) /dev/sda4 203,425,792 250,069,646 46,643,855 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdb _____________________________________________________________________ Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: ST4000VN008-2DR1 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,048 3,907,018,751 3,907,016,704 Data partition (Linux) /dev/sdb2 3,907,018,752 7,814,035,455 3,907,016,704 Data partition (Linux) /dev/sdb4 7,814,035,456 7,814,037,134 1,679 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdc _____________________________________________________________________ Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: ST4000VN008-2DR1 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,048 3,907,018,751 3,907,016,704 Data partition (Linux) /dev/sdc2 3,907,018,752 7,814,035,455 3,907,016,704 Data partition (Linux) /dev/sdc4 7,814,035,456 7,814,037,134 1,679 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set "blkid" output: ________________________________________________________________ Device UUID TYPE LABEL /dev/md40 /dev/md40p1 aad25743-100c-48f2-9581-adf1d6b32cd5 xfs 4TRaid10md /dev/md40p4 858502c5-6017-4381-9e6e-32af2ca87fe7 ext2 4TRaid10md-ext2 /dev/md41 4735f53c-7cdf-7758-e212-bec6aa2942e8 linux_raid_member jpo:40 /dev/md42 4735f53c-7cdf-7758-e212-bec6aa2942e8 linux_raid_member jpo:40 /dev/sda1 aafd8c10-b00c-48bc-9566-57ea73f3a126 swap jpo-swap /dev/sda2 22fad8b5-8b95-4e26-bd39-d22d1f10a22e xfs jposuse /dev/sda3 8e904f43-38c5-4350-8fdb-a1eea8e4a560 xfs /dev/sda4 d2692bbe-de41-4ddb-8975-4f69596994a7 xfs jpo-ssd /dev/sdb1 1d2ce819-ef7c-d123-267c-5ba58eddfc34 linux_raid_member jpo:md41 /dev/sdb2 1e4dec68-2c3f-8517-338d-243d5e63df65 linux_raid_member jpo:md42 /dev/sdb4 423d4b90-74d8-48e3-9638-51f6abbfa19a ext2 S4-...2X37-ext2 /dev/sdc1 1e4dec68-2c3f-8517-338d-243d5e63df65 linux_raid_member jpo:md42 /dev/sdc2 1d2ce819-ef7c-d123-267c-5ba58eddfc34 linux_raid_member jpo:md41 /dev/sdc4 22DD-1B4D vfat S4-KZTG-fat ========================= "ls -l /dev/disk/by-id" output: ====================== total 0 lrwxrwxrwx 1 root root 9 Aug 21 16:17 ata-SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 21 16:17 ata-SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 ata-SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 ata-SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Aug 21 16:17 ata-SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 ata-ST4000VN008-2DR166_ZDHB2X37 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 21 16:17 ata-ST4000VN008-2DR166_ZDHB2X37-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 ata-ST4000VN008-2DR166_ZDHB2X37-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 ata-ST4000VN008-2DR166_ZDHB2X37-part4 -> ../../sdb4 lrwxrwxrwx 1 root root 9 Sep 7 01:46 ata-ST4000VN008-2DR166_ZDHBKZTG -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 7 01:46 ata-ST4000VN008-2DR166_ZDHBKZTG-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 7 01:46 ata-ST4000VN008-2DR166_ZDHBKZTG-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 7 01:46 ata-ST4000VN008-2DR166_ZDHBKZTG-part4 -> ../../sdc4 lrwxrwxrwx 1 root root 10 Aug 21 16:17 md-name-jpo:40 -> ../../md40 lrwxrwxrwx 1 root root 12 Aug 21 16:17 md-name-jpo:40-part1 -> ../../md40p1 lrwxrwxrwx 1 root root 12 Aug 21 16:17 md-name-jpo:40-part4 -> ../../md40p4 lrwxrwxrwx 1 root root 10 Aug 21 16:17 md-name-jpo:md41 -> ../../md41 lrwxrwxrwx 1 root root 10 Aug 21 16:17 md-name-jpo:md42 -> ../../md42 lrwxrwxrwx 1 root root 10 Aug 21 16:17 md-uuid-1d2ce819:ef7cd123:267c5ba5:8eddfc34 -> ../../md41 lrwxrwxrwx 1 root root 10 Aug 21 16:17 md-uuid-1e4dec68:2c3f8517:338d243d:5e63df65 -> ../../md42 lrwxrwxrwx 1 root root 10 Aug 21 16:17 md-uuid-4735f53c:7cdf7758:e212bec6:aa2942e8 -> ../../md40 lrwxrwxrwx 1 root root 12 Aug 21 16:17 md-uuid-4735f53c:7cdf7758:e212bec6:aa2942e8-part1 -> ../../md40p1 lrwxrwxrwx 1 root root 12 Aug 21 16:17 md-uuid-4735f53c:7cdf7758:e212bec6:aa2942e8-part4 -> ../../md40p4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 scsi-0ATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-0ATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-0ATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-0ATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-0ATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 scsi-0ATA_ST4000VN008-2DR1_ZDHB2X37 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-0ATA_ST4000VN008-2DR1_ZDHB2X37-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-0ATA_ST4000VN008-2DR1_ZDHB2X37-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-0ATA_ST4000VN008-2DR1_ZDHB2X37-part4 -> ../../sdb4 lrwxrwxrwx 1 root root 9 Sep 7 01:46 scsi-0ATA_ST4000VN008-2DR1_ZDHBKZTG -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-0ATA_ST4000VN008-2DR1_ZDHBKZTG-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-0ATA_ST4000VN008-2DR1_ZDHBKZTG-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-0ATA_ST4000VN008-2DR1_ZDHBKZTG-part4 -> ../../sdc4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 scsi-1ATA_SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-1ATA_SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-1ATA_SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-1ATA_SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-1ATA_SAMSUNG_MZ7LN128HCHP-000L1_S1ZMNXAG628224-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 scsi-1ATA_ST4000VN008-2DR166_ZDHB2X37 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-1ATA_ST4000VN008-2DR166_ZDHB2X37-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-1ATA_ST4000VN008-2DR166_ZDHB2X37-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-1ATA_ST4000VN008-2DR166_ZDHB2X37-part4 -> ../../sdb4 lrwxrwxrwx 1 root root 9 Sep 7 01:46 scsi-1ATA_ST4000VN008-2DR166_ZDHBKZTG -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-1ATA_ST4000VN008-2DR166_ZDHBKZTG-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-1ATA_ST4000VN008-2DR166_ZDHBKZTG-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-1ATA_ST4000VN008-2DR166_ZDHBKZTG-part4 -> ../../sdc4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 scsi-35000c500e3ea9889 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-35000c500e3ea9889-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-35000c500e3ea9889-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-35000c500e3ea9889-part4 -> ../../sdb4 lrwxrwxrwx 1 root root 9 Sep 7 01:46 scsi-35000c500e4d51a09 -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-35000c500e4d51a09-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-35000c500e4d51a09-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-35000c500e4d51a09-part4 -> ../../sdc4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 scsi-35002538d00000000 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-35002538d00000000-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-35002538d00000000-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-35002538d00000000-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-35002538d00000000-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 scsi-SATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-SATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-SATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-SATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-SATA_SAMSUNG_MZ7LN128_S1ZMNXAG628224-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 scsi-SATA_ST4000VN008-2DR1_ZDHB2X37 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-SATA_ST4000VN008-2DR1_ZDHB2X37-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-SATA_ST4000VN008-2DR1_ZDHB2X37-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 scsi-SATA_ST4000VN008-2DR1_ZDHB2X37-part4 -> ../../sdb4 lrwxrwxrwx 1 root root 9 Sep 7 01:46 scsi-SATA_ST4000VN008-2DR1_ZDHBKZTG -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-SATA_ST4000VN008-2DR1_ZDHBKZTG-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-SATA_ST4000VN008-2DR1_ZDHBKZTG-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 7 01:46 scsi-SATA_ST4000VN008-2DR1_ZDHBKZTG-part4 -> ../../sdc4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 wwn-0x5000c500e3ea9889 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 21 16:17 wwn-0x5000c500e3ea9889-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 wwn-0x5000c500e3ea9889-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 wwn-0x5000c500e3ea9889-part4 -> ../../sdb4 lrwxrwxrwx 1 root root 9 Sep 7 01:46 wwn-0x5000c500e4d51a09 -> ../../sdc lrwxrwxrwx 1 root root 10 Sep 7 01:46 wwn-0x5000c500e4d51a09-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 Sep 7 01:46 wwn-0x5000c500e4d51a09-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 10 Sep 7 01:46 wwn-0x5000c500e4d51a09-part4 -> ../../sdc4 lrwxrwxrwx 1 root root 9 Aug 21 16:17 wwn-0x5002538d00000000 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 21 16:17 wwn-0x5002538d00000000-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Aug 21 16:17 wwn-0x5002538d00000000-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Aug 21 16:17 wwn-0x5002538d00000000-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Aug 21 16:17 wwn-0x5002538d00000000-part4 -> ../../sda4 ================================ Mount points: ================================= Device Mount_Point Type Options /dev/md40p1 /mnt/4TRaid10md xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,sunit=1024,swidth=2048,noquota) /dev/md40p4 /mnt/slices/4TRaid10md-ext2 ext2 (rw,relatime,stripe=1024) /dev/sda2 / xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sda4 /mnt/ssd xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdb4 /mnt/slices/Seag4000-ZDHB2X37-ext2 ext2 (rw,relatime,stripe=4) /dev/sdc4 /mnt/slices/Seag4000-ZDHBKZTG-fat vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) ========================== sda2/boot/grub2/grub.cfg: =========================== -------------------------------------------------------------------------------- # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -f ${config_directory}/grubenv ]; then load_env -f ${config_directory}/grubenv elif [ -s $prefix/grubenv ]; then load_env fi if [ "${env_block}" ] ; then set env_block="(${root})${env_block}" export env_block load_env -f "${env_block}" fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry if [ "${env_block}" ] ; then save_env -f "${env_block}" next_entry fi set boot_once=true else set default="${saved_entry}" 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}" if [ "${env_block}" ] ; then save_env -f "${env_block}" saved_entry else save_env saved_entry fi 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_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi font="/usr/share/grub2/unicode.pf2" fi if loadfont $font ; then if [ "${grub_platform}" = "efi" ]; then echo "Please press 't' to show the boot menu on this console" fi set gfxmode=auto load_video insmod gfxterm fi terminal_input console terminal_output gfxterm insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi insmod gfxmenu loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans-Bold14.pf2 loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans10.pf2 loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans12.pf2 loadfont ($root)/boot/grub2/themes/openSUSE/ascii.pf2 insmod png set theme=($root)/boot/grub2/themes/openSUSE/theme.txt export theme if [ x${boot_once} = xtrue ]; then set timeout=0 elif [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=2 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=2 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/00_tuned ### set tuned_params="" set tuned_initrd="" ### END /etc/grub.d/00_tuned ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'openSUSE Leap 15.2' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.106-default ...' linux /boot/vmlinuz-5.3.18-lp152.106-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e splash=silent quiet mitigations=auto echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.106-default } submenu 'Advanced options for openSUSE Leap 15.2' --hotkey=1 $menuentry_id_option 'gnulinux-advanced-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.106-default' --hotkey=2 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.106-default-advanced-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.106-default ...' linux /boot/vmlinuz-5.3.18-lp152.106-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e splash=silent quiet mitigations=auto echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.106-default } menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.106-default (recovery mode)' --hotkey=3 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.106-default-recovery-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.106-default ...' linux /boot/vmlinuz-5.3.18-lp152.106-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.106-default } menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.78-default' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.78-default-advanced-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.78-default ...' linux /boot/vmlinuz-5.3.18-lp152.78-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e splash=silent quiet mitigations=auto echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.78-default } menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.78-default (recovery mode)' --hotkey=1 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.78-default-recovery-22fad8b5-8b95-4e26-bd39-d22d1f10a22e' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 22fad8b5-8b95-4e26-bd39-d22d1f10a22e else search --no-floppy --fs-uuid --set=root 22fad8b5-8b95-4e26-bd39-d22d1f10a22e fi echo 'Loading Linux 5.3.18-lp152.78-default ...' linux /boot/vmlinuz-5.3.18-lp152.78-default root=UUID=22fad8b5-8b95-4e26-bd39-d22d1f10a22e echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.78-default } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_memtest86+ ### ### END /etc/grub.d/20_memtest86+ ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### ### BEGIN /etc/grub.d/80_suse_btrfs_snapshot ### ### END /etc/grub.d/80_suse_btrfs_snapshot ### ### BEGIN /etc/grub.d/90_persistent ### ### END /etc/grub.d/90_persistent ### ### BEGIN /etc/grub.d/95_textmode ### if [ "${grub_platform}" = "efi" ]; then # On EFI systems we can only have graphics *or* serial, so allow the user # to switch between the two hiddenentry 'Text mode' --hotkey 't' { set textmode=true terminal_output console } fi ### END /etc/grub.d/95_textmode ### -------------------------------------------------------------------------------- =============================== sda2/etc/fstab: ================================ -------------------------------------------------------------------------------- # # local stuff - internal # LABEL=jposuse / xfs defaults 0 1 LABEL=jpo-ssd /mnt/ssd xfs defaults 0 2 UUID=aafd8c10-b00c-48bc-9566-57ea73f3a126 swap swap defaults 0 0 LABEL=4TRaid10md /mnt/4TRaid10md xfs defaults 0 2 LABEL=4TRaid10md-ext2 /mnt/slices/4TRaid10md-ext2 ext2 defaults 0 2 LABEL=1TRaid10md /mnt/1TRaid10md xfs defaults,noauto 0 2 LABEL=S4-...2X37-ext2 /mnt/slices/Seag4000-ZDHB2X37-ext2 ext2 defaults,nofail 0 2 LABEL=S4-KZTG-fat /mnt/slices/Seag4000-ZDHBKZTG-fat vfat defaults,nofail 0 2 # # local stuff - transient # #LABEL=Raid1vol /mnt/raid1jpo ext3 defaults 0 2 #LABEL=Raid5vol /mnt/raid5jpo xfs defaults 0 2 -------------------------------------------------------------------------------- =================== sda2: Location of files loaded by Grub: ==================== GiB - GB File Fragment(s) 49.849739075 = 53.525749760 boot/grub2/grub.cfg 1 50.381263733 = 54.096470016 boot/grub2/i386-pc/core.img 1 50.645175934 = 54.379843584 boot/vmlinuz 1 50.645175934 = 54.379843584 boot/vmlinuz-5.3.18-lp152.106-default 1 50.792079926 = 54.537580544 boot/vmlinuz-5.3.18-lp152.78-default 1 51.038528442 = 54.802202624 boot/initrd 1 51.038528442 = 54.802202624 boot/initrd-5.3.18-lp152.106-default 1 51.063762665 = 54.829297664 boot/initrd-5.3.18-lp152.78-default 1 =============================== StdErr Messages: =============================== mdadm: No arrays found in config file or automatically :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

On 18/10/2022 03.17, Felix Miata wrote:

David T-G composed on 2022-10-17 21:59 (UTC):

...

The problem is creating the long output; at that box I'm at a plain text console with no GUI support and no other computer nearby. I miss serial consoles and remote access!

The rescue USB is wrriteable and runs in graphic XFCE mode. http://download.opensuse.org/distribution/leap/15.4/live/openSUSE-Leap-15.4-...

# sudo zypper in susepaste unzip # wget https://github.com/arvidjaar/bootinfoscript/archive/refs/heads/master.zip # unzip master.zip # sudo sh ./bootinfoscript-master/bootinfoscript | susepaste -n DavidTG -e 40320

Hopefully the URI resulting from the above command list, from the actual problem machine, will be the best info you give us about this, nailing down what's wrong. Andrei stopped bootinfoscript maintenance when the overwhelming majority of boot problems in the wild had long since moved from MBR booting to UEFI booting. The script does not properly support UEFI booting systems. :(

It can not detect some m2 disks. I just forget their device name this instant, this laptop doesn't use that, can't check.

I was under the impression that non-UEFI booting with GPT partitioned disks could only be done from Grub2 installed to a BIOS boot partition. From what I can see in the program output provided, you must be booting from Grub installed to a native Linux partition on a GPT disk. I've never seen that before, and didn't know it was possible. On MBR disks, it's what I've always done, never Grub purposely on any MBR here.

It can be done if the MBR is what it should be, there is a partition marked bootable, and grub is installed in that partition. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.3 (Legolas))

On 18/10/2022 13.32, David T-G wrote:

Carlos, et al --

...and then Carlos E. R. said... % On 18/10/2022 03.17, Felix Miata wrote: % > David T-G composed on 2022-10-17 21:59 (UTC): % > % > > The problem is creating the long output; at that box I'm at a plain text % > > console with no GUI support and no other computer nearby. I miss serial % > > consoles and remote access! % % The rescue USB is wrriteable and runs in graphic XFCE mode. % % http://download.opensuse.org/distribution/leap/15.4/live/openSUSE-Leap-15.4-... [snip]

Clearly there's something I'm missing -- and I think it's first that I'm on different media. I have a Leap 15.2 installer image thumb drive I'm using for boot, except that from the menu instead of choosing installation I choose "Rescue system" and land at a happy

rescue:/

prompt after logging in as root with no password.

No. Download and install to an USB stick the image I linked above. You may be able to download the one for 15.2 from some mirrors if you prefer that one. Then boot it on the faulty computer. You get a full graphical desktop (XFCE), where you can write files, even install things, and of course, have internet and open firefox -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.3 (Legolas))

Carlos, et al -- ...and then Carlos E. R. said... % On 17/10/2022 23.59, David T-G wrote: ... % > I can give you that sort of thing from my web server box, which is the % > exact same model with the exact same /dev/sda but without all of the % > other storage. So let's dig in, and maybe you can figure out how grub % > is actually doing anything here. % % No, you have to get the actual output from the bad computer. While I'm happy to try that, it will likely only tell me that grub is broken, and I meanwhile would have to figure out how to run in the /dev/sda context rather than the rescue USB context. Since the mystery seems to be how GRUB can possibly be working on a GPT disk with no /boot partition, I figured analysis of a happy system might be useful :-) % % Just download the script using the rescue ISO on USB stick and run it. It is % writeable. As an added bonus, I can get to jpo remotely, but with diskfarm down I have to be there. I'll be home again in a couple of days -- to, I hope, try out magic incantations we learn here. % % -- % Cheers / Saludos, % % Carlos E. R. % % (from openSUSE 15.3 (Legolas)) % Thanks again & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

Hi, all! ...and then Carlos E. R. said... % On 18/10/2022 13.25, David T-G wrote: % > % > While I'm happy to try that, it will likely only tell me that grub is % > broken, and I meanwhile would have to figure out how to run in the % > /dev/sda context rather than the rescue USB context. % % That doesn't matter, bootinfoscript will do the right thing, if you use the % USB image I told you elsewhere. [snip] I'm finally back, and so I've popped bootinfoscript onto my rescue thumb drive and run it. Pasted below my signature is the RESULTS1.txt file. I do see that grub2 is in the MBR and it's looking for core.img which is there. Yay, but ... I still don't know why it doesn't boot *sigh* I also don't know how jpo, my other system from RESULTS.txt last week, also boots, but at least it does. Meanwhile, I even tried a clean install to the mirrors on sde and it STILL doesn't boot. Weird ... Thanks again! :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt Boot Info Script 0.78 [09 October 2019] ============================= Boot Info Summary: =============================== => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 69344384 of the same hard drive for core.img. core.img is at this location. => 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 (v1.99-2.00) is installed in the MBR of /dev/sde and looks at sector 70108480 of the same hard drive for core.img, but core.img can not be found at this location. => Windows 7/8/2012 is installed in the MBR of /dev/sdf. => No boot loader is installed in the MBR of /dev/sdg. => No boot loader is installed in the MBR of /dev/sdh. => No boot loader is installed in the MBR of /dev/sdi. => No boot loader is installed in the MBR of /dev/sdj. => Windows 7/8/2012 is installed in the MBR of /dev/sdk. => No boot loader is installed in the MBR of /dev/sdl. => No boot loader is installed in the MBR of /dev/sdm. => ISOhybrid (Syslinux 4.05 and higher) is installed in the MBR of /dev/sdn. sda1: __________________________________________________________________________ File system: swap Boot sector type: - Boot sector info: sda2: __________________________________________________________________________ File system: xfs Boot sector type: - Boot sector info: Operating System: openSUSE Leap 15.2 Boot files: /boot/grub2/grub.cfg /etc/fstab /boot/grub2/i386-pc/core.img sda3: __________________________________________________________________________ File system: Boot sector type: - Boot sector info: sda4: __________________________________________________________________________ File system: xfs Boot sector type: - Boot sector info: Operating System: Boot files: sdb51: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb52: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb53: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb54: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb55: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb56: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdb128: ________________________________________________________________________ File system: ext3 Boot sector type: - Boot sector info: Operating System: Boot files: sdc51: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc52: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc53: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc54: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc55: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc56: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdc128: ________________________________________________________________________ File system: reiserfs Boot sector type: - Boot sector info: Operating System: Boot files: sdd51: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdd52: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdd53: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdd54: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdd55: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdd56: _________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdd128: ________________________________________________________________________ File system: xfs Boot sector type: - Boot sector info: Operating System: Boot files: sde1: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sde2: __________________________________________________________________________ File system: linux_raid_member Boot sector type: Unknown Boot sector info: sde3: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sde4: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sde5: __________________________________________________________________________ File system: ext2 Boot sector type: - Boot sector info: Operating System: Boot files: sdf1: __________________________________________________________________________ File system: ntfs Boot sector type: Windows 7/2008: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: sdg1: __________________________________________________________________________ File system: ext3 Boot sector type: - Boot sector info: Operating System: Boot files: sdg4: __________________________________________________________________________ File system: vfat Boot sector type: FAT16 Boot sector info: According to the info in the boot sector, sdg4 has 0 sectors. Operating System: Boot files: sdh1: __________________________________________________________________________ File system: ext3 Boot sector type: - Boot sector info: Operating System: Boot files: sdh4: __________________________________________________________________________ File system: vfat Boot sector type: FAT16 Boot sector info: According to the info in the boot sector, sdh4 has 0 sectors. Operating System: Boot files: sdj2: __________________________________________________________________________ File system: linux_raid_member Boot sector type: Windows 7/2008: NTFS Boot sector info: sdj3: __________________________________________________________________________ File system: xfs Boot sector type: - Boot sector info: Operating System: Boot files: sdk1: __________________________________________________________________________ File system: ntfs Boot sector type: Windows 7/2008: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /bootmgr /Boot/BCD sdk2: __________________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: sdk3: __________________________________________________________________________ File system: reiserfs Boot sector type: - Boot sector info: Operating System: Boot files: sdk4: __________________________________________________________________________ File system: reiserfs Boot sector type: - Boot sector info: Operating System: Boot files: sdl2: __________________________________________________________________________ File system: linux_raid_member Boot sector type: Windows 8/2012: NTFS Boot sector info: sdl3: __________________________________________________________________________ File system: ext3 Boot sector type: - Boot sector info: Operating System: Boot files: sdm1: __________________________________________________________________________ File system: ntfs Boot sector type: Windows Vista: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: sdn1: __________________________________________________________________________ File system: vfat Boot sector type: FAT16 Boot sector info: According to the info in the boot sector, sdn1 starts at sector 0. But according to the info from fdisk, sdn1 starts at sector 2804. According to the info in the boot sector, sdn1 has 0 sectors. Operating System: Boot files: /efi/BOOT/MokManager.efi /efi/BOOT/bootx64.efi /efi/BOOT/grub.efi /efi/BOOT/grub.cfg sdn2: __________________________________________________________________________ File system: iso9660 Boot sector type: - Boot sector info: Operating System: Boot files: sdn3: __________________________________________________________________________ File system: ext2 Boot sector type: - Boot sector info: Operating System: Boot files: md/diskfarm:750G: ______________________________________________________________ File system: Boot sector type: - Boot sector info: md/diskfarm:55: ________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: md/diskfarm:52: ________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: md/diskfarm:51: ________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: md/diskfarm:56: ________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: md/diskfarm:54: ________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: md/diskfarm:53: ________________________________________________________________ File system: linux_raid_member Boot sector type: - Boot sector info: md/diskfarm:ssd: _______________________________________________________________ File system: xfs Boot sector type: - Boot sector info: Mounting failed: mount: /tmp/BootInfo-TtY6mbpC/MDRaid/md/diskfarm:ssd: /dev/md120 already mounted on /mnt/ssd. md/diskfarm:swap: ______________________________________________________________ File system: swap Boot sector type: - Boot sector info: md/diskfarm:root: ______________________________________________________________ File system: xfs Boot sector type: - Boot sector info: Mounting failed: mount: /tmp/BootInfo-TtY6mbpC/MDRaid/md/diskfarm:root: /dev/md118 already mounted on /. md/diskfarm:next: ______________________________________________________________ File system: Boot sector type: - Boot sector info: md/diskfarm:10T: _______________________________________________________________ File system: Boot sector type: - Boot sector info: ============================ Drive/Partition Info: ============================= Drive: sda _____________________________________________________________________ Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors Disk model: SanDisk SD6SB1M1 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/sda1 * 1 250,069,679 250,069,679 ee GPT GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sda1 2,048 69,208,063 69,206,016 Swap partition (Linux) /dev/sda2 69,208,064 136,316,927 67,108,864 Data partition (Linux) /dev/sda3 B 136,316,928 203,425,791 67,108,864 Data partition (Linux) /dev/sda4 203,425,792 250,069,646 46,643,855 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdb _____________________________________________________________________ Disk /dev/sdb: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: TOSHIBA HDWR11A 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/sdb51 2,048 3,254,781,951 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdb52 3,254,781,952 6,509,561,855 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdb53 6,509,561,856 9,764,341,759 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdb54 9,764,341,76013,019,121,663 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdb55 13,019,121,66416,273,901,567 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdb56 16,273,901,56819,528,681,471 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdb128 19,528,681,47219,532,873,694 4,192,223 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdc _____________________________________________________________________ Disk /dev/sdc: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: TOSHIBA HDWR11A 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/sdc51 2,048 3,254,781,951 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdc52 3,254,781,952 6,509,561,855 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdc53 6,509,561,856 9,764,341,759 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdc54 9,764,341,76013,019,121,663 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdc55 13,019,121,66416,273,901,567 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdc56 16,273,901,56819,528,681,471 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdc128 19,528,681,47219,532,873,694 4,192,223 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdd _____________________________________________________________________ Disk /dev/sdd: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: TOSHIBA HDWR11A 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/sdd51 2,048 3,254,781,951 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdd52 3,254,781,952 6,509,561,855 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdd53 6,509,561,856 9,764,341,759 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdd54 9,764,341,76013,019,121,663 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdd55 13,019,121,66416,273,901,567 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdd56 16,273,901,56819,528,681,471 3,254,779,904 Logical Volume Manager (LVM) partition (Linux) /dev/sdd128 19,528,681,47219,532,873,694 4,192,223 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sde _____________________________________________________________________ Disk /dev/sde: 238.5 GiB, 256060514304 bytes, 500118192 sectors Disk model: SATA SSD 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 * 1 500,118,191 500,118,191 ee GPT GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sde1 4,096 71,303,167 71,299,072 Swap partition (Linux) /dev/sde2 71,303,168 142,606,335 71,303,168 EFI System partition /dev/sde3 142,606,336 213,909,503 71,303,168 EFI System partition /dev/sde4 213,909,504 500,117,503 286,208,000 RAID partition (Linux) /dev/sde5 34 4,095 4,062 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdf _____________________________________________________________________ Disk /dev/sdf: 698.7 GiB, 750156374016 bytes, 1465149168 sectors Disk model: WDC WD7500BPKX-7 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/sdf1 * 2,048 1,465,145,343 1,465,143,296 7 NTFS / exFAT / HPFS Drive: sdg _____________________________________________________________________ Disk /dev/sdg: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000LM035-1RK1 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/sdg1 1 1,953,525,167 1,953,525,167 ee GPT GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sdg1 2,048 1,953,488,895 1,953,486,848 Data partition (Linux) /dev/sdg4 1,953,503,232 1,953,523,711 20,480 Data partition (Windows/Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdh _____________________________________________________________________ Disk /dev/sdh: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: TOSHIBA MQ01ABD1 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/sdh1 1 1,953,525,167 1,953,525,167 ee GPT GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sdh1 2,048 1,953,488,895 1,953,486,848 Data partition (Linux) /dev/sdh4 1,953,488,896 1,953,523,711 34,816 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdi _____________________________________________________________________ Disk /dev/sdi: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors Disk model: TOSHIBA HDWR11A 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 Invalid MBR Signature found. Drive: sdj _____________________________________________________________________ Disk /dev/sdj: 698.7 GiB, 750156374016 bytes, 1465149168 sectors Disk model: WDC WD7500BPKX-7 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/sdj1 1 1,465,149,167 1,465,149,167 ee GPT GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sdj2 2,048 1,464,886,990 1,464,884,943 RAID partition (Linux) /dev/sdj3 1,464,887,296 1,465,149,134 261,839 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdk _____________________________________________________________________ Disk /dev/sdk: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Hitachi HDE72101 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/sdk1 2,048 8,255,487 8,253,440 27 Hidden NTFS (Recovery Environment) /dev/sdk2 8,255,488 1,473,140,431 1,464,884,944 fd Linux raid autodetect /dev/sdk3 1,473,140,432 1,473,402,575 262,144 83 Linux /dev/sdk4 1,473,402,576 1,953,525,167 480,122,592 83 Linux Drive: sdl _____________________________________________________________________ Disk /dev/sdl: 698.7 GiB, 750156374016 bytes, 1465149168 sectors Disk model: WDC WD7500BPKX-7 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/sdl1 1 1,465,149,167 1,465,149,167 ee GPT GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sdl2 2,048 1,464,886,990 1,464,884,943 RAID partition (Linux) /dev/sdl3 1,464,887,296 1,465,149,134 261,839 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdm _____________________________________________________________________ Disk /dev/sdm: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: ST3500413AS 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/sdm1 1 976,773,167 976,773,167 ee GPT GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sdm1 2,048 976,773,119 976,771,072 Data partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Drive: sdn _____________________________________________________________________ Disk /dev/sdn: 14.6 GiB, 15623782400 bytes, 30515200 sectors Disk model: USB Flash Disk 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/sdn1 2,804 11,119 8,316 ef EFI (FAT-12/16/32) /dev/sdn2 * 11,120 8,374,271 8,363,152 17 Hidden NTFS / HPFS /dev/sdn3 8,374,272 30,515,199 22,140,928 83 Linux "blkid" output: ________________________________________________________________ Device UUID TYPE LABEL /dev/loop0 squashfs /dev/loop1 squashfs /dev/loop2 squashfs /dev/loop3 squashfs /dev/loop4 squashfs /dev/loop5 squashfs /dev/md116 /dev/md116p1 d8cb1c48-964a-47a2-b194-87c801470d48 xfs 10Traid50md /dev/md118 e9e5d293-11a5-4c9e-8cb8-77b2e5352006 xfs df-root /dev/md119 3cb1cf4b-69f4-4e8b-89a2-22d1f8605f6c swap df-swap /dev/md120 d2171dc9-1bd2-4a4c-923c-876186b5d26a xfs df-ssd /dev/md121 cccbe073-d92c-6ecd-77ba-5c465db6b3f0 linux_raid_member diskfarm:10T /dev/md122 cccbe073-d92c-6ecd-77ba-5c465db6b3f0 linux_raid_member diskfarm:10T /dev/md123 cccbe073-d92c-6ecd-77ba-5c465db6b3f0 linux_raid_member diskfarm:10T /dev/md124 cccbe073-d92c-6ecd-77ba-5c465db6b3f0 linux_raid_member diskfarm:10T /dev/md125 cccbe073-d92c-6ecd-77ba-5c465db6b3f0 linux_raid_member diskfarm:10T /dev/md126 cccbe073-d92c-6ecd-77ba-5c465db6b3f0 linux_raid_member diskfarm:10T /dev/md127 /dev/md127p1 0b37f6c6-d1a2-4765-bcdd-24fb08ebbee2 reiserfs 750Graid5md /dev/sda1 3982f3a2-3e59-4658-b18d-5a036572c6c7 swap diskfarm-swap /dev/sda2 4fe67d3c-13b6-48d6-b134-b371898901ea xfs diskfarmsuse /dev/sda3 /dev/sda4 eb98e839-54d8-40ce-8c64-55b7d09a4ce8 xfs diskfarm-ssd /dev/sdb128 f466903f-3a29-4254-98ed-94f0b4578c9f ext3 10Traid50md-ext3 /dev/sdb51 9330e44f-35ba-f039-7e97-1a8eda983e31 linux_raid_member diskfarm:51 /dev/sdb52 d9eada18-2947-8a43-3765-4ef5d34df19c linux_raid_member diskfarm:52 /dev/sdb53 b2cb87a1-bdf1-adc5-e915-ada91ce428ec linux_raid_member diskfarm:53 /dev/sdb54 c5b644d5-af86-8c57-319b-51110b793de8 linux_raid_member diskfarm:54 /dev/sdb55 02b8734d-76ec-39c7-1a11-4c038d252aed linux_raid_member diskfarm:55 /dev/sdb56 7cb91524-2c2e-0a98-8a6e-af8d5c4b4279 linux_raid_member diskfarm:56 /dev/sdc128 fbfff397-a08d-4783-8219-f892df562fd8 reiserfs 10Traid50md-reis /dev/sdc51 9330e44f-35ba-f039-7e97-1a8eda983e31 linux_raid_member diskfarm:51 /dev/sdc52 d9eada18-2947-8a43-3765-4ef5d34df19c linux_raid_member diskfarm:52 /dev/sdc53 b2cb87a1-bdf1-adc5-e915-ada91ce428ec linux_raid_member diskfarm:53 /dev/sdc54 c5b644d5-af86-8c57-319b-51110b793de8 linux_raid_member diskfarm:54 /dev/sdc55 02b8734d-76ec-39c7-1a11-4c038d252aed linux_raid_member diskfarm:55 /dev/sdc56 7cb91524-2c2e-0a98-8a6e-af8d5c4b4279 linux_raid_member diskfarm:56 /dev/sdd128 7d5eabcb-c2b9-4846-b503-6fed63b85cb7 xfs 10Tr50md-xfs /dev/sdd51 9330e44f-35ba-f039-7e97-1a8eda983e31 linux_raid_member diskfarm:51 /dev/sdd52 d9eada18-2947-8a43-3765-4ef5d34df19c linux_raid_member diskfarm:52 /dev/sdd53 b2cb87a1-bdf1-adc5-e915-ada91ce428ec linux_raid_member diskfarm:53 /dev/sdd54 c5b644d5-af86-8c57-319b-51110b793de8 linux_raid_member diskfarm:54 /dev/sdd55 02b8734d-76ec-39c7-1a11-4c038d252aed linux_raid_member diskfarm:55 /dev/sdd56 7cb91524-2c2e-0a98-8a6e-af8d5c4b4279 linux_raid_member diskfarm:56 /dev/sde1 859f15de-cd6e-8a00-6230-b10449c3e2e4 linux_raid_member diskfarm:swap /dev/sde2 30f2f811-8821-6a55-a32a-dd5eb82cfb25 linux_raid_member diskfarm:root /dev/sde3 d6932c51-9189-0443-4c63-1db19582056b linux_raid_member diskfarm:next /dev/sde4 263347c2-4931-1da3-dea1-963972843db5 linux_raid_member diskfarm:ssd /dev/sde5 3da81ea4-4ceb-40e7-b2b9-cee2dcb86562 ext2 grub-boot /dev/sdf1 E2FE9598FE956597 ntfs arch-WX71A73E5533 /dev/sdg1 9d449ec5-c686-41fa-bae0-a1e016a7b7f8 ext3 GIFTarch-LM035 /dev/sdg4 40A5-88F4 vfat /dev/sdh1 d1a172be-b6a5-4128-abf9-a95a84888b0d ext3 GIFTarch-MQ01ABD /dev/sdh4 40A5-E664 vfat /dev/sdj2 88575f01-5921-67fd-bd9f-9ba1a61fafc4 linux_raid_member diskfarm:750G /dev/sdj3 02e8766a-4c2c-486d-9012-e3d641c01f1f xfs 50...8cb1db /dev/sdk1 EEA84FE1A84FA6C5 ntfs System /dev/sdk2 88575f01-5921-67fd-bd9f-9ba1a61fafc4 linux_raid_member diskfarm:750G /dev/sdk3 ad847b47-82d4-499c-b600-2fbc98e57436 reiserfs wwn-0x5000cca35e /dev/sdk4 f7fadc1d-e108-4d41-810e-96f7abf34e64 reiserfs scratch_reiserfs /dev/sdl2 88575f01-5921-67fd-bd9f-9ba1a61fafc4 linux_raid_member diskfarm:750G /dev/sdl3 dd314f63-11e9-4d55-abf4-cebd057484db ext3 wwn-0x50014ee605 /dev/sdm1 78B2166F286547A8 ntfs mp3backup /dev/sdn1 C010-9270 vfat /dev/sdn2 2020-06-26-06-47-04-69 iso9660 openSUSE-Leap-15.2-DVD-x86_64695 /dev/sdn3 ff101a5e-0af0-4abb-9cf5-0c0a9ec61ed5 ext2 Leap52rescue ========================= "ls -l /dev/disk/by-id" output: ====================== total 0 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-Hitachi_HDE721010SLA330_MS2R0UAS -> ../../sdk lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-Hitachi_HDE721010SLA330_MS2R0UAS-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-Hitachi_HDE721010SLA330_MS2R0UAS-part2 -> ../../sdk2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-Hitachi_HDE721010SLA330_MS2R0UAS-part3 -> ../../sdk3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-Hitachi_HDE721010SLA330_MS2R0UAS-part4 -> ../../sdk4 lrwxrwxrwx 1 root root 9 Oct 18 03:15 ata-SATA_SSD_21112525604525 -> ../../sde lrwxrwxrwx 1 root root 10 Oct 18 03:15 ata-SATA_SSD_21112525604525-part1 -> ../../sde1 lrwxrwxrwx 1 root root 10 Oct 18 03:15 ata-SATA_SSD_21112525604525-part2 -> ../../sde2 lrwxrwxrwx 1 root root 10 Oct 18 03:15 ata-SATA_SSD_21112525604525-part3 -> ../../sde3 lrwxrwxrwx 1 root root 10 Oct 18 03:15 ata-SATA_SSD_21112525604525-part4 -> ../../sde4 lrwxrwxrwx 1 root root 10 Oct 18 03:15 ata-SATA_SSD_21112525604525-part5 -> ../../sde5 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-ST1000LM035-1RK172_WL14W5N9 -> ../../sdg lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-ST1000LM035-1RK172_WL14W5N9-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-ST1000LM035-1RK172_WL14W5N9-part4 -> ../../sdg4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-ST3500413AS_5VMY21DL -> ../../sdm lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-ST3500413AS_5VMY21DL-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-SanDisk_SD6SB1M128G1001_142000400317 -> ../../sda lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-SanDisk_SD6SB1M128G1001_142000400317-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-SanDisk_SD6SB1M128G1001_142000400317-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-SanDisk_SD6SB1M128G1001_142000400317-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-SanDisk_SD6SB1M128G1001_142000400317-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A007FBKG -> ../../sdd lrwxrwxrwx 1 root root 12 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A007FBKG-part128 -> ../../sdd128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A007FBKG-part51 -> ../../sdd51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A007FBKG-part52 -> ../../sdd52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A007FBKG-part53 -> ../../sdd53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A007FBKG-part54 -> ../../sdd54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A007FBKG-part55 -> ../../sdd55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A007FBKG-part56 -> ../../sdd56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0BEFBKG -> ../../sdc lrwxrwxrwx 1 root root 12 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0BEFBKG-part128 -> ../../sdc128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0BEFBKG-part51 -> ../../sdc51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0BEFBKG-part52 -> ../../sdc52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0BEFBKG-part53 -> ../../sdc53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0BEFBKG-part54 -> ../../sdc54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0BEFBKG-part55 -> ../../sdc55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0BEFBKG-part56 -> ../../sdc56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0HQFBKG -> ../../sdb lrwxrwxrwx 1 root root 12 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0HQFBKG-part128 -> ../../sdb128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0HQFBKG-part51 -> ../../sdb51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0HQFBKG-part52 -> ../../sdb52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0HQFBKG-part53 -> ../../sdb53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0HQFBKG-part54 -> ../../sdb54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0HQFBKG-part55 -> ../../sdb55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 ata-TOSHIBA_HDWR11A_61U0A0HQFBKG-part56 -> ../../sdb56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-TOSHIBA_HDWR11A_91C0A03ZFBKG -> ../../sdi lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-TOSHIBA_MQ01ABD100_37MCWNJRT -> ../../sdh lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-TOSHIBA_MQ01ABD100_37MCWNJRT-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-TOSHIBA_MQ01ABD100_37MCWNJRT-part4 -> ../../sdh4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-WDC_WD7500BPKX-75HPJT0_WD-WX51A150PNP7 -> ../../sdl lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-WDC_WD7500BPKX-75HPJT0_WD-WX51A150PNP7-part2 -> ../../sdl2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-WDC_WD7500BPKX-75HPJT0_WD-WX51A150PNP7-part3 -> ../../sdl3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-WDC_WD7500BPKX-75HPJT0_WD-WX71A73E5533 -> ../../sdf lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-WDC_WD7500BPKX-75HPJT0_WD-WX71A73E5533-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 ata-WDC_WD7500BPKX-75HPJT0_WD-WXF1EA4CSA07 -> ../../sdj lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-WDC_WD7500BPKX-75HPJT0_WD-WXF1EA4CSA07-part2 -> ../../sdj2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 ata-WDC_WD7500BPKX-75HPJT0_WD-WXF1EA4CSA07-part3 -> ../../sdj3 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:10T -> ../../md116 lrwxrwxrwx 1 root root 13 Oct 18 03:10 md-name-diskfarm:10T-part1 -> ../../md116p1 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:51 -> ../../md124 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:52 -> ../../md125 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:53 -> ../../md121 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:54 -> ../../md122 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:55 -> ../../md126 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:56 -> ../../md123 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:750G -> ../../md127 lrwxrwxrwx 1 root root 13 Oct 18 03:10 md-name-diskfarm:750G-part1 -> ../../md127p1 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:next -> ../../md117 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:root -> ../../md118 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:ssd -> ../../md120 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-name-diskfarm:swap -> ../../md119 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-02b8734d:76ec39c7:1a114c03:8d252aed -> ../../md126 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-263347c2:49311da3:dea19639:72843db5 -> ../../md120 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-30f2f811:88216a55:a32add5e:b82cfb25 -> ../../md118 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-7cb91524:2c2e0a98:8a6eaf8d:5c4b4279 -> ../../md123 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-859f15de:cd6e8a00:6230b104:49c3e2e4 -> ../../md119 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-88575f01:592167fd:bd9f9ba1:a61fafc4 -> ../../md127 lrwxrwxrwx 1 root root 13 Oct 18 03:10 md-uuid-88575f01:592167fd:bd9f9ba1:a61fafc4-part1 -> ../../md127p1 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-9330e44f:35baf039:7e971a8e:da983e31 -> ../../md124 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-b2cb87a1:bdf1adc5:e915ada9:1ce428ec -> ../../md121 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-c5b644d5:af868c57:319b5111:0b793de8 -> ../../md122 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-cccbe073:d92c6ecd:77ba5c46:5db6b3f0 -> ../../md116 lrwxrwxrwx 1 root root 13 Oct 18 03:10 md-uuid-cccbe073:d92c6ecd:77ba5c46:5db6b3f0-part1 -> ../../md116p1 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-d6932c51:91890443:4c631db1:9582056b -> ../../md117 lrwxrwxrwx 1 root root 11 Oct 24 10:14 md-uuid-d9eada18:29478a43:37654ef5:d34df19c -> ../../md125 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_Hitachi_HDE72101_MS2R0UAS -> ../../sdk lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_Hitachi_HDE72101_MS2R0UAS-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_Hitachi_HDE72101_MS2R0UAS-part2 -> ../../sdk2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_Hitachi_HDE72101_MS2R0UAS-part3 -> ../../sdk3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_Hitachi_HDE72101_MS2R0UAS-part4 -> ../../sdk4 lrwxrwxrwx 1 root root 9 Oct 18 03:15 scsi-0ATA_SATA_SSD_21112525604525 -> ../../sde lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-0ATA_SATA_SSD_21112525604525-part1 -> ../../sde1 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-0ATA_SATA_SSD_21112525604525-part2 -> ../../sde2 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-0ATA_SATA_SSD_21112525604525-part3 -> ../../sde3 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-0ATA_SATA_SSD_21112525604525-part4 -> ../../sde4 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-0ATA_SATA_SSD_21112525604525-part5 -> ../../sde5 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_ST1000LM035-1RK1_WL14W5N9 -> ../../sdg lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_ST1000LM035-1RK1_WL14W5N9-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_ST1000LM035-1RK1_WL14W5N9-part4 -> ../../sdg4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_ST3500413AS_5VMY21DL -> ../../sdm lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_ST3500413AS_5VMY21DL-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_SanDisk_SD6SB1M1_142000400317 -> ../../sda lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_SanDisk_SD6SB1M1_142000400317-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_SanDisk_SD6SB1M1_142000400317-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_SanDisk_SD6SB1M1_142000400317-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_SanDisk_SD6SB1M1_142000400317-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A007FBKG -> ../../sdd lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part128 -> ../../sdd128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part51 -> ../../sdd51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part52 -> ../../sdd52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part53 -> ../../sdd53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part54 -> ../../sdd54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part55 -> ../../sdd55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part56 -> ../../sdd56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG -> ../../sdc lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part128 -> ../../sdc128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part51 -> ../../sdc51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part52 -> ../../sdc52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part53 -> ../../sdc53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part54 -> ../../sdc54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part55 -> ../../sdc55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part56 -> ../../sdc56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG -> ../../sdb lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part128 -> ../../sdb128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part51 -> ../../sdb51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part52 -> ../../sdb52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part53 -> ../../sdb53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part54 -> ../../sdb54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part55 -> ../../sdb55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part56 -> ../../sdb56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_TOSHIBA_HDWR11A_91C0A03ZFBKG -> ../../sdi lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_TOSHIBA_MQ01ABD1_37MCWNJRT -> ../../sdh lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_TOSHIBA_MQ01ABD1_37MCWNJRT-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_TOSHIBA_MQ01ABD1_37MCWNJRT-part4 -> ../../sdh4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_WDC_WD7500BPKX-7_WD-WX51A150PNP7 -> ../../sdl lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_WDC_WD7500BPKX-7_WD-WX51A150PNP7-part2 -> ../../sdl2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_WDC_WD7500BPKX-7_WD-WX51A150PNP7-part3 -> ../../sdl3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_WDC_WD7500BPKX-7_WD-WX71A73E5533 -> ../../sdf lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_WDC_WD7500BPKX-7_WD-WX71A73E5533-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-0ATA_WDC_WD7500BPKX-7_WD-WXF1EA4CSA07 -> ../../sdj lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_WDC_WD7500BPKX-7_WD-WXF1EA4CSA07-part2 -> ../../sdj2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-0ATA_WDC_WD7500BPKX-7_WD-WXF1EA4CSA07-part3 -> ../../sdj3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_Hitachi_HDE721010SLA330_MS2R0UAS -> ../../sdk lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_Hitachi_HDE721010SLA330_MS2R0UAS-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_Hitachi_HDE721010SLA330_MS2R0UAS-part2 -> ../../sdk2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_Hitachi_HDE721010SLA330_MS2R0UAS-part3 -> ../../sdk3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_Hitachi_HDE721010SLA330_MS2R0UAS-part4 -> ../../sdk4 lrwxrwxrwx 1 root root 9 Oct 18 03:15 scsi-1ATA_SATA_SSD_21112525604525 -> ../../sde lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-1ATA_SATA_SSD_21112525604525-part1 -> ../../sde1 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-1ATA_SATA_SSD_21112525604525-part2 -> ../../sde2 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-1ATA_SATA_SSD_21112525604525-part3 -> ../../sde3 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-1ATA_SATA_SSD_21112525604525-part4 -> ../../sde4 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-1ATA_SATA_SSD_21112525604525-part5 -> ../../sde5 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_ST1000LM035-1RK172_WL14W5N9 -> ../../sdg lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_ST1000LM035-1RK172_WL14W5N9-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_ST1000LM035-1RK172_WL14W5N9-part4 -> ../../sdg4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_ST3500413AS_5VMY21DL -> ../../sdm lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_ST3500413AS_5VMY21DL-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_SanDisk_SD6SB1M128G1001_142000400317 -> ../../sda lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_SanDisk_SD6SB1M128G1001_142000400317-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_SanDisk_SD6SB1M128G1001_142000400317-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_SanDisk_SD6SB1M128G1001_142000400317-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_SanDisk_SD6SB1M128G1001_142000400317-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A007FBKG -> ../../sdd lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part128 -> ../../sdd128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part51 -> ../../sdd51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part52 -> ../../sdd52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part53 -> ../../sdd53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part54 -> ../../sdd54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part55 -> ../../sdd55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A007FBKG-part56 -> ../../sdd56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG -> ../../sdc lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part128 -> ../../sdc128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part51 -> ../../sdc51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part52 -> ../../sdc52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part53 -> ../../sdc53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part54 -> ../../sdc54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part55 -> ../../sdc55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part56 -> ../../sdc56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG -> ../../sdb lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part128 -> ../../sdb128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part51 -> ../../sdb51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part52 -> ../../sdb52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part53 -> ../../sdb53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part54 -> ../../sdb54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part55 -> ../../sdb55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part56 -> ../../sdb56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_TOSHIBA_HDWR11A_91C0A03ZFBKG -> ../../sdi lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_TOSHIBA_MQ01ABD100_37MCWNJRT -> ../../sdh lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_TOSHIBA_MQ01ABD100_37MCWNJRT-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_TOSHIBA_MQ01ABD100_37MCWNJRT-part4 -> ../../sdh4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_WDC_WD7500BPKX-75HPJT0_WD-WX51A150PNP7 -> ../../sdl lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_WDC_WD7500BPKX-75HPJT0_WD-WX51A150PNP7-part2 -> ../../sdl2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_WDC_WD7500BPKX-75HPJT0_WD-WX51A150PNP7-part3 -> ../../sdl3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_WDC_WD7500BPKX-75HPJT0_WD-WX71A73E5533 -> ../../sdf lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_WDC_WD7500BPKX-75HPJT0_WD-WX71A73E5533-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-1ATA_WDC_WD7500BPKX-75HPJT0_WD-WXF1EA4CSA07 -> ../../sdj lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_WDC_WD7500BPKX-75HPJT0_WD-WXF1EA4CSA07-part2 -> ../../sdj2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-1ATA_WDC_WD7500BPKX-75HPJT0_WD-WXF1EA4CSA07-part3 -> ../../sdj3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-350000397a4a08263 -> ../../sdh lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-350000397a4a08263-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-350000397a4a08263-part4 -> ../../sdh4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-35000039af8e114ea -> ../../sdd lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-35000039af8e114ea-part128 -> ../../sdd128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e114ea-part51 -> ../../sdd51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e114ea-part52 -> ../../sdd52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e114ea-part53 -> ../../sdd53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e114ea-part54 -> ../../sdd54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e114ea-part55 -> ../../sdd55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e114ea-part56 -> ../../sdd56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-35000039af8e120fa -> ../../sdc lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-35000039af8e120fa-part128 -> ../../sdc128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e120fa-part51 -> ../../sdc51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e120fa-part52 -> ../../sdc52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e120fa-part53 -> ../../sdc53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e120fa-part54 -> ../../sdc54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e120fa-part55 -> ../../sdc55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e120fa-part56 -> ../../sdc56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-35000039af8e12235 -> ../../sdb lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-35000039af8e12235-part128 -> ../../sdb128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e12235-part51 -> ../../sdb51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e12235-part52 -> ../../sdb52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e12235-part53 -> ../../sdb53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e12235-part54 -> ../../sdb54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e12235-part55 -> ../../sdb55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-35000039af8e12235-part56 -> ../../sdb56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-35000039b28d03342 -> ../../sdi lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-35000c5002b05da67 -> ../../sdm lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35000c5002b05da67-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-35000c500b978e573 -> ../../sdg lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35000c500b978e573-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35000c500b978e573-part4 -> ../../sdg4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-35000cca35ee6323d -> ../../sdk lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35000cca35ee6323d-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35000cca35ee6323d-part2 -> ../../sdk2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35000cca35ee6323d-part3 -> ../../sdk3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35000cca35ee6323d-part4 -> ../../sdk4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-350014ee60577714e -> ../../sdj lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-350014ee60577714e-part2 -> ../../sdj2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-350014ee60577714e-part3 -> ../../sdj3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-350014ee6058cb1db -> ../../sdl lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-350014ee6058cb1db-part2 -> ../../sdl2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-350014ee6058cb1db-part3 -> ../../sdl3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-350014ee659266506 -> ../../sdf lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-350014ee659266506-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-35001b44c1b7723bd -> ../../sda lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35001b44c1b7723bd-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35001b44c1b7723bd-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35001b44c1b7723bd-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-35001b44c1b7723bd-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_Hitachi_HDE72101_MS2R0UAS -> ../../sdk lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_Hitachi_HDE72101_MS2R0UAS-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_Hitachi_HDE72101_MS2R0UAS-part2 -> ../../sdk2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_Hitachi_HDE72101_MS2R0UAS-part3 -> ../../sdk3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_Hitachi_HDE72101_MS2R0UAS-part4 -> ../../sdk4 lrwxrwxrwx 1 root root 9 Oct 18 03:15 scsi-SATA_SATA_SSD_21112525604525 -> ../../sde lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-SATA_SATA_SSD_21112525604525-part1 -> ../../sde1 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-SATA_SATA_SSD_21112525604525-part2 -> ../../sde2 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-SATA_SATA_SSD_21112525604525-part3 -> ../../sde3 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-SATA_SATA_SSD_21112525604525-part4 -> ../../sde4 lrwxrwxrwx 1 root root 10 Oct 18 03:15 scsi-SATA_SATA_SSD_21112525604525-part5 -> ../../sde5 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_ST1000LM035-1RK1_WL14W5N9 -> ../../sdg lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_ST1000LM035-1RK1_WL14W5N9-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_ST1000LM035-1RK1_WL14W5N9-part4 -> ../../sdg4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_ST3500413AS_5VMY21DL -> ../../sdm lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_ST3500413AS_5VMY21DL-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_SanDisk_SD6SB1M1_142000400317 -> ../../sda lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_SanDisk_SD6SB1M1_142000400317-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_SanDisk_SD6SB1M1_142000400317-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_SanDisk_SD6SB1M1_142000400317-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_SanDisk_SD6SB1M1_142000400317-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A007FBKG -> ../../sdd lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A007FBKG-part128 -> ../../sdd128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A007FBKG-part51 -> ../../sdd51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A007FBKG-part52 -> ../../sdd52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A007FBKG-part53 -> ../../sdd53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A007FBKG-part54 -> ../../sdd54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A007FBKG-part55 -> ../../sdd55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A007FBKG-part56 -> ../../sdd56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0BEFBKG -> ../../sdc lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part128 -> ../../sdc128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part51 -> ../../sdc51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part52 -> ../../sdc52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part53 -> ../../sdc53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part54 -> ../../sdc54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part55 -> ../../sdc55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0BEFBKG-part56 -> ../../sdc56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0HQFBKG -> ../../sdb lrwxrwxrwx 1 root root 12 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part128 -> ../../sdb128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part51 -> ../../sdb51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part52 -> ../../sdb52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part53 -> ../../sdb53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part54 -> ../../sdb54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part55 -> ../../sdb55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_61U0A0HQFBKG-part56 -> ../../sdb56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_TOSHIBA_HDWR11A_91C0A03ZFBKG -> ../../sdi lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_TOSHIBA_MQ01ABD1_37MCWNJRT -> ../../sdh lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_TOSHIBA_MQ01ABD1_37MCWNJRT-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_TOSHIBA_MQ01ABD1_37MCWNJRT-part4 -> ../../sdh4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_WDC_WD7500BPKX-7_WD-WX51A150PNP7 -> ../../sdl lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_WDC_WD7500BPKX-7_WD-WX51A150PNP7-part2 -> ../../sdl2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_WDC_WD7500BPKX-7_WD-WX51A150PNP7-part3 -> ../../sdl3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_WDC_WD7500BPKX-7_WD-WX71A73E5533 -> ../../sdf lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_WDC_WD7500BPKX-7_WD-WX71A73E5533-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 scsi-SATA_WDC_WD7500BPKX-7_WD-WXF1EA4CSA07 -> ../../sdj lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_WDC_WD7500BPKX-7_WD-WXF1EA4CSA07-part2 -> ../../sdj2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 scsi-SATA_WDC_WD7500BPKX-7_WD-WXF1EA4CSA07-part3 -> ../../sdj3 lrwxrwxrwx 1 root root 9 Oct 24 10:13 usb-General_USB_Flash_Disk_04FL876HSOVMPIZ4-0:0 -> ../../sdn lrwxrwxrwx 1 root root 10 Oct 24 10:13 usb-General_USB_Flash_Disk_04FL876HSOVMPIZ4-0:0-part1 -> ../../sdn1 lrwxrwxrwx 1 root root 10 Oct 24 10:13 usb-General_USB_Flash_Disk_04FL876HSOVMPIZ4-0:0-part2 -> ../../sdn2 lrwxrwxrwx 1 root root 10 Oct 24 10:13 usb-General_USB_Flash_Disk_04FL876HSOVMPIZ4-0:0-part3 -> ../../sdn3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x50000397a4a08263 -> ../../sdh lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x50000397a4a08263-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x50000397a4a08263-part4 -> ../../sdh4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x5000039af8e114ea -> ../../sdd lrwxrwxrwx 1 root root 12 Oct 18 03:10 wwn-0x5000039af8e114ea-part128 -> ../../sdd128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e114ea-part51 -> ../../sdd51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e114ea-part52 -> ../../sdd52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e114ea-part53 -> ../../sdd53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e114ea-part54 -> ../../sdd54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e114ea-part55 -> ../../sdd55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e114ea-part56 -> ../../sdd56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x5000039af8e120fa -> ../../sdc lrwxrwxrwx 1 root root 12 Oct 18 03:10 wwn-0x5000039af8e120fa-part128 -> ../../sdc128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e120fa-part51 -> ../../sdc51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e120fa-part52 -> ../../sdc52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e120fa-part53 -> ../../sdc53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e120fa-part54 -> ../../sdc54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e120fa-part55 -> ../../sdc55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e120fa-part56 -> ../../sdc56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x5000039af8e12235 -> ../../sdb lrwxrwxrwx 1 root root 12 Oct 18 03:10 wwn-0x5000039af8e12235-part128 -> ../../sdb128 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e12235-part51 -> ../../sdb51 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e12235-part52 -> ../../sdb52 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e12235-part53 -> ../../sdb53 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e12235-part54 -> ../../sdb54 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e12235-part55 -> ../../sdb55 lrwxrwxrwx 1 root root 11 Oct 18 03:10 wwn-0x5000039af8e12235-part56 -> ../../sdb56 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x5000039b28d03342 -> ../../sdi lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x5000c5002b05da67 -> ../../sdm lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5000c5002b05da67-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x5000c500b978e573 -> ../../sdg lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5000c500b978e573-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5000c500b978e573-part4 -> ../../sdg4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x5000cca35ee6323d -> ../../sdk lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5000cca35ee6323d-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5000cca35ee6323d-part2 -> ../../sdk2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5000cca35ee6323d-part3 -> ../../sdk3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5000cca35ee6323d-part4 -> ../../sdk4 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x50014ee60577714e -> ../../sdj lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x50014ee60577714e-part2 -> ../../sdj2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x50014ee60577714e-part3 -> ../../sdj3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x50014ee6058cb1db -> ../../sdl lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x50014ee6058cb1db-part2 -> ../../sdl2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x50014ee6058cb1db-part3 -> ../../sdl3 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x50014ee659266506 -> ../../sdf lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x50014ee659266506-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Oct 18 03:10 wwn-0x5001b44c1b7723bd -> ../../sda lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5001b44c1b7723bd-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5001b44c1b7723bd-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5001b44c1b7723bd-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Oct 18 03:10 wwn-0x5001b44c1b7723bd-part4 -> ../../sda4 ================================ Mount points: ================================= Device Mount_Point Type Options /dev/md118 / xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/md120 /mnt/ssd xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdn3 /tmp/n3 ext2 (rw,relatime) ========================== sda2/boot/grub2/grub.cfg: =========================== -------------------------------------------------------------------------------- # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -f ${config_directory}/grubenv ]; then load_env -f ${config_directory}/grubenv elif [ -s $prefix/grubenv ]; then load_env fi if [ "${env_block}" ] ; then set env_block="(${root})${env_block}" export env_block load_env -f "${env_block}" fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry if [ "${env_block}" ] ; then save_env -f "${env_block}" next_entry fi set boot_once=true else set default="${saved_entry}" 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}" if [ "${env_block}" ] ; then save_env -f "${env_block}" saved_entry else save_env saved_entry fi 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_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 4fe67d3c-13b6-48d6-b134-b371898901ea else search --no-floppy --fs-uuid --set=root 4fe67d3c-13b6-48d6-b134-b371898901ea fi font="/usr/share/grub2/unicode.pf2" fi if loadfont $font ; then if [ "${grub_platform}" = "efi" ]; then echo "Please press 't' to show the boot menu on this console" fi set gfxmode=auto load_video insmod gfxterm fi terminal_input console terminal_output gfxterm insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 4fe67d3c-13b6-48d6-b134-b371898901ea else search --no-floppy --fs-uuid --set=root 4fe67d3c-13b6-48d6-b134-b371898901ea fi insmod gfxmenu loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans-Bold14.pf2 loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans10.pf2 loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans12.pf2 loadfont ($root)/boot/grub2/themes/openSUSE/ascii.pf2 insmod png set theme=($root)/boot/grub2/themes/openSUSE/theme.txt export theme if [ x${boot_once} = xtrue ]; then set timeout=0 elif [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=2 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=2 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/00_tuned ### set tuned_params="" set tuned_initrd="" ### END /etc/grub.d/00_tuned ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'openSUSE Leap 15.2' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-4fe67d3c-13b6-48d6-b134-b371898901ea' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 4fe67d3c-13b6-48d6-b134-b371898901ea else search --no-floppy --fs-uuid --set=root 4fe67d3c-13b6-48d6-b134-b371898901ea fi echo 'Loading Linux 5.3.18-lp152.106-default ...' linux /boot/vmlinuz-5.3.18-lp152.106-default root=UUID=4fe67d3c-13b6-48d6-b134-b371898901ea quiet mitigations=auto echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.106-default } submenu 'Advanced options for openSUSE Leap 15.2' --hotkey=1 $menuentry_id_option 'gnulinux-advanced-4fe67d3c-13b6-48d6-b134-b371898901ea' { menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.106-default' --hotkey=2 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.106-default-advanced-4fe67d3c-13b6-48d6-b134-b371898901ea' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 4fe67d3c-13b6-48d6-b134-b371898901ea else search --no-floppy --fs-uuid --set=root 4fe67d3c-13b6-48d6-b134-b371898901ea fi echo 'Loading Linux 5.3.18-lp152.106-default ...' linux /boot/vmlinuz-5.3.18-lp152.106-default root=UUID=4fe67d3c-13b6-48d6-b134-b371898901ea quiet mitigations=auto echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.106-default } menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.106-default (recovery mode)' --hotkey=3 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.106-default-recovery-4fe67d3c-13b6-48d6-b134-b371898901ea' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 4fe67d3c-13b6-48d6-b134-b371898901ea else search --no-floppy --fs-uuid --set=root 4fe67d3c-13b6-48d6-b134-b371898901ea fi echo 'Loading Linux 5.3.18-lp152.106-default ...' linux /boot/vmlinuz-5.3.18-lp152.106-default root=UUID=4fe67d3c-13b6-48d6-b134-b371898901ea echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.106-default } menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.95-default' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.95-default-advanced-4fe67d3c-13b6-48d6-b134-b371898901ea' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 4fe67d3c-13b6-48d6-b134-b371898901ea else search --no-floppy --fs-uuid --set=root 4fe67d3c-13b6-48d6-b134-b371898901ea fi echo 'Loading Linux 5.3.18-lp152.95-default ...' linux /boot/vmlinuz-5.3.18-lp152.95-default root=UUID=4fe67d3c-13b6-48d6-b134-b371898901ea quiet mitigations=auto echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.95-default } menuentry 'openSUSE Leap 15.2, with Linux 5.3.18-lp152.95-default (recovery mode)' --hotkey=1 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.3.18-lp152.95-default-recovery-4fe67d3c-13b6-48d6-b134-b371898901ea' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod xfs set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2' 4fe67d3c-13b6-48d6-b134-b371898901ea else search --no-floppy --fs-uuid --set=root 4fe67d3c-13b6-48d6-b134-b371898901ea fi echo 'Loading Linux 5.3.18-lp152.95-default ...' linux /boot/vmlinuz-5.3.18-lp152.95-default root=UUID=4fe67d3c-13b6-48d6-b134-b371898901ea echo 'Loading initial ramdisk ...' initrd /boot/initrd-5.3.18-lp152.95-default } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_memtest86+ ### ### END /etc/grub.d/20_memtest86+ ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### ### BEGIN /etc/grub.d/80_suse_btrfs_snapshot ### ### END /etc/grub.d/80_suse_btrfs_snapshot ### ### BEGIN /etc/grub.d/90_persistent ### ### END /etc/grub.d/90_persistent ### ### BEGIN /etc/grub.d/95_textmode ### if [ "${grub_platform}" = "efi" ]; then # On EFI systems we can only have graphics *or* serial, so allow the user # to switch between the two hiddenentry 'Text mode' --hotkey 't' { set textmode=true terminal_output console } fi ### END /etc/grub.d/95_textmode ### -------------------------------------------------------------------------------- =============================== sda2/etc/fstab: ================================ -------------------------------------------------------------------------------- # diskfarm boot SSD LABEL=diskfarmsuse / xfs defaults 0 0 UUID=3982f3a2-3e59-4658-b18d-5a036572c6c7 swap swap defaults 0 0 LABEL=diskfarm-ssd /mnt/ssd xfs defaults 0 0 # diskfarm content disks LABEL=10Traid50md /mnt/10Traid50md xfs defaults 0 0 LABEL=10Traid50md-ext3 /mnt/slices/10Traid50md-ext3 ext3 defaults 0 0 LABEL=10Traid50md-reis /mnt/slices/10Traid50md-reiserfs reiserfs defaults 0 0 LABEL=10Tr50md-xfs /mnt/slices/10Traid50md-xfs xfs defaults 0 0 #fail#LABEL=4Traid5md /mnt/4Traid5md xfs defaults 0 0 #fail#LABEL=5000c5007a720d6c /mnt/slices/4Traid5md-ext3 ext3 defaults 0 0 #fail#LABEL=5000c5007a7 /mnt/slices/4Traid5md-vfat vfat defaults 0 0 #fail#LABEL=wwn-0x5000c50069 /mnt/slices/4Traid5md-reiserfs reiserfs defaults 0 0 #fail#LABEL=50...8050a3 /mnt/slices/4Traid5md-xfs xfs defaults 0 0 #fail#/mnt/4Traid5md/Backups/Scrp0250-72-att1..2017-post/Scrp0250-72-att1..p2..2017-post..dd-bs=64M /mnt/4Traid5md/Backups/Scrp0250-72-att1..2017-post/mnt ntfs defaults,uid=davidtg,gid=davidtg 0 0 #fail#/mnt/4Traid5md/Backups/Scrp0250-72-att2..2017-post/Scrp0250-72-att2..p2..2017-post..dd-bs=64M /mnt/4Traid5md/Backups/Scrp0250-72-att2..2017-post/mnt ntfs defaults,uid=davidtg,gid=davidtg 0 0 LABEL=750Graid5md /mnt/750Graid5md reiserfs defaults 0 0 #LABEL=wwn-0x50014ee605 #fail#LABEL=50...8cb1db /mnt/slices/750Graid5md-xfs xfs defaults 0 0 #fail#LABEL=wwn-0x5000cca35e /mnt/slices/750Graid5md-ext3 ext3 defaults 0 0 #fail#LABEL=wwn-0x5000cca360 /mnt/slices/750Graid5md-reiserfs reiserfs defaults 0 0 LABEL=scratch_reiserfs /mnt/scratch reiserfs defaults 0 0 ### # these should probably go away, but they're plugged in internally for now ... #gone#LABEL=arch-WX71A73E5533 /mnt/Archive-750 ntfs defaults 0 0 LABEL=GIFTarch-LM035 /mnt/GIFTarch-LM035 ext3 defaults 0 0 LABEL=GIFTarch-MQ01ABD /mnt/GIFTarch-MQ01ABD1 ext3 defaults 0 0 ### ### # removable disks LABEL=mp3backup /mnt/mp3 ntfs defaults,nofail 0 0 LABEL=Apri0120-5LZ4PZ83 /mnt/pix ntfs defaults,nofail 0 0 LABEL=WD16Tusb3 /mnt/WD16Tusb3 xfs defaults,nofail 0 0 LABEL=WD14Tusb3 /mnt/WD14Tusb3 xfs defaults,nofail 0 0 LABEL=WD10Tusb3 /mnt/WD10Tusb3 xfs defaults,nofail 0 0 /mnt/WD10Tusb3/Backups/AW-wings-acer/AW-wings-acer..dd-bs=64M-conv=noerror /mnt/WD10Tusb3/Backups/AW-wings-acer/mnt ntfs defaults,nofail,uid=1000,gid=1000 0 0 /mnt/WD10Tusb3/Backups/AW-quickbooks-tosh/AW-quickbooks-tosh..dd-bs=64M-conv=noerror /mnt/WD10Tusb3/Backups/AW-quickbooks-tosh/mnt ntfs defaults,nofail,uid=1000,gid=1000 0 0 LABEL=Seag4000-54-DavidBlue /mnt/Seag4000-54-DavidBlue ntfs defaults,nofail 0 0 LABEL=GIFTarch-TDBWT /mnt/GIFTarch-TDBWT ext3 defaults,nofail 0 0 LABEL=64JYTDBWT /mnt/slices/64JYTDBWT vfat defaults,nofail 0 0 LABEL=GIFTgoodies /mnt/GIFTgoodies ntfs defaults,nofail 0 0 ###/mnt/GIFTgoodies/Data/GetInspiredFlight/GIFTcams/00-Migrate /mnt/GIFTgoodies/Data/GetInspiredFlight/GIFTcams/00-Migrate.mnt ext3 defaults,nofail 0 0 ### ### # network resources jpo:/mnt/4TRaid10md /nfs/4Traid10md nfs defaults,soft,bg 0 0 gezebel:/mnt/hdd /nfs/gezebel-hdd nfs defaults,soft,bg 0 0 ### 2021 diskfarm suse 10T ### don't know the date # # 4Traid5md -> ../../md0p1 # System\x20Reserved -> ../../sda1 # # diskfarmsuse -> ../../sda2 # # diskfarm-ssd -> ../../sda4 # 5000c5007a720d6c -> ../../sdb2 # 5000c5007a7 -> ../../sdc2 # wwn-0x5000c50069 -> ../../sdd2 # 50...8050a3 -> ../../sde2 # 50...8cb1db -> ../../sdf3 # # mp3backup -> ../../sdg1 # arch-WX71A73E5533 -> ../../sdh1 # wwn-0x50014ee605 -> ../../sdi3 # System -> ../../sdj1 # wwn-0x5000cca360 -> ../../sdj3 # # scratch_reiserfs -> ../../sdj4 # New\x20Volume -> ../../sdk1 # # GIFTarch-LM035 -> ../../sdl1 # wwn-0x5000cca35e -> ../../sdl3 # # GIFTarch-MQ01ABD -> ../../sdm1 # # Seag4000-54-DavidBlue -> ../../sdn1 # # Apri0120-5LZ4PZ83 -> ../../sdo1 # # WD10Tusb3 -> ../../sdp1 # # GIFTgoodies -> ../../sdq1 -------------------------------------------------------------------------------- =================== sda2: Location of files loaded by Grub: ==================== GiB - GB File Fragment(s) 33.796363831 = 36.288569344 boot/grub2/grub.cfg 3 33.066001892 = 35.504349184 boot/grub2/i386-pc/core.img 1 58.073291779 = 62.355722240 boot/vmlinuz 1 58.073291779 = 62.355722240 boot/vmlinuz-5.3.18-lp152.106-default 1 58.457069397 = 62.767800320 boot/vmlinuz-5.3.18-lp152.95-default 1 58.029701233 = 62.308917248 boot/initrd 1 58.029701233 = 62.308917248 boot/initrd-5.3.18-lp152.106-default 1 57.711208344 = 61.966938112 boot/initrd-5.3.18-lp152.95-default 1 =========================== sdn1/efi/BOOT/grub.cfg: ============================ -------------------------------------------------------------------------------- with_gfx=1 gfxmode=auto locale_dir=$prefix/locale lang=en_US search --no-floppy --file /boot/x86_64/efi --set prefix=($root)/boot/x86_64/grub2-efi insmod efi_gop insmod efi_uga insmod gzio insmod gettext if [ "$with_gfx" = 1 ] ; then insmod gfxterm insmod gfxmenu insmod png echo "Please press 't' to show the boot menu on this console" terminal_output gfxterm theme=$prefix/themes/openSUSE/theme.txt export theme loadfont $prefix/unicode.pf2 loadfont $prefix/themes/openSUSE/DejaVuSans10.pf2 loadfont $prefix/themes/openSUSE/DejaVuSans12.pf2 loadfont $prefix/themes/openSUSE/DejaVuSans-Bold14.pf2 fi if sleep --interruptible 0 ; then timeout=60 fi default=1 # look for an installed SUSE system and boot it menuentry "Boot from Hard Disk" --class opensuse --class gnu-linux --class gnu --class os { if search --no-floppy --file /efi/boot/fallback.efi --set ; then for os in opensuse sles caasp ; do if [ -f /efi/$os/grub.efi ] ; then chainloader /efi/$os/grub.efi fi done fi } menuentry 'Installation' --class opensuse --class gnu-linux --class gnu --class os { set gfxpayload=keep echo 'Loading kernel ...' linuxefi /boot/x86_64/loader/linux splash=silent echo 'Loading initial ramdisk ...' initrdefi /boot/x86_64/loader/initrd } menuentry 'Upgrade' --class opensuse --class gnu-linux --class gnu --class os { set gfxpayload=keep echo 'Loading kernel ...' linuxefi /boot/x86_64/loader/linux splash=silent upgrade=1 echo 'Loading initial ramdisk ...' initrdefi /boot/x86_64/loader/initrd } submenu 'More ...' { menuentry 'Rescue System' --class opensuse --class gnu-linux --class gnu { set gfxpayload=keep echo 'Loading kernel ...' linuxefi /boot/x86_64/loader/linux splash=silent rescue=1 echo 'Loading initial ramdisk ...' initrdefi /boot/x86_64/loader/initrd } menuentry 'Boot Linux System' --class opensuse --class gnu-linux --class gnu { set gfxpayload=keep echo 'Loading kernel ...' linuxefi /boot/x86_64/loader/linux splash=silent systemboot=1 echo 'Loading initial ramdisk ...' initrdefi /boot/x86_64/loader/initrd } menuentry 'Check Installation Media' --class opensuse --class gnu-linux --class gnu { set gfxpayload=keep echo 'Loading kernel ...' linuxefi /boot/x86_64/loader/linux splash=silent mediacheck=1 echo 'Loading initial ramdisk ...' initrdefi /boot/x86_64/loader/initrd } } # On EFI systems we can only have graphics *or* serial, so allow the user # to switch between the two hiddenentry 'Text mode' --hotkey 't' { set textmode=true terminal_output console } -------------------------------------------------------------------------------- ======================== Unknown MBRs/Boot Sectors/etc: ======================== Unknown BootLoader on sde2 00000000 90 90 27 00 00 00 00 00 08 00 00 00 00 00 00 00 |..'.............| 00000010 41 04 06 00 00 00 00 00 a0 90 27 00 00 00 00 00 |A.........'.....| 00000020 08 00 00 00 00 00 00 00 05 ec 05 00 00 00 00 00 |................| 00000030 a8 90 27 00 00 00 00 00 08 00 00 00 00 00 00 00 |..'.............| 00000040 7e f0 05 00 00 00 00 00 b8 90 27 00 00 00 00 00 |~.........'.....| 00000050 08 00 00 00 00 00 00 00 85 f0 05 00 00 00 00 00 |................| 00000060 d0 90 27 00 00 00 00 00 08 00 00 00 00 00 00 00 |..'.............| 00000070 82 1e 06 00 00 00 00 00 d8 90 27 00 00 00 00 00 |..........'.....| 00000080 08 00 00 00 00 00 00 00 99 ff 05 00 00 00 00 00 |................| 00000090 00 91 27 00 00 00 00 00 08 00 00 00 00 00 00 00 |..'.............| 000000a0 7e ff 05 00 00 00 00 00 18 91 27 00 00 00 00 00 |~.........'.....| 000000b0 08 00 00 00 00 00 00 00 6a 2a 06 00 00 00 00 00 |........j*......| 000000c0 20 91 27 00 00 00 00 00 08 00 00 00 00 00 00 00 | .'.............| 000000d0 ad ff 05 00 00 00 00 00 48 91 27 00 00 00 00 00 |........H.'.....| 000000e0 08 00 00 00 00 00 00 00 6e c7 05 00 00 00 00 00 |........n.......| 000000f0 50 91 27 00 00 00 00 00 08 00 00 00 00 00 00 00 |P.'.............| 00000100 c8 ff 05 00 00 00 00 00 78 91 27 00 00 00 00 00 |........x.'.....| 00000110 08 00 00 00 00 00 00 00 6e c7 05 00 00 00 00 00 |........n.......| 00000120 80 91 27 00 00 00 00 00 08 00 00 00 00 00 00 00 |..'.............| 00000130 de ff 05 00 00 00 00 00 98 91 27 00 00 00 00 00 |..........'.....| 00000140 08 00 00 00 00 00 00 00 f4 ff 05 00 00 00 00 00 |................| 00000150 b0 91 27 00 00 00 00 00 08 00 00 00 00 00 00 00 |..'.............| 00000160 35 0a 06 00 00 00 00 00 d8 91 27 00 00 00 00 00 |5.........'.....| 00000170 08 00 00 00 00 00 00 00 6e c7 05 00 00 00 00 00 |........n.......| 00000180 e0 91 27 00 00 00 00 00 08 00 00 00 00 00 00 00 |..'.............| 00000190 08 00 06 00 00 00 00 00 f8 91 27 00 00 00 00 00 |..........'.....| 000001a0 08 00 00 00 00 00 00 00 1a 00 06 00 00 00 00 00 |................| 000001b0 20 92 27 00 00 00 00 00 08 00 00 00 00 00 00 00 | .'.............| 000001c0 6e c7 05 00 00 00 00 00 28 92 27 00 00 00 00 00 |n.......(.'.....| 000001d0 08 00 00 00 00 00 00 00 1f 00 06 00 00 00 00 00 |................| 000001e0 40 92 27 00 00 00 00 00 08 00 00 00 00 00 00 00 |@.'.............| 000001f0 2e 00 06 00 00 00 00 00 68 92 27 00 00 00 00 00 |........h.'.....| 00000200

Andrei, et al -- ...and then Andrei Borzenkov said... % On 24.10.2022 13:23, David T-G wrote: % > % > I'm finally back, and so I've popped bootinfoscript onto my rescue thumb % > drive and run it. Pasted below my signature is the RESULTS1.txt file. I % % I wanted to comment on it, but it is not included in reply because you made Oops. And here I thought I was being clever by taking care of future clutter ... :-/ % it signature. So TLDR - it sounds like core.img was overwritten on % /boot/gub2/i386-pc. May be it was deleted when new file was generated but % information in MBR was not updated. Oho! How interesting. Sooooo ... How do I fix that? I wonder if boot to rescue -> mount root under /tmp -> chroot -> grub2 -magic -fixarg is what I need. % ... % > % > Meanwhile, I even tried a clean install to the mirrors on sde and it % > STILL doesn't boot. Weird ... % % I do not understand what "it" refers to in the last sentence. grub on sda? % "New clean install on sde"? "It" is diskfarm, the computer in question. I had hoped that a fresh install on the new drive would result in a working system. It didn't :-/ Thanks again :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

On 26.10.2022 05:42, David T-G wrote:

Andrei, et al --

...and then David T-G home said... % % ...and then Andrei Borzenkov said... % ... % % it signature. So TLDR - it sounds like core.img was overwritten on % % /boot/gub2/i386-pc. May be it was deleted when new file was generated but % % information in MBR was not updated. % % Oho! How interesting.

BTW, there *is* a core.img file, but it's dated 10/17 after all of his trying and retrying. No idea how it looked right after failure :-( But that IS dated before I ran bootinfoscript and generated RESULTS1.txt yesterday ...

% % Sooooo ... How do I fix that? I wonder if boot to rescue -> mount root % under /tmp -> chroot -> grub2 -magic -fixarg is what I need. [snip]

Alas,

# make chroot stuff # chroot grub2-install /dev/sda

didn't work; I get a

grub2-install: error: cannot find EFI directory.

You are booted in EFI mode. Now you wrote a lot of all caps and expletives and swear words in this thread but you never mentioned whether you were using legacy BIOS or EFI boot in the first place. If you are actually using legacy BIOS you can either boot in legacy BIOS mode, or force installation using grub2-install --target=i386-pc /dev/sda assuming /dev/sda is really your BIOS boot device (which we have no way to determine). If you do not use legacy BIOS boot the bootinfoscript is mostly useless.

error and it dies. I dunno how to force it [new grub2 install] to be legacy and use that MBR that it [previous grub2] supposedly has.

ARRRRRGH! :-(

:-D

On 29.10.2022 05:57, David T-G wrote: ...

This is what my working machine, with a single boot SSD and a mirrored pair of data disks, said:

============================= Boot Info Summary: ===============================

=> Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 105657120 of the same hard drive for core.img. core.img is at this location and looks for (,gpt2)/boot/grub2. It also embeds following components:

modules --------------------------------------------------------------------------- fshelp xfs part_gpt biosdisk ---------------------------------------------------------------------------

As you see, grub2 is detected as v2.00 and the content of core.img is parsed. ...

GUID Partition Table detected.

Partition Attrs Start Sector End Sector # of Sectors System /dev/sda1 2,048 69,208,063 69,206,016 Swap partition (Linux) /dev/sda2 69,208,064 136,316,927 67,108,864 Data partition (Linux) /dev/sda3 B 136,316,928 203,425,791 67,108,864 Data partition (Linux) /dev/sda4 203,425,792 250,069,646 46,643,855 Data partition (Linux)

Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set

I wonder if the "B" flag (which, curiously, is on the "next" rather than "curr" slice) suggests anything.

This flag is not used by grub2 anyway. I believe it is used by syslinux gptmbr code (may be there are other bootloaders that use it).

This is what the dead machine, with sda boot SSD and new sde mirror SSD and lots of data disks, said:

============================= Boot Info Summary: ===============================

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 69344384 of the same hard drive for core.img. core.img is at this location.

As you see it is detected as v1.99 which is wrong version for your Leap release. Also it does not show the content of core.img. While this can be due to bug in bootinfoscript, this also suggests that MBR contains old content and points to disk location where there is no valid core.img. bootinfoscript just looks for known signatures in the first sector of this location. May be this sector is still valid. You can try to find out the the exact disk block of /boot/grub2/core.img on this disk. Something like bor@bor-Latitude-E5450:~$ sudo filefrag -v /boot/grub/x86_64-efi/core.efi Filesystem type is: ef53 File size of /boot/grub/x86_64-efi/core.efi is 147456 (36 blocks of 4096 bytes) ext: logical_offset: physical_offset: length: expected: flags: 0: 0.. 35: 58993088.. 58993123: 36: last,eof /boot/grub/x86_64-efi/core.efi: 1 extent found bor@bor-Latitude-E5450:~$ File offset on partition is shown in physical_offset column and is 58993088 blocks of size 4096. Each block is 8 x 512 sectors. In my case /boot is on /dev/sda4, so bor@bor-Latitude-E5450:~$ LC_ALL=C sudo fdisk -l /dev/sda ... Units: sectors of 1 * 512 = 512 bytes ... Device Start End Sectors Size Type ... /dev/sda4 7399424 943667199 936267776 446.4G Linux filesystem /dev/sda4 starts at sector 7399424 so the absolute disk offset of the file in sectors is 7399424 + 58993088*8 == 479344128 Compare the result with bootinfoscript output (looks at sector 70108480 of the same hard drive for core.img). Do they match?

=> 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 (v1.99-2.00) is installed in the MBR of /dev/sde and looks at sector 70108480 of the same hard drive for core.img, but core.img can not be found at this location.

Again, this could be the old installation in MBR. In this case even the first sector has the wrong (at least, unknown) content.

=> Windows 7/8/2012 is installed in the MBR of /dev/sdf. => No boot loader is installed in the MBR of /dev/sdg. => No boot loader is installed in the MBR of /dev/sdh. => No boot loader is installed in the MBR of /dev/sdi. => No boot loader is installed in the MBR of /dev/sdj. => Windows 7/8/2012 is installed in the MBR of /dev/sdk. => No boot loader is installed in the MBR of /dev/sdl. => No boot loader is installed in the MBR of /dev/sdm. => ISOhybrid (Syslinux 4.05 and higher) is installed in the MBR of /dev/sdn. ... ============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________ Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors Disk model: SanDisk SD6SB1M1 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/sda1 * 1 250,069,679 250,069,679 ee GPT

GUID Partition Table detected.

Partition Attrs Start Sector End Sector # of Sectors System /dev/sda1 2,048 69,208,063 69,206,016 Swap partition (Linux) /dev/sda2 69,208,064 136,316,927 67,108,864 Data partition (Linux) /dev/sda3 B 136,316,928 203,425,791 67,108,864 Data partition (Linux) /dev/sda4 203,425,792 250,069,646 46,643,855 Data partition (Linux)

Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set

Drive: sde _____________________________________________________________________ Disk /dev/sde: 238.5 GiB, 256060514304 bytes, 500118192 sectors Disk model: SATA SSD 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 * 1 500,118,191 500,118,191 ee GPT

GUID Partition Table detected.

Partition Attrs Start Sector End Sector # of Sectors System /dev/sde1 4,096 71,303,167 71,299,072 Swap partition (Linux) /dev/sde2 71,303,168 142,606,335 71,303,168 EFI System partition /dev/sde3 142,606,336 213,909,503 71,303,168 EFI System partition /dev/sde4 213,909,504 500,117,503 286,208,000 RAID partition (Linux) /dev/sde5 34 4,095 4,062 Data partition (Linux)

Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set

Note that I did not set up sde2 and sde3 as EFI system partitions when attempting to install there; they were originally mirrors just like sde4 and it seems that the install changed them. But I don't know how or when that happened; that's a guess.

Thanks again & HANN

:-D

David T-G composed on 2022-10-30 20:06 (UTC):

%> ============================= Boot Info Summary: =============================== %> => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector %> 69344384 of the same hard drive for core.img. core.img is at this location. % % As you see it is detected as v1.99 which is wrong version for your Leap % release. Also it does not show the content of core.img. While this can be % due to bug in bootinfoscript, this also suggests that MBR contains old

But ... but ... Why the wrong version? They are both the same and they were installed from the same media! Back in September in ... %> => Grub2 (v1.99-2.00) is installed in the MBR of /dev/sde and looks at sector %> 70108480 of the same hard drive for core.img, but core.img can not be %> found at this location.

% Again, this could be the old installation in MBR. In this case even the % first sector has the wrong (at least, unknown) content.

This drive was brand new in the box when I installed it, and I used the 15.2 installation thumb drive. I don't know why it's 1.99-2.00 and I don't know why it's different from the existing working jpo /dev/sda nor the existing broken diskfarm /dev/sda. Definitely confusing *sigh*

Is either /dev/sda or /dev/sde an old PATA disk? Did you ever use a 12.1 installation media, or some other old distro, such as Knoppix, to perform any kind of Grub repair on any installation, whether or not on that particular disk? Grub setup never gets uninstalled from a disk. It only goes away by being overwritten by something, or via a wipe. If an old installation ever used it, and nothing ever had reason to overwrite or wipe it, then there's your reason why it's there. Grub isn't always installed to the disk where the installation is that it's being set up from. Once upon a time (with various old BIOS and disk host "controllers"), an installation on /dev/sde couldn't be booted from /dev/sde anywhere (BIOS can't count to 5, or even 3), but needed to have the bootloader on a disk the BIOS could find, such as /dev/sda, to get /dev/sdeN booted. Multiboot with 4 non-RAIDed disks plus Windows is fragile. Multiply the fragility for every non-RAID disk and every RAID added beyond that. Your trouble was inevitable. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

On 10/28/22 22:57, David T-G wrote:

Andrei, et a --

...and then Andrei Borzenkov said... % On 26.10.2022 05:42, David T-G wrote: % > Andrei, et al -- % > % > ...and then David T-G home said... % > % ... % > % Sooooo ... How do I fix that? I wonder if boot to rescue -> mount root % > % under /tmp -> chroot -> grub2 -magic -fixarg is what I need. % > [snip] % > % > Alas, % > % > # make chroot stuff % > # chroot % > grub2-install /dev/sda % > % > didn't work; I get a % > % > grub2-install: error: cannot find EFI directory. % % You are booted in EFI mode. Now you wrote a lot of all caps and expletives

I don't know how I did that unless the install & rescue thumb drives makes it so. My BIOS, as far as I know, never offered nor required it.

Any suggestions on how I can get back to legacy mode?

% and swear words in this thread but you never mentioned whether you were

*sigh* That's frustration, despair, and a little bit of stark terror. We've already had a very bad year for data; if this computer also goes away I might as well just shoot myself. And the biggest problem is that I have no idea how I got to this point. It's like waking up one morning and finding my gas guzzler replaced with an electric vehicle. Sure, it's cool and all the rage, but I don't know anything about how to operate it and don't even have a charger. I know nothing about EFI/UEFI and have no idea why this trusty happy machine suddenly decided it would be a good thing to, apparently, switch to it.

% using legacy BIOS or EFI boot in the first place.

I never, ever, ever thought I would be in EFI mode, regardless of from what device I booted. I didn't select EFI/UEFI in the boot menu of my BIOS and simply said to boot first from sda and second from a USB drive.

% % If you are actually using legacy BIOS you can either boot in legacy BIOS % mode, or force installation using % % grub2-install --target=i386-pc /dev/sda

I *think* I tried this, but I'll try it for sure when I am home again.

% % assuming /dev/sda is really your BIOS boot device (which we have no way to % determine).

Indeed. I certainly thought that it was, since that's the only disk that has an OS on it and the disk to which I installed LEAP, but I'm obviously in no position to know ...

% % If you do not use legacy BIOS boot the bootinfoscript is mostly useless.

Here's hoping it can be useful, then :-) Let's go back to my previous submissions for a moment.

This is what my working machine, with a single boot SSD and a mirrored pair of data disks, said:

============================= Boot Info Summary: ===============================

=> Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 105657120 of the same hard drive for core.img. core.img is at this location and looks for (,gpt2)/boot/grub2. It also embeds following components:

modules --------------------------------------------------------------------------- fshelp xfs part_gpt biosdisk --------------------------------------------------------------------------- => No boot loader is installed in the MBR of /dev/sdb. => No boot loader is installed in the MBR of /dev/sdc. ... ============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________ Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors Disk model: SAMSUNG MZ7LN128 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/sda1 * 1 250,069,679 250,069,679 ee GPT

GUID Partition Table detected.

Partition Attrs Start Sector End Sector # of Sectors System /dev/sda1 2,048 69,208,063 69,206,016 Swap partition (Linux) /dev/sda2 69,208,064 136,316,927 67,108,864 Data partition (Linux) /dev/sda3 B 136,316,928 203,425,791 67,108,864 Data partition (Linux) /dev/sda4 203,425,792 250,069,646 46,643,855 Data partition (Linux)

Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set

I wonder if the "B" flag (which, curiously, is on the "next" rather than "curr" slice) suggests anything.

This is what the dead machine, with sda boot SSD and new sde mirror SSD and lots of data disks, said:

============================= Boot Info Summary: ===============================

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 69344384 of the same hard drive for core.img. core.img is at this location. => 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 (v1.99-2.00) is installed in the MBR of /dev/sde and looks at sector 70108480 of the same hard drive for core.img, but core.img can not be found at this location. => Windows 7/8/2012 is installed in the MBR of /dev/sdf. => No boot loader is installed in the MBR of /dev/sdg. => No boot loader is installed in the MBR of /dev/sdh. => No boot loader is installed in the MBR of /dev/sdi. => No boot loader is installed in the MBR of /dev/sdj. => Windows 7/8/2012 is installed in the MBR of /dev/sdk. => No boot loader is installed in the MBR of /dev/sdl. => No boot loader is installed in the MBR of /dev/sdm. => ISOhybrid (Syslinux 4.05 and higher) is installed in the MBR of /dev/sdn. ... ============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________ Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors Disk model: SanDisk SD6SB1M1 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/sda1 * 1 250,069,679 250,069,679 ee GPT

GUID Partition Table detected.

Partition Attrs Start Sector End Sector # of Sectors System /dev/sda1 2,048 69,208,063 69,206,016 Swap partition (Linux) /dev/sda2 69,208,064 136,316,927 67,108,864 Data partition (Linux) /dev/sda3 B 136,316,928 203,425,791 67,108,864 Data partition (Linux) /dev/sda4 203,425,792 250,069,646 46,643,855 Data partition (Linux)

Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set

Drive: sde _____________________________________________________________________ Disk /dev/sde: 238.5 GiB, 256060514304 bytes, 500118192 sectors Disk model: SATA SSD 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 * 1 500,118,191 500,118,191 ee GPT

GUID Partition Table detected.

Partition Attrs Start Sector End Sector # of Sectors System /dev/sde1 4,096 71,303,167 71,299,072 Swap partition (Linux) /dev/sde2 71,303,168 142,606,335 71,303,168 EFI System partition /dev/sde3 142,606,336 213,909,503 71,303,168 EFI System partition /dev/sde4 213,909,504 500,117,503 286,208,000 RAID partition (Linux) /dev/sde5 34 4,095 4,062 Data partition (Linux)

Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set

Note that I did not set up sde2 and sde3 as EFI system partitions when attempting to install there; they were originally mirrors just like sde4 and it seems that the install changed them. But I don't know how or when that happened; that's a guess.

Thanks again & HANN

:-D

With the HUGE caveat that I have not studied your long thread and only because it seems you are stuck . . . And assuming you don't care about the advantages of using GPT partitioning, would be fine with the old BIOS method, want to use RAID to mirror, AND you have a solid backup: You can use the following hack from the old days . . . (exactly how will depend on where your production data lives now or what your backup method is, but the gist is the same) . . . 1.  Break the RAID 2.  Re-partition an MBR disk 3.  Clear any grub code remnants from that disk's MBR block 4.  Copy the generic /usr/lib/boot/master-boot-code to its MBR block 5.  Set the boot flag on the boot directory partition 6.  Copy the data to the disk 7.  Do 2-5 on the other disk(s) 8.  Build the array off the first disk, depending on RAID type/nbr disks in array This approach allows the choice of mirroring a boot directory or not, having them be identical or not, booting individually or chain loading.  There are no sector pointers as ordinarily used by grub2. In my quick scan I didn't see discussion as to why you want a nested RAID setup.  Do you really need such complexity?  I variously used 0, 1, and 5 years ago - but dropped RAID given SSD performance, because there are easier ways to get redundancy, and because of the extra attention/overhead RAID can require.  On one box I have 4 instances of openSUSE on 4 disks with a mix of GPT and MBR (2 of which are "mirrored" with rsync), plus a disk with W10.  I can boot from any disk individually or chain from any one to boot any one of the others. HTH. --dg 15.2 & Plasma

On Sun, 30 Oct 2022 20:06:59 +0000, David T-G wrote:

I'd love to use GPT, because I like its flexibility, but I think I could happily live with MSDOS partitioning because I only need

   swap    previous-version    future-version    data

partitions, which fits.  [Am I right?  I don't need a dedicated /boot slice, do I?]  And I shouldn't need a backup because I'm trying to install to the new 256G sde, keeping the 128G sda around only for migration later, at which point I will replace it with another 256G drive and finish the mirroring.  I think I do want to mirror, but let's talk about that below ...

You are not limited to just four MSDOS partitions.  There may be three primary ones plus an extended partition containing multiple logical partitions. [1] [1] https://gparted.org/h2-fix-msdos-pt.php#basic-msdos -- Robert Webb

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2022-10-31 a las 20:17 -0000, David T-G escribió:

Robert et al --

...and then Robert Webb said... % On Sun, 30 Oct 2022 20:06:59 +0000, David T-G wrote: % % > I'd love to use GPT, because I like its flexibility, but I think I could % > happily live with MSDOS partitioning because I only need ... % % You are not limited to just four MSDOS partitions.  There may be three [snip]

True, and thanks for the reminder pointer. I've always hated logical partitions, though, not least because you can't boot from them; that for me is a huge reason to love GPT.

Yes you can. Right now I don't remember how, but you can. I have done it. If you need it, I'll think about it and post details. - -- Cheers, Carlos E. R. (from openSUSE 15.3 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY2AubBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVL4MAmgKlqIgE9fCdA3EAv3Uu IjsGyKBrAKCTGMyebib/TsQtYWMxQpQeRWkRaA== =LTVs -----END PGP SIGNATURE-----

On 2022-10-31 21:44, Felix Miata wrote:

David T-G composed on 2022-10-31 20:17 (UTC):

...

I've always hated logical partitions, though, not least because you can't boot from them

That's news to me. I've never installed any Linux distro on a primary partition on an MBR disk, all of which here BTW are multiboot, and they all have been booting, ever since last century sometime when I did my first Linux installation. Also, I've never purposely had a Linux bootloader in any MBR.

That said, GPT on UEFI PCs provides a vast improvement over traditional BIOS booting. Other than migrating working disks from a legacy system to a newer PC supporting UEFI, or continuing use of legacy-only PCs, there's /no/ good reason I can think of for MBR booting any more.

I just was told the other day that Intel is removing BIOS support from machines very soon, like now. I'm unsure how Intel is involved, it should be the UEFI/BIOS makers. This means not only bios booting, but all the Basic Input Output System, ie, all those interrupts used by MsDOS programs. I don't have a link, though. Just hearsay on Usenet. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

On 10/30/22 16:06, David T-G wrote:

Dennis, et al --

...and then DennisG said... % % With the HUGE caveat that I have not studied your long thread and only % because it seems you are stuck . . .

Heh. I am *so* seriously stuck. Thanks for the input!

...

long snip

I have no interest in loading lots of other candidate OSes (unles the whole "containerized" thing blows up, anyway ;-) but instead just want to be able to practice an upgrade migration on a copy ("next") while retaining the ability to go back to the old ("prev") instance.

Oh my.  I had written a rather lengthy reply but when I got to the last paragraph, I deleted it all.  Clearly I must be missing something . . . Let me get this straight:  One disk only, with one instance of openSUSE which is your production system and a second instance of openSUSE which you want to be a copy to test upgrading on?  That's the extent of it? If so, why wouldn't you just do a clean install on one partition and then make a snapshot copy on to an identical partition for testing upgrades when the time comes?  Why all the business with RAID/mirroring/containers?  Or the second disk (although having your test copy on a second disk might make this a bit easier)? If you suspect dirty bits or bad pointers for whatever reason, use dd to zero out the first 10MB on the disk, starting with the first sector.  That will clear anything in the MBR or the "bios boot" sectors (which is NOT the same as a traditional /boot partition or an efi partition) in case that space was used before for any reason. Unless you must use UEFI, which I gather from your posts you do not, then at your install (as you illustrated) create a GPT with a single root partition for your production system and another identical partition for the test copy.  There will not be a separate /boot (or /efi); the install will allocate ~8MB at the front of the disk which is not a real partition but just space to hold grub2 code because it can't fit in the MBR like the old grub.  During install enter the Boot Loader dialog, select vanilla grub2, and instruct YaST to "write to the master boot record" and turn on the "probe foreign OS" switch.  You will now have a system which will both either instance. There are a couple of additional details you would need to tend to with the above, but I won't go that far until the above sounds like what you're looking for.  Does it? --dg 15.3 & Plasma

On 11/3/22 06:51, David T-G wrote:

Dennis, et al --

...and then DennisG said... % % On 10/30/22 16:06, David T-G wrote: % % > I have no interest in loading lots of other candidate OSes (unles the % > whole "containerized" thing blows up, anyway ;-) but instead just want to % > be able to practice an upgrade migration on a copy ("next") while % > retaining the ability to go back to the old ("prev") instance. % % Oh my.  I had written a rather lengthy reply but when I got to the last % paragraph, I deleted it all.  Clearly I must be missing something . . .

Sorry for the confusion :-( I admit that I must be weird to want just SuSE on the box and have a bunch of disks in there. It's a poor man's server for home.

% % Let me get this straight:  One disk only, with one instance of openSUSE % which is your production system and a second instance of openSUSE which you % want to be a copy to test upgrading on?  That's the extent of it?

Wellll ... The original config is one swap/boot/boot/home device and everything else is data. I'd *like* a MIRRORED swap/boot/boot/home device for fault tolerance, which brings us to two disks [of interest]. But, yeah, that's pretty much it.

% % If so, why wouldn't you just do a clean install on one partition and then % make a snapshot copy on to an identical partition for testing upgrades when % the time comes?  Why all the business with RAID/mirroring/containers?  Or % the second disk (although having your test copy on a second disk might make % this a bit easier)?

The only RAID is for mirroring. I'm not doing anything with containers. Heck, I don't even know how to create and run a VM, and I've had that on my to-do list for five years and haven't had a chance to look at a single man page or HOWTO!

% % If you suspect dirty bits or bad pointers for whatever reason, use dd to % zero out the first 10MB on the disk, starting with the first sector.  That % will clear anything in the MBR or the "bios boot" sectors (which is NOT the % same as a traditional /boot partition or an efi partition) in case that % space was used before for any reason.

That sounds like a conveniently round number. I probably shouldn't try that on any of the data disks (which, of course, are recovered from other old computers) to get rid of the Win boot loader. But it does sound like a good way to make a disk unrecognizable == "fresh".

% % Unless you must use UEFI, which I gather from your posts you do not, then at

Not as far as I know ...

% your install (as you illustrated) create a GPT with a single root partition % for your production system and another identical partition for the test

Perfect. And also swap and data for the remainder, but I can't see how that should be a problem ... right?

% copy.  There will not be a separate /boot (or /efi); the install will % allocate ~8MB at the front of the disk which is not a real partition but % just space to hold grub2 code because it can't fit in the MBR like the old

Well, wait ... Maybe I'm partitioning things wrong. You can see below that I only have about 1M free, rather than 8M free, on sda (on both machines, in fact). How did I even boot on diskfarm, and how do I even boot on jpo?

% grub.  During install enter the Boot Loader dialog, select vanilla grub2, % and instruct YaST to "write to the master boot record" and turn on the % "probe foreign OS" switch.  You will now have a system which will both % either instance.

Oho! I do want "probe"? I've been turning that off because I don't want it to try to use those old Windows drives. Maybe that's part of my problem.

% % There are a couple of additional details you would need to tend to with the % above, but I won't go that far until the above sounds like what you're % looking for.  Does it?

Yes, I think so. Here's the layout on the "working" machine:

davidtg@jpo:~> sudo lsblk -a /dev/sda NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 119.2G 0 disk ..sda1 8:1 0 33G 0 part [SWAP] ..sda2 8:2 0 32G 0 part / ..sda3 8:3 0 32G 0 part ..sda4 8:4 0 22.2G 0 part /mnt/ssd

davidtg@jpo:~> sudo parted /dev/sda p free Model: ATA SAMSUNG MZ7LN128 (scsi) Disk /dev/sda: 128GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: pmbr_boot

Number Start End Size File system Name Flags 17.4kB 1049kB 1031kB Free Space 1 1049kB 35.4GB 35.4GB linux-swap(v1) jpo-swap swap 2 35.4GB 69.8GB 34.4GB xfs jposuse 3 69.8GB 104GB 34.4GB xfs jpoalt legacy_boot 4 104GB 128GB 23.9GB xfs jpo-ssd

Here's the old sda on the "broken" machine:

diskfarm:~ # lsblk -a /dev/sda NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 119.2G 0 disk ââsda1 8:1 0 33G 0 part [SWAP] ââsda2 8:2 0 32G 0 part / ââsda3 8:3 0 32G 0 part ââsda4 8:4 0 22.2G 0 part /mnt/ssd

diskfarm:~ # parted /dev/sda p free Model: ATA SanDisk SD6SB1M1 (scsi) Disk /dev/sda: 128GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: pmbr_boot

Number Start End Size File system Name Flags 17.4kB 1049kB 1031kB Free Space 1 1049kB 35.4GB 35.4GB linux-swap(v1) diskfarm-swap swap 2 35.4GB 69.8GB 34.4GB xfs diskfarmsuse 3 69.8GB 104GB 34.4GB diskfarmknop legacy_boot 4 104GB 128GB 23.9GB xfs diskfarm-ssd

Here's the new sde on the "broken" machine:

diskfarm:~ # lsblk -a /dev/sde NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sde 8:64 0 238.5G 0 disk ââsde1 8:65 0 34G 0 part â ââmd124 9:124 0 34G 0 raid1 ââsde2 8:66 0 34G 0 part â ââmd125 9:125 0 34G 0 raid1 /tmp/e2 ââsde3 8:67 0 34G 0 part â ââmd126 9:126 0 34G 0 raid1 /tmp/e3 ââsde4 8:68 0 136.5G 0 part ââmd127 9:127 0 136.4G 0 raid1 /tmp/e4

diskfarm:~ # parted /dev/sde p free Model: ATA SATA SSD (scsi) Disk /dev/sde: 256GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags:

Number Start End Size Type File system Flags 32.3kB 1049kB 1016kB Free Space 1 1049kB 36.5GB 36.5GB primary type=82 2 36.5GB 73.0GB 36.5GB primary boot, type=83 3 73.0GB 110GB 36.5GB primary type=83 4 110GB 256GB 147GB primary type=83 256GB 256GB 352kB Free Space

That's after I tried an MSDOS-MBR install, and it didn't work at all. I'm currently up and running via thumb drive -> boot linux system -> it finds sda -> ta-da, but curiously sde was not even an option. Before I go too deeply down that rabbit hole, though, yes, I think we're talking about the same very simple setup.

% % --dg % 15.3 & Plasma

Thanks again & HAND

:-D

Way, way too convoluted and complicated.  One more time (and only one) . . . First, forget about mirroring or RAID or any such thing.  Put that out of your mind for now. No offense, but my sense is that you don't have a good grasp of how booting works.  Look once again at the fdisk output you posted for /dev/sda: Device Start End Sectors Size Type /dev/sda1 2048 69208063 69206016 33G Linux swap /dev/sda2 69208064 136316927 67108864 32G Linux filesystem /dev/sda3 136316928 203425791 67108864 32G Linux filesystem /dev/sda4 203425792 250069646 46643855 22.2G Linux filesystem Note that the first partition in the table begins at sector 2048. The sectors immediately before that partition are explained here: /In the context of GPT on a BIOS-based computer, a BIOS boot partition is similar /[but not the same!]/in some respects to the EFI system partition, which is used by systems based on EFI. The EFI System partition holds a _filesystem and files_ used by the UEFI, while the BIOS boot partition is used in BIOS-based systems and accessed without a filesystem by holding _raw binary code_. /To reiterate, the boot distinction between an UEFI vs a BIOS system, is that with UEFI an/actual partition in the partition table/ is required for the efi files (and filesystem) that grub2 needs in order to boot such a system. With a BIOS type system that is not required, but instead all that is needed is simply additional/space/ to hold the grub2 raw code. The sectors preceding sda1 are for that raw code only. The term "boot partition" in a BIOS system is correct only in the sense that it is a piece or segment of the disk, a partition of this disk, if you will. But it is not a "partition" in the sense of typical partitions in the table that hold filesystems, etc.. When Linux is installed on a BIOS machine, the installer will automatically allocate the disk space needed to fit the grub2 code, beginning at the first sector. When the user/system then proceeds with building the partition table, it will place the user's first partition immediately following the spaced allocated for grub2, i.e., at sector 2048 above. So to get a working system on your /dev/sde, all that is needed is to set the BIOS to not use UEFI (which apparently you have done), instruct the installer to use grub2 (not grub2-efi), have the installer format the entire disk, and then partition however you wish. I don't recall at the moment what the default partitioning is as recommended by the installer. But probably the simplest and very common way these days would be 3 partitions, one for the entire OS (/), another for /home, and the third for swap. But you can easily have openSUSE entirely on one partition, if you wish. Or you can have a bunch more for various types of data, etc. Choosing whatever partitioning best fits your needs is beyond the scope of this message, except to say that if you want to use the "snapshot" feature where you can "roll back" the system to a prior point in time, you will need to use the btrfs filesystem. You might want to consider this given your interest in "fault tolerance" (which strictly speaking, this is not - and it is very doubtful that you would need true FT anyway). Beyond that, my advice is to keep things simple and only do what you are sure about. Including W$ - or not - in your boot configuration is a separate discussion. And the previous suggestion re zeroing out the first ~10MB was strictly in the context of being concerned that there were old bits hanging around from previous use/attempts and preparing to use the old DOS method. Disregard all that. I suggest you first focus on only getting a simple working sde, nothing more. Go thru the vanilla install per above for verification using ext4. Once you have confirmed that, you can repeat the process however once you've worked out the partitioning scheme that you actually need. That's all I got. Good luck. --dg 15.3/Plasma

Dennis, et al -- ...and then David T-G home said... % % ...and then DennisG said... % % ... % % % % So to get a working system on your /dev/sde, all that is needed is to % % set the BIOS to not use UEFI (which apparently you have done), instruct % % the installer to use grub2 (not grub2-efi), have the installer format % % the entire disk, and then partition however you wish. I don't recall at % % Ah! That's one step that I have also left out; because the installer % makes some very non-valid assumptions, I always partition before I get % in. I'll disconnect everything else in the box so that it can't get % carried away and try an install where I drive through the tool rather % than directly on the disk. [snip] I unplugged the world, leaving just the 256G SSD (now sda) and the 16G install thumb drive (now sdb). I also wiped the SSD partition table with 20M of /dev/zero for a fresh start. I let the partitioner plan its setup, with no mirroring or anything fancy; it planned a GPT table and it included an 8M sda1 as /boot along with a BtrFS / and some swap. I confirmed that the grub it selected was GRUB2 (not "with EFI"). I went back to the partitioner and deleted the /boot slice and got the usual The system might not be able to boot: A partition of type BIOS Boot Partition is needed to install the bootloader. It will not be possible to install the bootloader. error. So how can I have - GPT - non-EFI - no /boot partition under LEAP 15.2? Do I just start my first partition 8 or 10 or 64 M in from the beginning of the disk? [My running system, just like this broken one had previously, only has 1M free on its disk.] TIA again :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

Carlos, et al -- ...and then Carlos E. R. said... % On 2022-11-04 12:05, David T-G wrote: % > % > ...and then David T-G home said... % > % % > % ...and then DennisG said... % > % % % > ... % > % % % > % % So to get a working system on your /dev/sde, all that is needed is to % > % % set the BIOS to not use UEFI (which apparently you have done), instruct % > % % the installer to use grub2 (not grub2-efi), have the installer format % > % % the entire disk, and then partition however you wish. I don't recall at % > % % > % Ah! That's one step that I have also left out; because the installer % > % makes some very non-valid assumptions, I always partition before I get % > % in. I'll disconnect everything else in the box so that it can't get % > % carried away and try an install where I drive through the tool rather % > % than directly on the disk. % > [snip] % > % > I unplugged the world, leaving just the 256G SSD (now sda) and the 16G % > install thumb drive (now sdb). I also wiped the SSD partition table with % > 20M of /dev/zero for a fresh start. % > % > I let the partitioner plan its setup, with no mirroring or anything fancy; % > it planned a GPT table and it included an 8M sda1 as /boot along with a % % No. That is not /boot. I've just gone back in again, and I see that. Of course, I am still VERY confused at how this davidtg@jpo:~> sudo parted /dev/sda p free Model: ATA SAMSUNG MZ7LN128 (scsi) Disk /dev/sda: 128GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 17.4kB 1049kB 1031kB Free Space 1 1049kB 35.4GB 35.4GB linux-swap(v1) jpo-swap swap 2 35.4GB 69.8GB 34.4GB xfs jposuse 3 69.8GB 104GB 34.4GB xfs jpoalt legacy_boot 4 104GB 128GB 23.9GB xfs jpo-ssd can boot, and nobody seems to have any answers, and I'm sure not smart enough to have pulled off any magic, but at least it isn't the /boot that I [am pretty sure I] saw in other passes. % ... % > % > So how can I have % > % > - GPT % > - non-EFI % > - no /boot partition % % It is not /boot. Just let the install system put that partition, which is % not /boot, it knows it is needed and you don't. _HE_ is right. Yep. I meant to ask how I can have - GPT - non-EFI - no boot partition like I show above. [Next comes mirroring, but one step at a time...] % % You can change, if you wish, the btrfs to ext4 if you wish, xfs for /home... % that's ok. But leave that 8 M partition alone, you really need it. Yes, I've been unable to get around it on this new install. I've created sda128 in that first 8M and am now trying a basic install, having made it past the point of complaint. Stay tuned ... Thanks again & HAND/QTBD :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

Andrei, et al -- ...and then Andrei Borzenkov said... % On 05.11.2022 18:30, David T-G wrote: % > % > I've just gone back in again, and I see that. Of course, I am still VERY % > confused at how this % > % > davidtg@jpo:~> sudo parted /dev/sda p free % > Model: ATA SAMSUNG MZ7LN128 (scsi) % > Disk /dev/sda: 128GB % > Sector size (logical/physical): 512B/512B % > Partition Table: gpt % > Disk Flags: pmbr_boot % > Number Start End Size File system Name Flags % > 17.4kB 1049kB 1031kB Free Space % > 1 1049kB 35.4GB 35.4GB linux-swap(v1) jpo-swap swap % > 2 35.4GB 69.8GB 34.4GB xfs jposuse % > 3 69.8GB 104GB 34.4GB xfs jpoalt legacy_boot % > 4 104GB 128GB 23.9GB xfs jpo-ssd % > % > can boot, and nobody seems to have any answers, % % There is not enough information to provide any answer. All that is needed to Sorry about that. I had posted content before, but I agree that I didn't post it this time. % boot in this configuration is code in MBR that knows how to load next stage % code. Next stage code can be loaded from partition (unless you are using % some fancy bootloader that misuses post-MBR gap on GPT). Code in MBR could Not as far as I know ... It's just grub2, and it's just a simple single-disk installation with only 1M free at the beginning of the disk. % be grub2 or could be Syslinux gptmbr or something else. If you want the % definitive answer, you need to show bootinfoscript output. I tried susepaste again https://susepaste.org/10731681 https://susepaste.org/16799124 but can't see my results. I fear that it's still broken. I've also pasted at a few https://hastebin.com/dorajedocu.yaml https://pst.klgrth.io/paste/u7co8 https://controlc.com/08be2450 https://rentry.co/m9kfc other sites in case any of those are acceptable. I'd sure like to understand how this system boots from its little sda with no boot partition! I'm asking here because this is a LEAP system running from a pretty basic install and I didn't have to do anything crazy or detailed to make it work; it "just does". I may need to go and ask on the help-grub list despite the wealth of strong opinion available, though; if that's the case, please let me know that this well is dry. Thanks again & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

Andrei, et al -- ...and then Andrei Borzenkov said... % On 15.11.2022 21:13, David T-G wrote: % > % > ...and then Andrei Borzenkov said... % > % On 05.11.2022 18:30, David T-G wrote: % > % > % > % > I've just gone back in again, and I see that. Of course, I am still VERY % > % > confused at how this % > % > % > % > davidtg@jpo:~> sudo parted /dev/sda p free ... % > % > Partition Table: gpt % > % > Disk Flags: pmbr_boot % > % > Number Start End Size File system Name Flags % > % > 17.4kB 1049kB 1031kB Free Space ... % > % be grub2 or could be Syslinux gptmbr or something else. If you want the % > % definitive answer, you need to show bootinfoscript output. % % => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector % 105657120 of the same hard drive for core.img. core.img is at this % location and looks for (,gpt2)/boot/grub2. It also embeds following ... % Sector 105657120 is inside /dev/sda2 % % Partition Attrs Start Sector End Sector # of Sectors System % /dev/sda1 2,048 69,208,063 69,206,016 Swap partition % (Linux) % /dev/sda2 69,208,064 136,316,927 67,108,864 Data partition % (Linux) % % and /dev/sda2 seems to be your root partition % % Device Mount_Point Type Options % % ... % /dev/sda2 / xfs % (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) I follow that so far. Thanks. % % grub modules in core.img match it (grub needs gpt and xfs drivers to access % root partition to read kernel etc). % % All of this explains how does it work. But ... There is no boot partition, and everyone has been telling me that I need a boot partition on a GPT disk, so I am still quite confused as to how this can boot. I don't want to waste a boot partition and would love to know how to not have to bother with it. Something broke on diskfarm and I could never get it working again. Here I have a still-working happy system, and I'd love to understand it so that I can replicate it. Thanks again & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

On Wed, Nov 16, 2022 at 4:50 PM David T-G wrote:

But ... There is no boot partition, and everyone has been telling me that I need a boot partition on a GPT disk, so I am still quite confused as to how this can boot.

I do not know what you call a "boot partition". If you mean whatever is mounted on /boot, I fail to see how it is related to GPT. If you mean "BIOS boot partition" - it is needed if you want to install grub outside of any filesystem. During boot grub simply loads its code from absolute disk location. Whether this location is inside the BIOS boot partition or inside your / or /boot partition does not matter at this time. Installing grub in BIOS boot partition is preferred because it is easier to accidentally destroy or corrupt grub file when it is on filesystem. But technically it will work also without this partition, at least as long as filesystem supports it. E.g., grub will refuse to be installed in this mode on btrfs. Which may be one reason why installer insists on creating BIOS boot partition - because default SUSE filesystem is btrfs.

On Nov 16, 2022, at 1:47 PM, Carlos E. R. wrote:

Please stop saying that you need a "boot partition". What you need is a "BIOS boot partition". I though I had explained the differences.

As Andrei explained, it is possible to do without it, but it is more complex and has nuances, so YaST properly insists that you need a BIOS boot partition.

Perhaps calling it the “bios partition” instead of the “bios boot partition” would eliminate some of the confusion.

-- Cheers / Saludos,

Carlos E. R. (from 15.3 x86_64 at Telcontar)

kschneider bout-tyme.net composed on 2022-11-16 19:40 (UTC):

Perhaps calling it the “bios partition” instead of the “bios boot partition” would eliminate some of the confusion.

Use /boot/ for a /boot/ filesystem rather than partition. After all, it's filesystems we mount. Partitions lacking filesystems cannot be mounted. For the BIOS boot area, capitalize it to match it's being an acronym, and use a hyphen: BIOS-boot partition. It contains no filesystem. Alternatively, GPT-boot-partition. Or, GPT-legacy-boot partition. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

Hi, all -- ...and then Carlos E. R. said... % On 2022-11-05 16:30, David T-G wrote: % > ... % > can boot, and nobody seems to have any answers, and I'm sure not smart % > enough to have pulled off any magic, but at least it isn't the /boot that % > I [am pretty sure I] saw in other passes. % % It is not /boot, it is BIOS BOOT partition. % % Differences: % % /boot is formatted. BIOS BOOT is not formatted % /boot is mounted BIOS BOOT is not mounted % /boot is hundreds of MB BIOS BOOT is just 8 meg. [snip] Thanks again. Yes, I was confusing the two, and I was more confused because the system never had a boot partition before (but instead just 1M available) and still worked. But I agree that it wasn't really a distinct /boot mounted filesystem. So, confusion be damned, I bit the bullet and created an extra partition diskfarm:~ # parted /dev/sda p free ; parted /dev/sde p free Model: ATA SATA SSD (scsi) Disk /dev/sda: 256GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 128 17.4kB 8389kB 8371kB grubboot bios_grub 1 8389kB 36.5GB 36.5GB df-swap swap 2 36.5GB 73.0GB 36.5GB df-prev legacy_boot 3 73.0GB 110GB 36.5GB df-next legacy_boot 4 110GB 256GB 147GB df-ssd Model: ATA SATA SSD (scsi) Disk /dev/sde: 256GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 128 17.4kB 8389kB 8371kB grubboot bios_grub 1 8389kB 36.5GB 36.5GB linux-swap(v1) df-swap swap 2 36.5GB 73.0GB 36.5GB xfs df-prev legacy_boot 3 73.0GB 110GB 36.5GB xfs df-next legacy_boot 4 110GB 256GB 147GB xfs df-ssd diskfarm:~ # df -kh / ; grep md2 /proc/mdstat Filesystem Size Used Avail Use% Mounted on /dev/md2 34G 7.6G 27G 23% / md2 : active raid1 sda2[2] sde2[0] and was able to complete the installation, and now we're up and running. FINALLY! (I'm sure you guys are as tired of all of this as I :-) I of course had to install grub2 on both sda and sde to ensure that either would work, but we should be happy and protected. For my next adventure, we'll look at cloning onto md3 and then running a test upgrade to get current. One down, and one to go! Thanks again & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

On 2022-11-04 17:11, Felix Miata wrote:

David T-G composed on 2022-11-04 11:05 (UTC):

...

I unplugged the world, leaving just the 256G SSD (now sda) and the 16G install thumb drive (now sdb). I also wiped the SSD partition table with 20M of /dev/zero for a fresh start.

That's not a fresh start if the partition table was GPT. A GPT table is mirrored at the end of the disk. If you want a fresh start simply you use a partitioning tool to do the wiping, or create a new "table" with it, which means "tables" at both ends of the disk. If you want to wipe the hard way with dd, you must do the whole disk, or at least both ends.

But that is not an issue, YaST will create a new partition table. Wiping the whole thing with dd on a SSD is not a good think, kills lives. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

On Mon, 17 Oct 2022 21:59:48 +0000, David T-G wrote:

Felix, et al -- ...and then Felix Miata said... % [quote] [...]

% bootinfoscript output % fdisk -l % parted -l % lsblk -f % cat /etc/fstab % etc.

I can give you that sort of thing from my web server box, which is the exact same model with the exact same /dev/sda but without all of the other storage.  So let's dig in, and maybe you can figure out how grub is actually doing anything here.

So why not take diffs of each of those info outputs for the broken system against the working one?  The error should show in the difference.

[...] % Long output can be susepasted with URI thereto provided.

The problem is creating the long output; at that box I'm at a plain text console with no GUI support and no other computer nearby.  I miss serial consoles and remote access!

Does that mean you can't get any of the info from the broken system? -- Robert Webb

David T-G composed on 2022-10-28 02:15 (UTC):

So, I figure, I must be going about this the wrong way. I can't be the only stupid idiot out there who wants to mirror his boot devices, likes GPT, and expects to use GRUB2. How should I be configuring this installation to make it all Just Work again? Does anyone out there have anything comparable to share?

In case you missed it: https://forums.opensuse.org/showthread.php/533087-How-to-have-a-custom-UEFI-... -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

On 2022-10-29 04:35, David T-G wrote:

Felix, et al --

...and then Felix Miata said... % David T-G composed on 2022-10-28 02:15 (UTC): % % > So, I figure, I must be going about this the wrong way. I can't be the % > only stupid idiot out there who wants to mirror his boot devices, likes % > GPT, and expects to use GRUB2. How should I be configuring this % > installation to make it all Just Work again? Does anyone out there have % > anything comparable to share? % % In case you missed it: % https://forums.opensuse.org/showthread.php/533087-How-to-have-a-custom-UEFI-...

Thanks! That sure was a lot to read, and I'm going to have to go back to it. But ... I don't really want EFI/UEFI and so far don't know *why* I would want it. I'm quite happy with legacy mode, or at least I think I have been for years and I think I would continue to be ... As long as you are not installing Windows on the same machine, that's not a problem.

-- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)