Boot failure, BTFS and xfs, kde

English Install/Boot/Login
1

Main linux system: shared motherboard with separated hard drives. Only one hard drive is switched on at time. Has worked successfully for many opensuse installs. With one exception, when both are switched on, I boot to linux and virus scan the mswin system. MSWIN’s system boot is working.

After opensuse leap 43.3 had a boot failure, I installed opensuse leap 15 and restore from backup. I booted linux and it worked fine. I rebooted to an ‘upgrade install’ and let that complete. It worked. I use ‘upgrade installed’ since it it runs faster and I don’t have to reboot again and again.

I installed the nvidia drivers. Rebooted and opensuse leap 15 worked fine. Installed the mp4 codecs. Rebooted and linux system and it fails to boot with “crash dump” shown. I tried using upgrade install, no effect. BTRFS and XFS file system errors.

Need help, if possible, how do I fix this. This is 4 failures with opensuse leap 43.3 and 1 failure with opensuse leap 15,

2

a) such version does not exist
b) your post is marked with “Leap 15”, what “Leap 43” has to do with it?

it fails to boot with “crash dump” shown.

Shown where exactly?

3

Clear as mud. “Only one at a time”, then “when both”. Exactly how are you making this “switch”, and why?

MSWIN’s system boot is working.
Which Windows version?

After opensuse leap 43.3 had a boot failure, I installed opensuse leap 15 and restore from backup.
Failed exactly how? Why did you choose this point in time to upgrade? Did you upgrade the existing installation, or install from scratch? Did the new installation create all new partitions? Reformat and use old partitions? With how many disks “switched on”? Restored exactly what from backup?

I booted linux and it worked fine.
Booted what Linux? Why?

I rebooted to an ‘upgrade install’ and let that complete.
Right after you had Linux working fine you upgraded? To what? Why? With how many disks “switched on”?

It worked. I use ‘upgrade installed’ since it it runs faster
Faster than what? How do you know it’s faster?

and I don’t have to reboot again and again.
Why do you keep having to reboot?

I installed the nvidia drivers. Rebooted and opensuse leap 15 worked fine. Installed the mp4 codecs. Rebooted
Rebooted why? When, right after installing drivers? Did you use any applications that use those codecs before you rebooted? With how many disks “switched on”?

and linux system and it fails to boot with “crash dump” shown.
Rebooted how, with only one disk “switched on”, or with more than one?

I tried using upgrade install, no effect. BTRFS and XFS file system errors.
Did you run filesystem checks after the crash dump? Do you really expect an upgrade install to fix a broken installation that still has unsupported software installed (NVidia drivers)? Upgrades should be preceded by removing unsupported software first.

Need help, if possible, how do I fix this. This is 4 failures with opensuse leap 43.3 and 1 failure with opensuse leap 15,
Whatever is causing you to choose to “upgrade” needs to be determined, and fixed. Most people don’t reinstall Linux when something goes wrong. That’s what Windows users do. The cause of failure needs to be found and fixed.

Your description is sketchy, lacking details to help us help you. At this point you should gather some information to share if you want useful help. Start by running GitHub - arvidjaar/bootinfoscript with all disks “switched on”. Also from any kind of Linux boot, gather the output from hwinfo, lspci and/or inxi commands so we have some idea of what hardware you are using.

4

Maybe some reading here http://www.catb.org/~esr/faqs/smart-questions.html might help also.

5

My special setup:

A few years ago, I had system with shared harddrive for opensuse and mswin. It worked well.

When you boot to mswin, a security issue comes up. mswin, using some software, can read a linux directory, This makes a security a hole for dual boot single drive system, a drive not encrypted. I decided on putting one hard drive to mwin. The other to opensuse. This created various booting issues.

I found a hardware solution. A friend wired a power switch on the power cable. (details left out). I called the msi motherboard tech support. I explained the wiring setup. 'It’s safe as long the computer is powered down. Case power cable still plugged into socket and case power switch on is safe.

sata1 power cable<----------------------switch---------------------------- >harddrive (on off)
sata2 power cable<----------------------switch---------------------------- >harddrive (off on)

Trial and error got the wiring switch setup working for the bios system.

This setup has two separate drives sharing a motherboard, but not data between them. It’s worked for many years. Opensuse handles the setup and boots normally. MSWIN now and then fails on boot then works. It’s assures a virus on either system doesn’t affect the other.

Sata1 linux - on
Sata2 mswin - on

press key for boot menu then boot to linux, else mswin will boot. Then I can use scanvirus to scan the mswin system.

If that’s not clearly explained, ask questions.

6

‘Opensuse Leap 43.2’(version before leap 15) had BTRFS partition corruption, boot failure. 4 full opensuse 42.3
‘Opensuse Leap 15’ BTRFS and XFS partition corruption, boot failure.

If I boot to ‘opensuse leap 15’, current main linux setup, the screen shows ‘crash dump’ in the last text screen. The keyboard will not respond.

7

Opensuse Leap 15 DVD boot (‘opensuse leap 15’ installed - hard drive sata power on only)

If you do a full install, erasing all partitions, proceed with entering user data and admin passwords with internet connection present. Then proceed with the install until it reboots(‘rebooting’ [ok]). Then opensuse leap dvd shows ‘boot to hard drive’ and you click on it. Opensuse leap boots successfully to the desktop.

>Faster than what? How do you know it’s faster?

An educated guess. Downloads and install time appear to be faster in an upgrade install.

Proceeding from above, system updates appear, 100+. I then reboot opensuse and wait for the dvd menu to come up. I select from the ‘opensuse leap 15’ dvd menu ‘upgrade install’. The follow the steps in sequence until the ‘upgrade’ installs all new updates. I wait for ‘reboot’ [ok]. Then click and wait for the boot to complete to desktop.

>Why do you keep having to reboot?

Wait for ‘opensuse leap 15’ to finish boot to desktop. I wait for ‘system updates’(system tray) to complete. ‘System updates’ now shows ‘no new updates’.

https://en.opensuse.org/SDB:NVIDIA_drivers

I use manual install. (Note, the text has errors.) So, I enter this in superuser mode.

Zypper

openSUSE Leap

zypper addrepo --refresh Index of /opensuse/leap/15.0 NVIDIA

zypper inr -r NVIDIA - this line doesn’t work. So, I skip to next line.

or

zypper in <x11-video-nvidiaG02 or x11-video-nvidiaG03 or x11-video-nvidiaG04>

Following those steps. I reboot to startup the nvidia driver. It works. I am able to access the nvidia graphics xserver menu.

>Did you use any applications that use those codecs before you rebooted?
>Do you really expect an upgrade install to fix a broken installation that still has unsupported software installed (NVidia drivers)? Upgrades should be preceded by removing unsupported software first.

After rebooting with the nvidia driver installed, I use the manual process for installing codecs. (MP4, DVD)

http://opensuse-guide.org/codecs.php

Enter in superuser mode. Usually successful. I can now play dvd and play mp4 videos with VLC.

>Did you run filesystem checks after the crash dump?

Running out of time this session. Will answer next time.

>Whatever is causing you to choose to “upgrade” needs to be determined, and fixed. Most people don’t reinstall Linux when something goes wrong. That’s what Windows users do. The cause of failure needs to be found and fixed.

As shown above the ‘upgrade install’ dvd trick works, I don’t think it’s the problem. Some time ago, I sent my motherboard to msi and received a ‘used’ refurbished fixed motherboard. These boot failures started at about the same time. The mag hard drive is also at least 5 years old.

>Your description is sketchy, lacking details to help us help you. At this point you should gather some information to share if you want useful help. Start by running GitHub - arvidjaar/bootinfoscript with all disks “switched on”. Also from any kind of Linux boot, gather the output from hwinfo, lspci and/or inxi commands so we have some idea of what hardware you are using.[/QUOTE]

This a complex and long process to explain in clear language every step I take. This message took 45 mins+ to write.

Will report on the remaining items soon as possible.

tail -n 100 /var/log/dmesg.log

hwinfo, lspci and/or inxi

8

I have all the data requested, I’m not going to post my hardware info publicly. I will private mail an admin on this post for security reasons,

Using the latest “gparted live dvd” from ‘https://gparted.org/’, I did a right-click ‘check’. Attempt to fix partitions BTRFS and XFS. Both were unable to complete. Text file error output.

GParted 0.32.0 --enable-online-resize
Libparted 3.2

Check and repair file system (btrfs) on /dev/sda2 00:00:14 ( ERROR )

[TR]
[TD=“colspan: 2”] calibrate /dev/sda2 00:00:01 ( SUCCESS ) |
| | [TABLE]
[TR]
[TD=“colspan: 2”] path: /dev/sda2 (partition)
start: 18432
end: 83904511
size: 83886080 (40.00 GiB) |

[/TD]
[/TR]
[/TABLE]

check file system on /dev/sda2 for errors and (if possible) fix them 00:00:13 ( ERROR )

[TR]
[TD=“colspan: 2”] btrfsck '/dev/sda2’ 00:00:13 ( ERROR ) |
| | [TABLE]
[TR]
[TD=“colspan: 2”] *Checking filesystem on /dev/sda2
UUID: d0264c53-43fb-4e23-b566-53fc59dae8e7

  • |

| *parent transid verify failed on 679084032 wanted 762 found 348
|
parent transid verify failed on 679084032 wanted 762 found 348
parent transid verify failed on 679084032 wanted 762 found 348
parent transid verify failed on 679084032 wanted 762 found 348
Ignoring transid failure
parent transid verify failed on 695468032 wanted 764 found 354
parent transid verify failed on 695468032 wanted 764 found 354
parent transid verify failed on 696205312 wanted 764 found 354
parent transid verify failed on 696205312 wanted 764 found 354
parent transid verify failed on 696352768 wanted 764 found 354
parent transid verify failed on 696352768 wanted 764 found 354
parent transid verify failed on 696483840 wanted 764 found 354
parent transid verify failed on 696483840 wanted 764 found 354
parent transid verify failed on 696516608 wanted 764 found 354
parent transid verify failed on 696516608 wanted 764 found 354
parent transid verify failed on 696532992 wanted 764 found 354
parent transid verify failed on 696532992 wanted 764 found 354
parent transid verify failed on 696549376 wanted 764 found 354
parent transid verify failed on 696549376 wanted 764 found 354
parent transid verify failed on 681508864 wanted 764 found 762
parent transid verify failed on 681508864 wanted 764 found 762
parent transid verify failed on 683376640 wanted 764 found 351
parent transid verify failed on 683376640 wanted 764 found 351
parent transid verify failed on 683393024 wanted 764 found 351
parent transid verify failed on 683393024 wanted 764 found 351
parent transid verify failed on 683474944 wanted 764 found 351
parent transid verify failed on 683474944 wanted 764 found 351
parent transid verify failed on 681541632 wanted 764 found 762
parent transid verify failed on 681541632 wanted 764 found 762
parent transid verify failed on 683507712 wanted 764 found 354
parent transid verify failed on 683507712 wanted 764 found 354
parent transid verify failed on 696631296 wanted 764 found 354
parent transid verify failed on 696631296 wanted 764 found 354
parent transid verify failed on 683524096 wanted 764 found 351
parent transid verify failed on 683524096 wanted 764 found 351
parent transid verify failed on 683540480 wanted 764 found 353
parent transid verify failed on 683540480 wanted 764 found 353
parent transid verify failed on 679870464 wanted 762 found 354
parent transid verify failed on 679870464 wanted 762 found 354
parent transid verify failed on 679870464 wanted 762 found 354
parent transid verify failed on 679870464 wanted 762 found 354
Ignoring transid failure
parent transid verify failed on 696647680 wanted 764 found 354
parent transid verify failed on 696647680 wanted 764 found 354
parent transid verify failed on 696745984 wanted 764 found 354
parent transid verify failed on 696745984 wanted 764 found 354
parent transid verify failed on 696778752 wanted 764 found 354
parent transid verify failed on 696778752 wanted 764 found 354
parent transid verify failed on 696844288 wanted 764 found 354
parent transid verify failed on 696844288 wanted 764 found 354
parent transid verify failed on 696893440 wanted 764 found 354
parent transid verify failed on 696893440 wanted 764 found 354
parent transid verify failed on 696926208 wanted 764 found 354
parent transid verify failed on 696926208 wanted 764 found 354
parent transid verify failed on 696958976 wanted 764 found 354
parent transid verify failed on 696958976 wanted 764 found 354
parent transid verify failed on 697057280 wanted 764 found 354
parent transid verify failed on 697057280 wanted 764 found 354
parent transid verify failed on 697040896 wanted 764 found 354
parent transid verify failed on 697040896 wanted 764 found 354
parent transid verify failed on 697073664 wanted 764 found 354
parent transid verify failed on 697073664 wanted 764 found 354
parent transid verify failed on 683720704 wanted 764 found 354
parent transid verify failed on 683720704 wanted 764 found 354
parent transid verify failed on 681623552 wanted 764 found 762
parent transid verify failed on 681623552 wanted 764 found 762
parent transid verify failed on 681672704 wanted 764 found 762
parent transid verify failed on 681672704 wanted 764 found 762
parent transid verify failed on 681689088 wanted 764 found 762
parent transid verify failed on 681689088 wanted 764 found 762
parent transid verify failed on 697188352 wanted 764 found 354
parent transid verify failed on 697188352 wanted 764 found 354
parent transid verify failed on 681705472 wanted 764 found 762
parent transid verify failed on 681705472 wanted 764 found 762
parent transid verify failed on 681721856 wanted 764 found 762
parent transid verify failed on 681721856 wanted 764 found 762
parent transid verify failed on 681738240 wanted 764 found 762
parent transid verify failed on 681738240 wanted 764 found 762
parent transid verify failed on 697303040 wanted 764 found 354
parent transid verify failed on 697303040 wanted 764 found 354
parent transid verify failed on 681754624 wanted 764 found 762
parent transid verify failed on 681754624 wanted 764 found 762
parent transid verify failed on 681771008 wanted 764 found 762
parent transid verify failed on 681771008 wanted 764 found 762
parent transid verify failed on 697417728 wanted 764 found 354
parent transid verify failed on 697417728 wanted 764 found 354
parent transid verify failed on 697434112 wanted 764 found 354
parent transid verify failed on 697434112 wanted 764 found 354
parent transid verify failed on 684179456 wanted 764 found 762
parent transid verify failed on 684179456 wanted 764 found 762
parent transid verify failed on 684195840 wanted 764 found 762
parent transid verify failed on 684195840 wanted 764 found 762
parent transid verify failed on 684212224 wanted 764 found 762
parent transid verify failed on 684212224 wanted 764 found 762
parent transid verify failed on 681803776 wanted 764 found 762
parent transid verify failed on 681803776 wanted 764 found 762
parent transid verify failed on 681836544 wanted 764 found 762
parent transid verify failed on 681836544 wanted 764 found 762
parent transid verify failed on 684244992 wanted 764 found 762
parent transid verify failed on 684244992 wanted 764 found 762
parent transid verify failed on 681902080 wanted 764 found 762
parent transid verify failed on 681902080 wanted 764 found 762
parent transid verify failed on 681918464 wanted 764 found 762
parent transid verify failed on 681918464 wanted 764 found 762
parent transid verify failed on 684294144 wanted 764 found 762
parent transid verify failed on 684294144 wanted 764 found 762
parent transid verify failed on 684441600 wanted 764 found 762
parent transid verify failed on 684441600 wanted 764 found 762
parent transid verify failed on 684670976 wanted 764 found 762
parent transid verify failed on 684670976 wanted 764 found 762
parent transid verify failed on 684736512 wanted 764 found 762
parent transid verify failed on 684736512 wanted 764 found 762
parent transid verify failed on 684769280 wanted 764 found 762
parent transid verify failed on 684769280 wanted 764 found 762
parent transid verify failed on 682000384 wanted 764 found 762
parent transid verify failed on 682000384 wanted 764 found 762
parent transid verify failed on 690077696 wanted 764 found 762
parent transid verify failed on 690077696 wanted 764 found 762
parent transid verify failed on 690094080 wanted 764 found 762
parent transid verify failed on 690094080 wanted 764 found 762
parent transid verify failed on 682016768 wanted 764 found 762
parent transid verify failed on 682016768 wanted 764 found 762
parent transid verify failed on 690110464 wanted 764 found 762
parent transid verify failed on 690110464 wanted 764 found 762
parent transid verify failed on 690339840 wanted 764 found 762
parent transid verify failed on 690339840 wanted 764 found 762
parent transid verify failed on 683261952 wanted 762 found 353
parent transid verify failed on 683261952 wanted 762 found 353
parent transid verify failed on 683261952 wanted 762 found 353
parent transid verify failed on 683261952 wanted 762 found 353
Ignoring transid failure
ERROR: child eb corrupted: parent bytenr=744292352 item=207 parent level=1 child level=1
ERROR: failed to repair root items: Input/output error

  • |

[/TD]
[/TR]
[/TABLE]
[/TD]
[/TR]
[/TABLE]
[/TD]
[/TR]
[/TABLE]

GParted 0.32.0 --enable-online-resize
Libparted 3.2

Check and repair file system (xfs) on /dev/sda3 00:00:04 ( ERROR )

[TR]
[TD=“colspan: 2”] calibrate /dev/sda3 00:00:01 ( SUCCESS ) |
| | [TABLE]
[TR]
[TD=“colspan: 2”] path: /dev/sda3 (partition)
start: 83904512
end: 1887760383
size: 1803855872 (860.15 GiB) |

[/TD]
[/TR]
[/TABLE]

check file system on /dev/sda3 for errors and (if possible) fix them 00:00:03 ( ERROR )

[TR]
[TD=“colspan: 2”] xfs_repair -v '/dev/sda3’ 00:00:03 ( ERROR ) |
| | [TABLE]
[TR]
[TD=“colspan: 2”]
|

| *Phase 1 - find and verify superblock…
|
- block cache size set to 1531760 entries
Phase 2 - using internal log
- zero log…
xfs_repair: read failed: Input/output error
empty log check failed
zero_log: cannot find log head/tail (xlog_find_tail=-5)
ERROR: The log head and/or tail cannot be discovered. Attempt to mount the
filesystem to replay the log or use the -L option to destroy the log and
attempt a repair.

  • |

[/TD]
[/TR]
[/TABLE]
[/TD]
[/TR]
[/TABLE]
[/TD]
[/TR]
[/TABLE]

9

All these command were performed with only linux harddrive on (win10 power off, opensuse power on)

hwinfo.txt command output of ‘#hwinfo’

lspci.txt command output of ‘#lspci’

bootinfo.txt results of ‘#bootinfoscript’

Available for private mail to admins. For security reasons, i’m not posting hardware info publicly.

LV>it fails to boot with “crash dump” shown
arvidjaar>Shown where exactly?

press power switch
grub loading screen
click on opensuse (first line)
boot completes
screen text and keyboard frozen.

I see text on screen like ‘crash dump’. Keyboard is frozen so I can’t capture any text.

10

Not sure why you thing the type of hardware is a security breach but ok…

Looks to me like a seriously corrupt file system. Check the drive.

11

The system won’t boot at all. The monitor light changed color briefly (red → blue). Then turned back to red. It doesn’t even show the bios screen.

The original msi was showing blue scan lines on the bios flash screen. Soon after, it failed. I sent the motherboard back to about < 1 year ago. I got back a “refurbished” motherboard. Fixed motherboard. The replacement motherboard was at least about 3.5 years old. It was showing some of the same blue lines before it failed.

I did check all the motherboard connections. I replaced the video card with one I know works. No successful boot. Yes, all these action with the power off and unplugged.

I’m having it checked by a professional soon. We came to the same conclusion over the phone. The motherboard is “dead as door-nail”, “a rotting corpse”. It’s unlikely that they will get the msi motherboard working. :frowning:

So, thanks for everyone’s help.

Just one last question. Are these motherboard opensuse 15 compatible?

https://www.amazon.com/Gigabyte-6Gbps-Socket-Motherboards-GA-970A-DS3P/dp/B00CX4MUCC/ref=sr_1_1?s=pc&ie=UTF8&qid=1539064716&sr=1-1&keywords=am3%2B+sata+3+ddr3

(continued)

12

https://www.amazon.com/Gigabyte-4xDDR3-Realtek-4xUSB3-1-Motherboard/dp/B079GRXBDJ/ref=sr_1_1?s=pc&ie=UTF8&qid=1539067383&sr=1-1&keywords=motherboards&refinements=p_n_feature_seven_browse-bin%3A5657494011

13

Those were the gparted reports (latest version) after failing the fix the hard drive. I am 99% sure that the cause was the failing motherboard.

Being paranoid about computer security. That’s a good thing. :wink:

14

I’m getting off topic. Thanks to all for the help.