Failed to mount /sysroot

jurombo · July 8, 2025, 2:10am

athW15:/home/ju.rom.bo # journalctl -b0  _KERNEL_SUBSYSTEM=scsi -g sda
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] 4096-byte physical blocks
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Write Protect is off
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't su>
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Attached SCSI disk
Jul 08 03:57:47 MathW15.hit.ac.zw kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Jul 08 03:57:53 MathW15.hit.ac.zw kernel: sd 4:0:0:0: [sda] Starting disk

There two TW installation one on /dev/sda5 and another on /dev/sdb.

jurombo · July 8, 2025, 2:11am

athW15:/home/ju.rom.bo # journalctl -b0  _KERNEL_SUBSYSTEM=scsi -g sda
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] 4096-byte physical blocks
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Write Protect is off
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't su>
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Jul 07 22:36:27 localhost kernel: sd 4:0:0:0: [sda] Attached SCSI disk
Jul 08 03:57:47 MathW15.hit.ac.zw kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Jul 08 03:57:53 MathW15.hit.ac.zw kernel: sd 4:0:0:0: [sda] Starting disk

karlmistelberger · July 8, 2025, 5:58am

There is no problem with dev/sda. However the running system is shaky. Show the mounts:

erlangen:~ # findmnt --real 
TARGET                   SOURCE                                      FSTYPE OPTIONS
/                        /dev/nvme0n1p2[/@/.snapshots/3979/snapshot] btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=7092,subvol=/@/.snapshots/3979/snapshot
├─/.snapshots            /dev/nvme0n1p2[/@/.snapshots]               btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=265,subvol=/@/.snapshots
├─/boot/grub2/i386-pc    /dev/nvme0n1p2[/@/boot/grub2/i386-pc]       btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=264,subvol=/@/boot/grub2/i386-pc
├─/boot/grub2/x86_64-efi /dev/nvme0n1p2[/@/boot/grub2/x86_64-efi]    btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=263,subvol=/@/boot/grub2/x86_64-efi
├─/home                  /dev/nvme0n1p2[/@/home]                     btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=262,subvol=/@/home
├─/opt                   /dev/nvme0n1p2[/@/opt]                      btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=261,subvol=/@/opt
├─/root                  /dev/nvme0n1p2[/@/root]                     btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=260,subvol=/@/root
├─/srv                   /dev/nvme0n1p2[/@/srv]                      btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=259,subvol=/@/srv
├─/usr/local             /dev/nvme0n1p2[/@/usr/local]                btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=258,subvol=/@/usr/local
├─/var                   /dev/nvme0n1p2[/@/var]                      btrfs  rw,relatime,ssd,discard=async,nospace_cache,subvolid=257,subvol=/@/var
├─/boot/efi              /dev/nvme0n1p1                              vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
└─/home_SSD              /dev/sda1                                   btrfs  rw,relatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/
erlangen:~ #

hcvv · July 8, 2025, 7:14am

There may be a language barrier or some other peoblem but I really do not get this.

├─sda5 btrfs                                                  e02b8b6c-d435-4006-a77b-fb5b836e801c

/dev/sda5 is a partition and it hosts a btrfs file system. How can you use this in a Windows system?

arvidjaar · July 8, 2025, 7:43am

If you can still reproduce it, run

strace -f -o /tmp/mount.strace mount -t btrfs /dev/sda5 /mnt

and upload the file /tmp/mount.strace to the https://paste.opensuse.org/

cakeisamadeupdrug · July 9, 2025, 12:59am

Huh. This may be unrelated, but I had this issue last week. I booted into a kubuntu live disk and it could only mount one of my two btrfs filesystems (I have one for SSDs with OS and applications, and one for HDDs with documents and music etc. The kubuntu live disk could only access the HDD filesystem). btrfs check didn’t reveal any issues with any of my drives, and neither did SMART. It happened the day after I backed up so I reformatted and reinstalled. We’ll see if it happens again.

jurombo · July 9, 2025, 9:52am

The linux system on /dev/sda5 is on dual boot with Windows. They are on the same HDD.

hcvv · July 9, 2025, 10:12am

You probably mean that /dev/sda contains a Windows and an openSUSE system, though on different partitions and not both on /dev/sda5.

You really make it difficult for, at least me, to understand your environment. I do not even understand what your topic title “Failed to mount /sysroot” means. Most systems have no directory /sysroot, let alone as a mount point.
And you do never mention /sysroot anywhere in your posts above. So what is wrong there???

karlmistelberger · July 9, 2025, 10:33am

Infamous Host Erlangen has it:

erlangen:~ # journalctl -b -u '*mount' -g sysroot
Jul 07 20:26:31 erlangen systemd[1]: Mounting /sysroot...
Jul 07 20:26:31 erlangen systemd[1]: Mounted /sysroot.
erlangen:~ #

hcvv · July 9, 2025, 10:52am

And is that that maximum amount of explanation you can provide?

I do have the same as you

boven:~ # journalctl -b -u '*mount' -g sysroot
Jul 09 07:47:24 boven systemd[1]: Mounting /sysroot...
Jul 09 07:47:24 boven systemd[1]: Mounted /sysroot.
boven:~ #

But I do not have the directory

henk@boven:~> ls -la /sysroot
ls: cannot access '/sysroot': No such file or directory
henk@boven:~>

Nor is it in the list of mounts:

boven:~ # mount | grep sysroot
boven:~ #

karlmistelberger · July 9, 2025, 10:57am

https://www.google.com/search?client=firefox-b-d&q=linux+mounting+%2Fsysroot

jurombo · July 19, 2025, 6:09am

I backed up the partition on another drive dd if=/dev/sda5 of /devsdb2 and still the partition and the backups are not mounting.

The message is that system is busy and points to BUS Connection failure.

How do you fix a BUS connection error, if the error is coming a possible a bad shutdown.

arvidjaar · July 19, 2025, 11:58am

Do what you did to get this failure and copy-paste the complete commands with their full output, not your interpretation of it. After that upload the full output of

dmesg

to the https://paste.opensuse.org/

myswtest · July 19, 2025, 12:59pm

@jurombo …

In Post #1, we see this:

Math:~ # some-command [ such as: mount ... ]

Then from Post #3 and on, we see

MathW15:/home/ju.rom.bo # some-command [ such as: fdisk -l ]

Let’s disregard the command executed, and focus on the machine-name. I’m curious:

what is “Math”?? (yes, I assume machine-name).
Is that a Live/Rescue FlashDrive?? A Linux install on another drive?
what is “MathW15”?? Is that really a different machine than “Math”??
Is that another / different Live/Rescue FlashDrive?? Another Linux install on another drive?

mrmazda · July 20, 2025, 3:46am

# inxi -S
System:
  Host: ab250 Kernel: 6.12.38-1-longterm arch: x86_64 bits: 64
  Console: pty pts/0 Distro: openSUSE Tumbleweed 20250718
# ls -gGh /sysr*
ls: cannot access '/sysr*': No such file or directory
# journalctl -b | grep sroot
Jul 19 18:22:55 ab250 systemd[1]: Mounting /sysroot...
Jul 19 18:22:55 ab250 systemd[1]: Mounted /sysroot.
# lsinitrd /boot/initrd | grep -C2 sroot
-rwxr-xr-x   1 root     root         4780 May 21 08:45 shutdown
drwxr-xr-x   2 root     root            0 Jul 19 22:20 sys
drwxr-xr-x   2 root     root            0 Jul 19 22:20 sysroot
drwxr-xr-x   2 root     root            0 Jul 19 22:20 tmp
drwxr-xr-x   7 root     root            0 Jul 19 22:20 usr
--
-rwxr-xr-x   1 root     root        63680 Jul 11 12:52 usr/lib/systemd/systemd-shutdown
-rwxr-xr-x   1 root     root        22832 Jul 11 12:52 usr/lib/systemd/systemd-sysctl
lrwxrwxrwx   1 root     root           41 Jul 19 22:20 usr/lib/systemd/systemd-sysroot-fstab-check -> system-generators/systemd-fstab-generator
lrwxrwxrwx   1 root     root           17 Jul 19 22:20 usr/lib/systemd/systemd-udevd -> ../../bin/udevadm
-rwxr-xr-x   1 root     root        30912 Jul 11 12:52 usr/lib/systemd/systemd-vconsole-setup
#

jurombo · August 7, 2025, 8:41pm

I am using a LiveCD and MathW15 is a machine, with two different TWs on two drives.

jurombo · August 7, 2025, 8:41pm

I tried to resize my /boot and then now I cannot log into my TW. It is going into emergency mode.

Trying to check the filesystem with btrfs check gives me:

jurombo@MathW15:~> sudo btrfs check /dev/sdb5
Opening filesystem to check...
parent transid verify failed on 55999217664 wanted 1153971 found 1157407
parent transid verify failed on 55999217664 wanted 1153971 found 1157407
parent transid verify failed on 55999217664 wanted 1153971 found 1157407
Ignoring transid failure
ERROR: child eb corrupted: parent bytenr=67354624 item=365 parent level=1 child bytenr=55999217664 child level=1
ERROR: failed to read block groups: Input/output error
ERROR: cannot open file system

How do I fix this issue?

knurpht · August 7, 2025, 10:00pm

To be honest, you brought yourself in trouble. I think you have no other option than to do:
sudo btrfs check --repair /dev/sdb5 Read the output very carefully.

system · September 6, 2025, 10:00pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.