Page 3 of 15 FirstFirst 1234513 ... LastLast
Results 21 to 30 of 144

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

  1. #21

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

    Thanks for the data . . . .

  2. #22
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,122

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

    Quote Originally Posted by non_space View Post
    et al:

    Got back to the TTY and ran as many of the commands as I could, some of them "worked" . . . some didn't, again, hard to get that data posted over here . . . after I ran those commands I ran another zypper ref && dup . . . supposedly "9.2 MB" to download and install, got to package #4 "openSUSE-release-20191112-314.1x86_64.rpm" . . . and it stalled . . . walked away for a few minutes and when I came back it was still hanging there. Tried to ctrl-x out of it, but TTY1 didn't respond, went to TTY2 and tried the same command, but it was "locked" by zypper, so I just rebooted out of it and into another recently installed linux system that is working just fine.



    Yes, all are UEFI. "/etc/fstab" showed "swap, /, /home, and /boot/efi" as I had it set in the installer. I believe the "efibootmgr" shows /boot/efi as "UUID=67E3-17ED" and "parted -l outputs" shows all three disks with flash drive and all of the internal partitions, including efi, etc.



    I tried this adding the 3 and it still went to the "efi not found, hit any key to continue, and then went to the command line showing "panic" and "dump trace" rebooting in 90 seconds.



    This command brought back "unknown column, NAME" when I tried to put "NAME, PARTUUID, FSTYPE" and then also didn't work when I tried just "lsblk -o"



    I changed the numbers to what was showing on the TW line, output, it showed the other options as well . . .


    I believe I copied the "opensuse" lines out of that data.



    Running this command just brought a boot cursor, no data found or shown on it.
    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
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  3. #23

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

    Quote Originally Posted by karlmistelberger View Post
    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
    @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 . . . ??????

  4. #24
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,122

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

    Quote Originally Posted by non_space View Post
    @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 . . . ??????
    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:

    Code:
    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:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  5. #25

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

    Quote Originally Posted by karlmistelberger View Post
    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:
    @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???

  6. #26
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,835

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

    Quote Originally Posted by non_space View Post
    question is what is happening when grub tries to boot up TW partition???
    bootinfoscript output may answer more than just the three commands karlmistelberger requested.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  7. #27

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

    Quote Originally Posted by mrmazda View Post
    bootinfoscript output may answer more than just the three commands karlmistelberger requested.
    Code:
    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.

  8. #28

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

    Quote Originally Posted by karlmistelberger View Post
    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
    @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" . . . .

    Code:
    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:~>

  9. #29
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,835

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

    Quote Originally Posted by non_space View Post
    Code:
    sudo ./bootinfoscript <outputfile>
    But for this "boot info script" is that not an app that has to be installed?
    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:
    Code:
    > 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.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  10. #30
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,122

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

    Quote Originally Posted by non_space View Post
    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" . . . .
    You may check sdb8 as follows:

    Code:
    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.c...rub-efi-btrfs/ This requires a matching rescue or live system.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

Page 3 of 15 FirstFirst 1234513 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •