Install followed by fresh upgrade couple days later--lost by grub/EFI boot??

English Install/Boot/Login
21

Thanks for the data . . . .

22

I don’t understand what you are doing. Would you mind booting a live system and running all of the following from a terminal window:

  • fdisk -l
  • efibootmgr -v
  • lsblk -o PATH,LABEL,UUID,FSTYPE
23

@karl:

Thanks for the reply here. I was booting from a “live” installer, then selecting the TW installation by using, “boot linux from hard drive” . . . after which it would hang in the dmesg. Then I would open a TTY shell and log into the installed TW system via TTY console . . . and I tried to run your commands, as well as other poster’s . . . and I reported them here a couple days ago.

I don’t have time to mess with this today, but I notice that the “lsblk -o NAME, xxxx” command you posted before, which was returned as error for not recognizing “NAME” . . . is now changed to “PATH” . . . ???

I believe I did run the first two commands and they showed all of the internal partitions properly, and it showed that “0000” was “opensuse tumbleweed” as the “current” boot at the time.

To understand your present question, you are asking me to boot up the uninstalled live usb flash drive system and then run your three commands. i.e., not from the installed TW system, which is now only accessible by TTY by way of booting it “from hard drive” by the “live” installer . . . ???

24

Yes. Bypass the installed system, which is broken. Boot into the live image. You will get a working Tumbleweed system. Run the 3 commands already mentioned.

Don’t tell what the commands do. Don’t edit the output. Post the command line and the complete output as follows:

erlangen:~ # fdisk -l
Disk /dev/nvme0n1: 476.96 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: Samsung SSD 950 PRO 512GB               
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: A84F222E-0177-499B-A7EA-BDA6F31E2196

Device             Start        End   Sectors  Size Type
/dev/nvme0n1p1    206848   67102719  66895872 31.9G Linux filesystem
/dev/nvme0n1p2  67102720  134207487  67104768   32G Linux filesystem
/dev/nvme0n1p3 134207488 1000214527 866007040  413G Linux filesystem
/dev/nvme0n1p4      2048     206847    204800  100M EFI System

Partition table entries are not in disk order.


Disk /dev/sda: 3.65 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EZRX-22S
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 27C8C52A-8091-403C-ADF1-E9C791667D40

Device         Start        End    Sectors  Size Type
/dev/sda1   67119104  134223871   67104768   32G Linux filesystem
/dev/sda2      16384   67119103   67102720   32G Linux filesystem
/dev/sda4  134223872 7814035455 7679811584  3.6T Linux filesystem

Partition table entries are not in disk order.


Disk /dev/sdb: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850 
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: 90C1973B-4A41-4E96-85BA-B7358EA77CCC

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048    208895    206848   101M EFI System
/dev/sdb2     208896  63119359  62910464    30G Linux filesystem
/dev/sdb3   63119360 126033919  62914560    30G Linux filesystem
/dev/sdb4  126033920 852088831 726054912 346.2G Linux filesystem
/dev/sdb5  852088832 976773119 124684288  59.5G Linux filesystem
erlangen:~ # lsblk -o PATH,LABEL,UUID,FSTYPE
PATH           LABEL          UUID                                 FSTYPE
/dev/sda                                                           
/dev/sda1      Manjaro        fad3604b-5a61-4653-8c14-518d850400ba ext4
/dev/sda2      Tumbleweed-HDD 3760cc8d-f468-4654-855b-afcd31071075 ext4
/dev/sda4      Home-HDD       f5177cae-4082-44ed-9471-b99030f06866 ext4
/dev/sdb                                                           
/dev/sdb1                     4A24-B10D                            vfat
/dev/sdb2      ArchLinux      690b51d7-7034-4585-b362-615f8056be45 ext4
/dev/sdb3      SLED           492c5d5e-5d9b-4a99-9d34-e1f9cee09fe9 ext4
/dev/sdb4      Home-SSD       f4c5463f-f43d-420a-a0ea-4456cfbc54fa ext4
/dev/sdb5      Tumbleweed     204f7d0f-979a-41e1-a483-a597d0357e0b btrfs
/dev/nvme0n1                                                       
/dev/nvme0n1p1 Fedora         047d4d83-a9a7-482e-8d15-a1c855a637ea ext4
/dev/nvme0n1p2 Tumbleweed     8b190950-c141-4351-9198-7a9592b4fb34 ext4
/dev/nvme0n1p3 Home           704621ef-9b45-4e96-ba7f-1becd3924f08 ext4
/dev/nvme0n1p4                6DEC-64F9                            vfat
erlangen:~ # efibootmgr -v
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0000,0001,0002,0003,0005,0007
Boot0000* tumbleweed-ext4       HD(4,GPT,0497bfdf-73d7-47a8-9d8e-6b911574f774,0x800,0x32000)/File(\EFI\TUMBLEWEED-EXT4\GRUBX64.EFI)
Boot0001* Fedora        HD(4,GPT,0497bfdf-73d7-47a8-9d8e-6b911574f774,0x800,0x32000)/File(\EFI\FEDORA\SHIMX64.EFI)
Boot0002* sled  HD(4,GPT,0497bfdf-73d7-47a8-9d8e-6b911574f774,0x800,0x32000)/File(\EFI\SLED\GRUBX64.EFI)
Boot0003* manjaro       HD(1,GPT,2fe6b58a-379a-4f6e-899b-8be22ef6e885,0x800,0x32800)/File(\EFI\MANJARO\GRUBX64.EFI)
Boot0005* arch  HD(1,GPT,2fe6b58a-379a-4f6e-899b-8be22ef6e885,0x800,0x32800)/File(\EFI\ARCH\GRUBX64.EFI)
Boot0006* tumbleweed-btrfs      HD(1,GPT,2fe6b58a-379a-4f6e-899b-8be22ef6e885,0x800,0x32800)/File(\EFI\TUMBLEWEED-BTRFS\GRUBX64.EFI)
Boot0007* UEFI: SanDisk Extreme 0001, Partition 2       PciRoot(0x0)/Pci(0x14,0x0)/USB(21,0)/HD(2,MBR,0x54907881,0x1bd800,0x7800)..BO
erlangen:~ #
25

@karlmistelberger:

OK, got it, yes, if I can use the live terminal app it will be easier to post the data you asked for . . . since I was trying to respond to several folks and their questions I tried to get to it via TTY and then I just copied the salient points by hand . . . . I’ll get back to it later tonight or tomorrow and post back with the outputs, pretty sure the various disks are cut up and showing up . . . question is what is happening when grub tries to boot up TW partition???

26

bootinfoscript output may answer more than just the three commands karlmistelberger requested.

27 
sudo ./bootinfoscript <outputfile>

@mrmazda:

Alrighty, in a little while I’ll boot the live system and run Karl’s suggested commands. But for this “boot info script” is that not an app that has to be installed? And would this command then be run in the installed TW system via TTY?

Or, that is something like Karl is suggesting, run from the “live” installer TW system, and therefore I could easily copy/paste the data into a post window here?? My question is specifically about the

<outputfile>
name . . . is that something that I enter, or that is the exact command, and it produces an “outputfile” . . . and then something has to be done with that file to get it out of the TTY . . . i.e., higher level of difficulty.

28

@karlm:

So the TW flash drive I have must be the “DVD installer” as it wouldn’t boot to a live session, while I was there I went to the “rescue system” and in the dmesg it said, “Failed to start login service” . . . then when it went to the “rescue login” cursor it wouldn’t accept the user name or password or any combo of “live” . . . .

So, realizing that these three commands could be run from any console in the computer, I booted up a Gecko rolling partition in the same HDD as the TW install and ran the commands. The first two seemed to work, the third command I had problems with previously when I tried it, and did so again. The TW install is in “sdb8” and grub should be in “sdb1” . . . .

nonspac@nonspac-pc:~> fdisk -l
bash: fdisk: command not found
nonspac@nonspac-pc:~> sudo fdisk -l
[sudo] password for root: 
Disk /dev/sda: 232.91 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Mercury Electra 
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: AE3BFD84-809E-4CBD-8C97-8CB91BA0822E

Device      Start       End   Sectors   Size Type
/dev/sda1      40    409639    409600   200M EFI System
/dev/sda2  409640 488397127 487987488 232.7G unknown


Disk /dev/sdb: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM010-2EP1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F1161268-E36C-44A2-B2B6-F0B1FEC1FD0A

Device          Start        End   Sectors   Size Type
/dev/sdb1          40     409639    409600   200M EFI System
/dev/sdb2      409640  491208671 490799032   234G Apple HFS/HFS+
/dev/sdb3   492478208  983267695 490789488   234G Apple HFS/HFS+
/dev/sdb4   983267696  984537231   1269536 619.9M Apple boot
/dev/sdb5   984537232 1431038951 446501720 212.9G Apple HFS/HFS+
/dev/sdb6  1431302144 1532518399 101216256  48.3G Linux filesystem
/dev/sdb7  1532518400 1634918399 102400000  48.8G Microsoft basic data
/dev/sdb8  1634918400 1737318399 102400000  48.8G Linux filesystem
/dev/sdb9  1737318400 1926143999 188825600    90G Linux filesystem
/dev/sdb10 1926144000 1953523711  27379712  13.1G Linux swap


Disk /dev/sdc: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00B
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 453477A3-2476-4320-B59A-C172BB69F019

Device          Start        End   Sectors   Size Type
/dev/sdc1          40     409639    409600   200M EFI System
/dev/sdc2      409640  585868783 585459144 279.2G Apple HFS/HFS+
/dev/sdc3   585868784  587138327   1269544 619.9M Apple boot
/dev/sdc4   587138328 1415950871 828812544 395.2G Apple HFS/HFS+
/dev/sdc5  1415952384 1513607167  97654784  46.6G Linux filesystem
/dev/sdc6  1513607168 1611263999  97656832  46.6G Linux filesystem
/dev/sdc7  1922275328 1953523711  31248384  14.9G Linux swap
/dev/sdc8  1611264000 1922275327 311011328 148.3G Linux filesystem

Partition table entries are not in disk order.




Disk /dev/sdd: 14.62 GiB, 15682240512 bytes, 30629376 sectors
Disk model: Ultra           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1b8412a2

Device     Boot Start     End Sectors  Size Id Type
/dev/sdd1        3632   11947    8316  4.1M ef EFI (FAT-12/16/32)
/dev/sdd2  *    11948 9054207 9042260  4.3G 17 Hidden HPFS/NTFS
nonspac@nonspac-pc:~> sudo efibootmgr -v
BootCurrent: 0000
BootOrder: 0003,0002,0005,0080,0006,0004,0001,0000
Boot0000* openSUSE    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\openSUSE\grubx64.efi)
Boot0001* debian    HD(1,GPT,36faabea-42fb-40d1-b88b-fb254febf542,0x28,0x64000)/File(\EFI\debian\grubx64.efi)
Boot0002* opensuse-secureboot    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
Boot0003* ubuntu    HD(1,GPT,1470d224-08ec-4863-9e67-93af726f576b,0x28,0x64000)/File(\EFI\ubuntu\shimx64.efi)
Boot0004* siduction_2018.3.0    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\siduction_2018.3.0\grubx64.efi)
Boot0005* Manjaro    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\Manjaro\grubx64.efi)
Boot0006* grub-secureboot    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\grub\shim.efi)
Boot0080* Mac OS X    PciRoot(0x0)/Pci(0x1f,0x2)/Sata(2,0,0)/HD(2,GPT,7f49ef28-6bfc-4523-a88a-1148b7b94d81,0x64028,0x1d161920)/VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,11f54d5c769a284a842102224bd2197e)/File(\3A593A60-4D5F-4C03-A546-64C44DD0FA3C\System\Library\CoreServices\boot.efi)
Boot0081* Mac OS X    PciRoot(0x0)/Pci(0x1f,0x2)/Sata(3,0,0)/HD(2,GPT,3447e9e0-204a-414f-a226-9f19fa88ef29,0x64028,0x1d40ffb8)
Boot0082*     PciRoot(0x0)/Pci(0x1f,0x2)/Sata(3,0,0)/HD(2,GPT,3447e9e0-204a-414f-a226-9f19fa88ef29,0x64028,0x1d40ffb8)
BootFFFF*     PciRoot(0x0)/Pci(0x1f,0x2)/Sata(3,0,0)/HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\BOOT\BOOTX64.efi)
nonspac@nonspac-pc:~> sudo lsblk -o PATH, LABEL, UUID, FSTYPE
lsblk: unknown column: PATH,
nonspac@nonspac-pc:~> sudo lsblk -o LABEL, UUID, FSTYPE
lsblk: unknown column: LABEL,
nonspac@nonspac-pc:~> sudo lsblk -o
lsblk: option requires an argument -- 'o'
Try 'lsblk --help' for more information.
nonspac@nonspac-pc:~> lsblk --o
lsblk: option '--o' is ambiguous; possibilities: '--output' '--output-all'
Try 'lsblk --help' for more information.
nonspac@nonspac-pc:~>
29

I gave you a link. I expected you would open it and read the description provided by its author.

And would this command then be run in the installed TW system via TTY?
It’s a script. Scripts do not need to be “installed”. If it exists on a local filesystem, it can be run. That translates to, from a terminal: 1-download it; 2-extract it; 3-run it:

> wget https://github.com/arvidjaar/bootinfoscript/archive/master.zip # or equivalent download with web browser or curl or other downloader
> unzip master.zip
> sudo sh bootinfoscript-master/bootinfoscript
# (follow its resulting instruction)

Or, that is something like Karl is suggesting, run from the “live” installer TW system, and therefore I could easily copy/paste the data into a post window here??
Something like that. When you run the script, it tells you what to do next, but you do not paste its output. It’s too big for pasting. You upload it to https://susepaste.org, or equivalent other pastebin site, and type or pasted its URL here.

My question is specifically about the name . . . is that something that I enter, or that is the exact command,
Both.

and it produces an “outputfile” . . . and then something has to be done with that file to get it out of the TTY . . . i.e., higher level of difficulty.
This is answered by previous answers and opening the URL provided to read its instructions. I guess instead of <outputfile> I should have written AnyUniqueFilenameYouCanThinkUpAndRememberAndRetypeWhenNecessary. :slight_smile:

30

You may check sdb8 as follows:

erlangen:~ # btrfs check --force /dev/sdb5
Opening filesystem to check...
WARNING: filesystem mounted, continuing because of --force
Checking filesystem on /dev/sdb5
UUID: 204f7d0f-979a-41e1-a483-a597d0357e0b
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups
found 14265012224 bytes used, no error found
total csum bytes: 11592740
total tree bytes: 760217600
total fs tree bytes: 714571776
total extent tree bytes: 30146560
btree space waste bytes: 124749311
file data blocks allocated: 145146220544
 referenced 32731504640
erlangen:~ #

You may try to repair grub: https://karlmistelberger.wordpress.com/2019/11/19/grub-efi-btrfs/ This requires a matching rescue or live system.

31

Leave out the whitespace following commas (type it as shown by karlmistelberger).

32

At the user prompt type (no password required):

karl@erlangen:~> su -
Passwort: 
erlangen:~ #
33

@mrmazda:

First thing I did this morning was to click on your link . . . but thanks for the clarifications on it . . . I’ll check into it later on.

@karlm:

OK, thanks for that, assuming I would put “–force sdb8” rather than your example. Also I am formatted “ext4” but I still would use “btrfs”??

34 
erlangen:~ # fsck -f /dev/sdb2
fsck from util-linux 2.34
e2fsck 1.45.4 (23-Sep-2019)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
ArchLinux: 178649/1966080 files (0.4% non-contiguous), 2345293/7863808 blocks
erlangen:~ #
35

???

 # lsblk -o PATH, LABEL, UUID, FSTYPE
lsblk: unknown column: PATH,

nonspac-pc:/home/nonspac # btrfs check --force /dev/sdb8
Opening filesystem to check...
No valid Btrfs found on /dev/sdb8
ERROR: cannot open file system

nonspac-pc:/home/nonspac # ext4 check --force /dev/sdb8
bash: ext4: command not found

nonspac-pc:/home/nonspac # fsck -f /dev/sdb8
fsck from util-linux 2.34
e2fsck 1.45.4 (23-Sep-2019)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
disk1s8: 255214/3203072 files (0.1% non-contiguous), 1704429/12800000 blocks
36

Sorry, seems like these posts are slipping by . . . here are all three commands run, in reverse order . . . haven’t had time to check the bootinfoscript or look at the link to repair grub . . . ran update-grub in several other systems, grub finds TW, but fails to boot it . . . I’ll look into the repair link in a minute.

nonspac@nonspac-pc:~> su
Password: 
nonspac-pc:/home/nonspac # lsblk -o PATH,LABEL,UUID,FSTYPE
PATH   LABEL                         UUID                                 FSTYPE
/dev/sda
                                                                          
/dev/sda1
       EFI                           67E3-17ED                            vfat
/dev/sda2
                                     adb56592-c260-4620-b298-be3e012b5e57 apfs
/dev/sdb
                                                                          
/dev/sdb1
       EFI                           67E3-17ED                            vfat
/dev/sdb2
       1Macinto                      632a31b3-7430-3c28-a992-c92271adfa58 hfsplu
/dev/sdb3
       2Macinto                      93f0ad8c-baed-3a31-8811-56b4a5cc6765 hfsplu
/dev/sdb4
       Recovery HD                   11b8a168-b278-3d38-8df7-daee4fec3d35 hfsplu
/dev/sdb5
       3Linux                        4bc32144-c9ad-3c87-9b64-44e2f89dd31b hfsplu
/dev/sdb6
                                     078658fb-f9ce-42e1-a2d5-05b316a268de ext4
/dev/sdb7
                                     56e0c14d-22ed-4466-b69c-2f62e5065bfc ext4
/dev/sdb8
       disk1s8                       d8c52ffb-c429-46c4-bb8f-b786ca361672 ext4
/dev/sdb9
                                     64c5dba2-bacd-4459-9904-6bda0fbe24e7 ext4
/dev/sdb10
                                     dac6d73c-5e42-47ce-af39-ba762532645d swap
/dev/sdc
                                                                          
/dev/sdc1
       EFI                           67E3-17ED                            vfat
/dev/sdc2
       MacintoUno                    8037621e-c63c-3884-bfb4-729282cf76fd hfsplu
/dev/sdc3
       Recovery HD                   15f8192a-a9d0-3409-a5b9-084fc913ca7e hfsplu
/dev/sdc4
       MacintoDos                    6073161c-00c1-3827-9f81-000472e23582 hfsplu
/dev/sdc5
                                     fb9d1360-bb56-40d0-a776-65cb2dddae70 ext4
/dev/sdc6
                                     17bcb813-d05e-4cc3-bcdf-16d283156780 ext4
/dev/sdc7
                                     f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0 swap
/dev/sdc8
                                     598d1ebe-6ad9-4491-b95a-7540208c28e3 ext4
/dev/sdd
       openSUSE-Tumbleweed-DVD-x86_6417
                                     2019-11-08-06-52-35-41               iso966
/dev/sdd1
                                     893F-2E62                            vfat
/dev/sdd2
       openSUSE-Tumbleweed-DVD-x86_6417
                                     2019-11-08-06-52-29-33               iso966
/dev/sr0
                                                                          
nonspac-pc:/home/nonspac # efibootmgr -v
BootCurrent: 0000
BootOrder: 0003,0002,0005,0080,0006,0004,0001,0000
Boot0000* openSUSE    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\openSUSE\grubx64.efi)
Boot0001* debian    HD(1,GPT,36faabea-42fb-40d1-b88b-fb254febf542,0x28,0x64000)/File(\EFI\debian\grubx64.efi)
Boot0002* opensuse-secureboot    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
Boot0003* ubuntu    HD(1,GPT,1470d224-08ec-4863-9e67-93af726f576b,0x28,0x64000)/File(\EFI\ubuntu\shimx64.efi)
Boot0004* siduction_2018.3.0    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\siduction_2018.3.0\grubx64.efi)
Boot0005* Manjaro    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\Manjaro\grubx64.efi)
Boot0006* grub-secureboot    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\grub\shim.efi)
Boot0080* Mac OS X    PciRoot(0x0)/Pci(0x1f,0x2)/Sata(2,0,0)/HD(2,GPT,7f49ef28-6bfc-4523-a88a-1148b7b94d81,0x64028,0x1d161920)/VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,11f54d5c769a284a842102224bd2197e)/File(\3A593A60-4D5F-4C03-A546-64C44DD0FA3C\System\Library\CoreServices\boot.efi)
Boot0081* Mac OS X    PciRoot(0x0)/Pci(0x1f,0x2)/Sata(3,0,0)/HD(2,GPT,3447e9e0-204a-414f-a226-9f19fa88ef29,0x64028,0x1d40ffb8)
Boot0082*     PciRoot(0x0)/Pci(0x1f,0x2)/Sata(3,0,0)/HD(2,GPT,3447e9e0-204a-414f-a226-9f19fa88ef29,0x64028,0x1d40ffb8)
BootFFFF*     PciRoot(0x0)/Pci(0x1f,0x2)/Sata(3,0,0)/HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\BOOT\BOOTX64.efi)

nonspac-pc:/home/nonspac # fdisk -l
Disk /dev/sda: 232.91 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Mercury Electra 
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: AE3BFD84-809E-4CBD-8C97-8CB91BA0822E

Device      Start       End   Sectors   Size Type
/dev/sda1      40    409639    409600   200M EFI System
/dev/sda2  409640 488397127 487987488 232.7G unknown


Disk /dev/sdb: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM010-2EP1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F1161268-E36C-44A2-B2B6-F0B1FEC1FD0A

Device          Start        End   Sectors   Size Type
/dev/sdb1          40     409639    409600   200M EFI System
/dev/sdb2      409640  491208671 490799032   234G Apple HFS/HFS+
/dev/sdb3   492478208  983267695 490789488   234G Apple HFS/HFS+
/dev/sdb4   983267696  984537231   1269536 619.9M Apple boot
/dev/sdb5   984537232 1431038951 446501720 212.9G Apple HFS/HFS+
/dev/sdb6  1431302144 1532518399 101216256  48.3G Linux filesystem
/dev/sdb7  1532518400 1634918399 102400000  48.8G Microsoft basic data
/dev/sdb8  1634918400 1737318399 102400000  48.8G Linux filesystem
/dev/sdb9  1737318400 1926143999 188825600    90G Linux filesystem
/dev/sdb10 1926144000 1953523711  27379712  13.1G Linux swap


Disk /dev/sdc: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00B
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 453477A3-2476-4320-B59A-C172BB69F019

Device          Start        End   Sectors   Size Type
/dev/sdc1          40     409639    409600   200M EFI System
/dev/sdc2      409640  585868783 585459144 279.2G Apple HFS/HFS+
/dev/sdc3   585868784  587138327   1269544 619.9M Apple boot
/dev/sdc4   587138328 1415950871 828812544 395.2G Apple HFS/HFS+
/dev/sdc5  1415952384 1513607167  97654784  46.6G Linux filesystem
/dev/sdc6  1513607168 1611263999  97656832  46.6G Linux filesystem
/dev/sdc7  1922275328 1953523711  31248384  14.9G Linux swap
/dev/sdc8  1611264000 1922275327 311011328 148.3G Linux filesystem

Partition table entries are not in disk order.




Disk /dev/sdd: 14.62 GiB, 15682240512 bytes, 30629376 sectors
Disk model: Ultra           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1b8412a2

Device     Boot Start     End Sectors  Size Id Type
/dev/sdd1        3632   11947    8316  4.1M ef EFI (FAT-12/16/32)
/dev/sdd2  *    11948 9054207 9042260  4.3G 17 Hidden HPFS/NTFS
nonspac-pc:/home/nonspac #
37

(It wouldn’t let me delete response mooted by an intervening response.)

38

@karlm, et al:

So I looked at this linked page, right now “rescue” isn’t accepting any log in names or passwords . . . can I not run these commands in another linux system, as long as it isn’t the TW installed system?

But, grub2 is installed, and grub2 shows all of the presently installed options, and it boots all of the other options except for the TW system . . . if I wanted to “cat” something from grub2 that might be diagnostic, what would that be?

I’m following mrmazda’s thought that something in the suse installer is being “dropped” when dealing with mac computers as far as either “booting” or via some script in the specific grub data for TW . . . but how to check that? I have run “update-grub” numerous times from the ubuntu installs, hasn’t repaired the TW “crash” issue, and in the second “upgrade” from the 11/7 snapshot I saw it run, “installing grub” and “installing bootloader” toward the end of the upgrade . . . but somehow that isn’t getting the system to boot . . . ??

I haven’t done a lot of “chrooting” . . . but is this something that can be done on “adjacent” installed system, or must be done from ext drive booted up in live, and then if so, does that “live” system have to be “tumbleweed”?? I think I have a Manjaro live flash drive if it has to be done “externally”??

39

@mrmazda:

Thanks for helping out, I think I got that data right and posted up . . . .

40

You got lots of disks, systems and hence grubs. As I understand:

  • Tumbleweed system sits on sdb8. The file system is clean.
  • Tumbleweed grub sits on sdb1. It does not work.

Don’t refer to the other systems, their grubs and their menu entries. You need to fix Tumbleweed’s grub on sdb1 . For doing so you might try to repair grub as follows: