Hello,
I am running Tumbleweed on a Ryzen 7 laptop with Nvidia graphics and 2 Samsung SSD’s. Used the laptop normally yesterday, shut down normally too. When starting today it boots into emergency mode. How to get the output of journalctl -xb to another computer to post it here ?
Tried to update (from installation USB stick) the system but failed because of several partition mount errors.
Attached a picture of the bootup screen. Any other information required ?
Thanks!
It is showing problems on your NVME drive. This could be a hardware failure, but that’s only a guess.
Ok, so no more suggestions? If it is a SSD malfunction, could it be that the large number of Tumbleweed updates effects the SSD longevity ?
It is known that an SSD has a shorter expected life than rotating rust.
Hmm, sources please.
does not sound trustworthy
Well known. Flash has limited number of erase cycles and thus writes. This is why load leveling was invented to spreed the erases across the full address space.
I’m a bit doubtful that TW updates have that much of an effect to drive longevity.
Do you have a separate /home partition, or some other partition available besides the root partition?
If yes, you can redirect the output to one of those. Example, just days ago, one of my TW installs would boot with the root partition as read-only (because of BTRFS errors). Because I have a separate /home, I simply logged in as my regular user, then ran “dmesg > someFilename.txt”. It may also be possible to redirect to an external drive.
One other thing you might consider - download a “rescue” ISO and write it to a thumb-drive, then boot to it.
Did you ever ask yourself “how much”? Samsung 1TB SATS SSD provides warranty for 300-360TBW. How much do you write daily? Weekly? Yearly?
It’s still limited try with spare blocks and load leveling you do get 100s of terabytes of writes. But it also depends type of flash amount of spare blocks and size of average write . Even a single byte written usually sends on average 100K byte block to the erase cycler. Current flash will survive about 10K erases last I looked.
FYI some history. I bought this laptop at a linux laptop store, but they did not offer Open Suse as a preinstall. So it was blanc when I received it. Tried installing Leap 15.2 (latest available version at that time) but that did not support the Ryzen / Nvidia combination. After some research (and support from the linux shop) I found out that Leap did not have a kernel version that supported the Ryzen/Nvidia combination. So I had to resort to Tumbleweed. Over the years in use I installed thousands of updates. I have/had a /home directory that contains loads of history documents/email, which are now inaccessible. I now have ordered a new SSD drive. Will install that in place of the inaccessible drive, reinstall Tumbleweed on that new drive and mount the inaccessible drive as second SSD.
I hope that I then can access my /home directory. I was not able to access it with a live USB stick, but that can be a security measure I assume. Will keep you posted on the outcome. Thanks.
Best of luck on the recovery!!
I understand your frustration !! About 30 years ago, I learned the importance of a separate /home partition. It proved useful just three days ago, when my main TW installation would only boot to read-only mode on the root partition because of BTRFS errors (now recovered).
The screenshot posted above also shows a lot of BTRFS errors. How did you recover from these ?
Are you responding to me, “@myswtest” ??
If yes, you can see my thread in here at:
… jump to my response message #18, that begins with “I am HAPPY to report that I ran the steps”
I briefly explain what steps I followed (though you might want to read thru all of the thread)
.
Tried the proposed ’ How to repair a broken/unmountable btrfs filesystem’ with the TW live USB :
linux@mx1:~> su
mx1:/home/linux # mount /dev/nvme0 /mnt
mount: /mnt: /dev/nvme0 is not a block device.
dmesg(1) may have more information after failed mount system call.
mx1:/home/linux # dmesg(1)
bash: syntax error near unexpected token1' mx1:/home/linux # btrfs scrub start /mnt ERROR: not a btrfs filesystem: /mnt mx1:/home/linux # btrfs scrub status /mnt ERROR: not a btrfs filesystem: /mnt mx1:/home/linux # btrfs scrub start /dev/nvme0 ERROR: not a directory: /dev/nvme0 mx1:/home/linux # btrfs scrub status /dev/nvme0 ERROR: not a directory: /dev/nvme0 mx1:/home/linux # mount -o usebackuproot /dev/nvme0 /mnt mount: /mnt: /dev/nvme0 is not a block device. dmesg(1) may have more information after failed mount system call. mx1:/home/linux # dmesg(1) bash: syntax error near unexpected token1’
mx1:/home/linux # btrfs check /dev/nvme0
Opening filesystem to check…
ERROR: not a regular file or block device: /dev/nvme0
ERROR: cannot open file system
mx1:/home/linux # btrfs restore /dev/nvme0 /mnt/usbdrive
ERROR: not a regular file or block device: /dev/nvme0
Could not open root, trying backup super
ERROR: not a regular file or block device: /dev/nvme0
Could not open root, trying backup super
ERROR: not a regular file or block device: /dev/nvme0
Could not open root, trying backup super
mx1:/home/linux # btrfs restore /dev/nvme0 /mnt/nvm1
ERROR: not a regular file or block device: /dev/nvme0
Could not open root, trying backup super
ERROR: not a regular file or block device: /dev/nvme0
Could not open root, trying backup super
ERROR: not a regular file or block device: /dev/nvme0
Could not open root, trying backup super
mx1:/home/linux # btrfs rescue super-recover /dev/nvme0
Usage or syntax errors
mx1:/home/linux # mount /dev/nvme0 /mnt
mount: /mnt: /dev/nvme0 is not a block device.
dmesg(1) may have more information after failed mount system call.
mx1:/home/linux # btrfs rescue zero-log /dev/nvme0
ERROR: not a regular file or block device: /dev/nvme0
ERROR: could not open ctree
mx1:/home/linux # btrfs rescue chunk-recover /dev/nvme0
read super block error
recover prepare error
mx1:/home/linux #
I guess I could have stopped at : /mnt: /dev/nvme0 is not a block device.
I assume this is a serious problem, any further suggestions ?
No, it is the wrong name. NVMe devices in Linux are not usually named this way. Use the correct name for your device.
Well, the system stopped you, because you were not mounting a partition, based on your console output … your first mount attempt did NOT designate a partition.
Check out my screenshot … that is a visual clue as to the naming structure of an NVME drive and its partitions. That screenshot shows TWO different NVME drives (there’s a 3rd sda drive too).
nvme0n1 is the DRIVE (and second drive nvme1n1) …
and nvme0n1p2 (p1 , p3 , p4) are the partitions.
Thanks, my oversight as a novice at this. Tried again with nvme0n1 :
linux@mx1:~> su
mx1:/home/linux # mount /dev/nvme0n1 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
mx1:/home/linux # dmesg(1)
bash: syntax error near unexpected token `1’
mx1:/home/linux # btrfs scrub start /mnt
ERROR: not a btrfs filesystem: /mnt
mx1:/home/linux # btrfs scrub status /mnt
ERROR: not a btrfs filesystem: /mnt
mx1:/home/linux # btrfs scrub start /dev/nvme0n1
ERROR: ‘/dev/nvme0n1’ is not a mounted btrfs device
mx1:/home/linux # btrfs scrub status /dev/nvme0n1
ERROR: ‘/dev/nvme0n1’ is not a mounted btrfs device
mx1:/home/linux # mount -o usebackuproot /dev/nvme0n1 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
mx1:/home/linux # btrfs check /dev/nvme0n1
Opening filesystem to check…
No valid Btrfs found on /dev/nvme0n1
ERROR: cannot open file system
mx1:/home/linux # btrfs restore /dev/nvme0n1 /mnt/nvme1n1
No valid Btrfs found on /dev/nvme0n1
Could not open root, trying backup super
No valid Btrfs found on /dev/nvme0n1
Could not open root, trying backup super
No valid Btrfs found on /dev/nvme0n1
Could not open root, trying backup super
mx1:/home/linux # btrfs rescue super-recover /dev/nvme01n1
ERROR: mount check: cannot open /dev/nvme01n1: No such file or directory
ERROR: could not check mount status: No such file or directory
mx1:/home/linux # btrfs rescue chunk-recover /dev/nvme0n1
read super block error
recover prepare error
mx1:/home/linux #
Hardware failure after all ?
More likely you need to use the correct partition instead of full device.
Looking at the picture in your very first post I guess you should have tried
mount /dev/nvme1n1p2 /mnt
I am somewhat confused by this, I assume that nvme0n1p2 is the (broken) system partition, nvme1n1p1 is a data partition and is normally accessible, apparently nvme1n1p2 does not exist.
Please correct me if I am wrong. Anyhow, tried again with nvme0n1p2 :
linux@mx1:~> su
mx1:/home/linux # mount /dev/nvme0n1p2 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme0n1p2, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
mx1:/home/linux # btrfs scrub start /mnt
ERROR: not a btrfs filesystem: /mnt
mx1:/home/linux # btrfs scrub status /mnt
ERROR: not a btrfs filesystem: /mnt
mx1:/home/linux # btrfs scrub start /dev/nvme0n1p2
scrub started on /dev/nvme0n1p2, fsid ccf6f517-0782-440a-8ad9-9d4d127ec422 (pid=5731)
mx1:/home/linux # btrfs scrub status /dev/nvme0n1p2
UUID: ccf6f517-0782-440a-8ad9-9d4d127ec422
Scrub started: Mon May 1 05:39:50 2023
Status: aborted
Duration: 0:00:00
Total to scrub: 57.80GiB
Rate: 0.00B/s
Error summary: no errors found
mx1:/home/linux # mount /dev/nvme0n1p2 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme0n1p2, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
mx1:/home/linux # mount -o usebackuproot /dev/nvme0n1p2 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme0n1p2, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
mx1:/home/linux # btrfs check /dev/nvme0n1p2
Opening filesystem to check…
ERROR: /dev/nvme0n1p2 is currently mounted, use --force if you really intend to check the filesystem
mx1:/home/linux # btrfs restore /dev/nvme0n1p2 /mnt/nvme1n1p1
ERROR: /dev/nvme0n1p2 is currently mounted, cannot continue
mx1:/home/linux # btrfs rescue super-recover /dev/nvme0n1p2
ERROR: the device is busy
mx1:/home/linux # btrfs rescue chunk-recover /dev/nvme0n1p2
ERROR: the device is busy
mx1:/home/linux #
I am somewhat lost now.
