ERROR: device 'UUID=...' not found. Skipping fsck.

breadegg4 · 2024-04-10 08:32:58

my arch laptop suddenly crash. I really want to restore this driver because I have important file for my work. I already try my best on knowledge but because of my incompetence I don know how to fix this. My only hope now in this forum.

the following error output show after I boot my laptop.

Starting version 247.3-1-arch
ERROR: device 'UUID=...' not found. Skipping fsck.
mount: /new_root: can't find UUID=...
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off

since I can't use vim at `/new_root` I try to format `nvme1n1 driver and install another arch so the structure of the lsblk -f

all the bootloader is using GRUB

NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
zram0
                                                                            [SWAP]
nvme0n1
│                                                                           
├─nvme0n1p1
│    vfat   FAT32       6FB7-0EF9                                           
└─nvme0n1p2
                                                                            
nvme1n1
│                                                                           
├─nvme1n1p1
│    vfat   FAT32       4DC5-4EEB                             436.1M    15% /boot
└─nvme1n1p2
     btrfs              0ac6ba4c-687c-481f-a175-8a33d9e082cb    1.8T     3% /var/log
                                                                            /var/cache/pacman/pkg
                                                                            /home
                                                                            /.snapshots
                                                                            /

nvme0n1 is the arch I have installed but I can't boot it then I install another arch in nvme1n1.

I boot my system using nvme1n1 driver to check what wrong with my nvme0n1.

fsck -r /dev/nvme0n1p2

mount: /boot: wrong fs type, bad option, bad superblock/dev/nvme0n1. missing codepage or helper program, or other error 
dmesg(1) may have more information after failed mount system call.

[monochrome@syrufit ~]$ sudo fsck -r /dev/nvme0n1p2
fsck from util-linux 2.40
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/nvme0n1p2

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/nvme0n1p2: status 8, rss 20932, real 0.047386, user 0.028332, sys 0.009368

fdisk -l

Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: TS2TMTE250H                             
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: FD246CAE-848F-4DBC-8B87-1FB36B4EF00A

Device           Start        End    Sectors  Size Type
/dev/nvme0n1p1    2048    1050623    1048576  512M EFI System
/dev/nvme0n1p2 1050624 3907028991 3905978368  1.8T Linux filesystem


Disk /dev/nvme1n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: TS2TMTE250H                             
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: A1F97DF7-7F5B-43C4-ADD8-359ECACB859D

Device           Start        End    Sectors  Size Type
/dev/nvme1n1p1    2048    1050623    1048576  512M EFI System
/dev/nvme1n1p2 1050624 3907026943 3905976320  1.8T Linux filesystem


Disk /dev/zram0: 4 GiB, 4294967296 bytes, 1048576 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

sudo blkid

/dev/nvme0n1p1: UUID="6FB7-0EF9" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="c79bae78-fc3a-4e8d-82c2-49b100af58f2"
/dev/nvme0n1p2: PARTUUID="aeb1b786-6f4e-4ee3-a090-3c72d76d1e4f"
/dev/nvme1n1p2: UUID="0ac6ba4c-687c-481f-a175-8a33d9e082cb" UUID_SUB="ae8457ff-eff5-47cd-a565-abd2e0d233c6" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="d53587ce-9a5d-49c1-8356-75369e52170a"
/dev/nvme1n1p1: UUID="4DC5-4EEB" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="d1a825a4-99d3-4266-a882-bf5828f10d78"
/dev/zram0: LABEL="zram0" UUID="f34c5b43-1c96-4229-889b-6cc96640ee53" TYPE="swap"

since I don know why nvme0n1 nuked itself I can't boot it to check /etc/fstab.

I already check the following post but still don know how to fix this:
[Solved] cannot boot, ERROR: device "" not found, skipping fsck; re...
[SOLVED] ERROR: device 'UUID=88a...7c' not found. Skipping fsck.

I really appreciate the help. Thank you.

Last edited by breadegg4 (2024-04-10 08:35:36)

Maniaxx · 2024-04-10 18:47:28

1) What filesystem has it? If btrfs (like your other drive) try 'fsck.btrfs' explicitly. If ext4 try the alternate superblock (as stated in your fsck message).
2) Is it a standard partition (or encrypted/handled by LVM)?
3) Also give 'file -s /dev/nvme0n1p2' a try.
4) Take a look what's actually on the partition header (maybe there's garbage/all zero/ioerror or whatever) and compare it roughly to another one with the same filesystem.

# xxd -c16 -l4096 /dev/nvme0n1p2

or:

# hexdump -C -n4096 /dev/nvme0n1p2

5) Check drive vitality and firmware version for updates (i wouldn't update though until data is backed up).

# smartctl -a /dev/nvme0

Last edited by Maniaxx (2024-04-10 19:07:57)

breadegg4 · 2024-04-11 07:37:05

Hello Maniaxx thanks for the help really appreciate it.

1) sudo lsblk --output NAME,FSTYPE,LABEL,UUID,MODE

NAME        FSTYPE LABEL UUID                                 MODE
zram0                                                         brw-rw----
nvme0n1                                                       brw-rw----
├─nvme0n1p1 vfat         6FB7-0EF9                            brw-rw----
└─nvme0n1p2                                                   brw-rw----
nvme1n1                                                       brw-rw----
├─nvme1n1p1 vfat         4DC5-4EEB                            brw-rw----
└─nvme1n1p2 btrfs        0ac6ba4c-687c-481f-a175-8a33d9e082cb brw-rw----

it should be btrfs but fsck.btrfs not working.

it show following error

btrfs check /dev/nvme0n1p2

sudo btrfs check /dev/nvme0n1p2
Opening filesystem to check...
No valid Btrfs found on /dev/nvme0n1p2
ERROR: cannot open file system

2) It standard partition without any encryption

3)file -s /dev/nvme0n1p2

/dev/nvme0n1p2: data

4) xxd -c16 -l4096 /dev/nvme0n1p2
I can't show all the output because it beyond the terminal

00000de0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000df0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e00: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e10: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e20: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e30: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e40: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e50: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e60: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e70: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e80: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000e90: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000ea0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000eb0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000ec0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000ed0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000ee0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000ef0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f00: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f10: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f20: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f30: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f40: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f50: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f60: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f70: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f80: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000f90: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000fa0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000fb0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000fc0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000fd0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000fe0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000ff0: 0000 0000 0000 0000 0000 0000 0000 0000  ................

hexdump -C -n4096 /dev/nvme0n1p2

00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00001000

5) smartctl -a /dev/nvme0

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.4-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       TS2TMTE250H
Serial Number:                      H799940075
Firmware Version:                   A224V81A
PCI Vendor/Subsystem ID:            0x1d79
IEEE OUI Identifier:                0x48357c
Total NVM Capacity:                 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          2,000,398,934,016 [2.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            7c3548 520c846deb
Local Time is:                      Thu Apr 11 15:14:51 2024 CST
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005e):     Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     85 Celsius
Critical Comp. Temp. Threshold:     90 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     9.00W       -        -    0  0  0  0        0       0
 1 +     4.60W       -        -    1  1  1  1   100000  100000
 2 +     3.80W       -        -    2  2  2  2   500000  500000
 3 -   0.0450W       -        -    3  3  3  3     2000    2000
 4 -   0.0040W       -        -    4  4  4  4     6000    8000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        40 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    2,944,642 [1.50 TB]
Data Units Written:                 11,691,375 [5.98 TB]
Host Read Commands:                 22,408,127
Host Write Commands:                266,647,561
Controller Busy Time:               362
Power Cycles:                       309
Power On Hours:                     2,514
Unsafe Shutdowns:                   148
Media and Data Integrity Errors:    0
Error Information Log Entries:      12
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, 8 of 8 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

I also want to add up what is my previous partition look like:
https://bbs.archlinux.org/viewtopic.php … 1#p2139701

I didn't make any change and just leave it like that.

Last edited by breadegg4 (2024-04-11 07:48:35)

seth · 2024-04-11 14:43:07

The first 4kB of that partition are blank

since I can't use vim at `/new_root` I try to format `nvme1n1 driver

might indicate bad things.
https://wiki.archlinux.org/title/File_r … d_PhotoRec - but it looks like you've zero'd the partition?

arch64 · 2024-04-11 16:59:12

seth wrote:

The first 4kB of that partition are blank

That's normal. The first superblock is located at 64KiB.
https://btrfs.readthedocs.io/en/latest/ … superblock

arch64 · 2024-04-11 17:16:23

breadegg4 wrote:

/dev/nvme1n1p2: UUID="0ac6ba4c-687c-481f-a175-8a33d9e082cb" UUID_SUB="ae8457ff-eff5-47cd-a565-abd2e0d233c6" BLOCK_SIZE="4096" TYPE="btrfs"

Are you able to mount /dev/nvme1n1p2 somewhere? The following command should mount the partition read-only on /mnt

mount -o ro /dev/nvme1n1p2 /mnt

This topic: [SOLVED] Can't recover bad superblock on BTRFS filesystem has a similar No valid Btrfs found on error and was solved by recovering the superblock using btrfs rescue.

Last edited by arch64 (2024-04-11 17:34:50)

seth · 2024-04-11 20:40:12

D'ohh, I missed that the OP only posted the tail of xxd
@breadegg4

sudo xxd -c16 -l4096 /dev/nvme0n1p2 | curl -F 'file=@-' 0x0.st

Maniaxx · 2024-04-11 22:04:21

The 2nd 'hexdump' shows all zeros (the asterisk is "squeezing" zero lines).

Maybe increase to 132KB (561KB).

sudo xxd -c16 -l135168 /dev/nvme0n1p2 | curl -F 'file=@-' 0x0.st

Or use '010editor' or any other graphical hexeditor to inspect the partition. Jump to (physical) address 537919488 (0x20100000) and roughly scroll over the partition. If there is data (and you cannot recover the btrfs structure) you might still have a chance to recover files by patterns/known file headers.

But you probably want to start with 'btrfs rescue' first (as mentioned above).

Last edited by Maniaxx (2024-04-12 17:29:38)

arch64 · 2024-04-11 22:50:19

breadegg4 wrote:

└─nvme1n1p2 btrfs        0ac6ba4c-687c-481f-a175-8a33d9e082cb brw-rw----

it should be btrfs but fsck.btrfs not working.

btrfs check /dev/nvme0n1p2

sudo btrfs check /dev/nvme0n1p2
Opening filesystem to check...
No valid Btrfs found on /dev/nvme0n1p2
ERROR: cannot open file system

You ran btrfs check on the wrong partition. /dev/nvme1n1p2 is the one with btrfs. Before running btrfs check make sure to
read the warning on this site: https://btrfs.readthedocs.io/en/latest/btrfs-check.html.

I actually ran into the very same issue as you today with the slight difference of running on JFS in a VM.
I solved my issue by mounting the root partision on /mnt and then arch-chroot /mnt and then downgrade the
linux kernel from 6.8.4 to 6.7.11. I am almost 100% certain there's nothing wrong with your data.

seth · 2024-04-12 07:40:18

I try to format `nvme1n1 driver and install another arch

Afaiu the OP they lost the access to nvme0n1p2 and simply installed a second OS on nvme1n1 - this is consistent w/ cross-referncing

/dev/nvme0n1p2: PARTUUID="aeb1b786-6f4e-4ee3-a090-3c72d76d1e4f"

and their linked post https://bbs.archlinux.org/viewtopic.php?id=291428 (the partuuid is used at the kernel commandline and the related UUID "d2d454dc-352e-4cdc-9ce1-2321bc323811" doesn't show up in this thread)

As Maniaxx pointed out, the hexdump actually does suggest that the 1st 4k are entirely blank (what's not normal and since the UUID and LABEL are stored there, among others) and, along the btrfs failure raises the concern that the entire partition has been subjected to dd if=/dev/zero

---

I solved my issue by mounting the root partision on /mnt and then arch-chroot /mnt and then downgrade the linux kernel from 6.8.4 to 6.7.11.

There's a super-high chance you updated the system w/o mounting the boot partition (or did mount a spurious boot partition while booting from the root partition) and were booting the older kernel w/o its matching modules in /lib/modules (this happens rather a-lot…)

Last edited by seth (2024-04-12 07:40:55)

arch64 · 2024-04-12 15:19:48

seth wrote:

As Maniaxx pointed out, the hexdump actually does suggest that the 1st 4k are entirely blank (what's not normal and since the UUID and LABEL are stored there, among others) and, along the btrfs failure raises the concern that the entire partition has been subjected to dd if=/dev/zero

In btrfs UUID and LABEL are stored in the superblock which begins at 64KIB. UUID is at offset (from the start of the superblock) 0x20 and label is at 0x12b.
Look at the link to the superblock I linked earlier. 0x20 is byte 32 and 0x12b is byte 299.

---

There's a super-high chance you updated the system w/o mounting the boot partition (or did mount a spurious boot partition while booting from the root partition) and were booting the older kernel w/o its matching modules in /lib/modules (this happens rather a-lot…)

I have retried multiple times just to make sure. Upgrade to 6.8.4 boot fails, downgrade to 6.7.11 boot succeeds. /boot is mounted.
Don't understand why. Let's see if it persists with 6.8.5.

breadegg4 · 2024-04-12 17:23:42

arch64 wrote:

breadegg4 wrote:
/dev/nvme1n1p2: UUID="0ac6ba4c-687c-481f-a175-8a33d9e082cb" UUID_SUB="ae8457ff-eff5-47cd-a565-abd2e0d233c6" BLOCK_SIZE="4096" TYPE="btrfs" 
Are you able to mount /dev/nvme1n1p2 somewhere? The following command should mount the partition read-only on /mnt
mount -o ro /dev/nvme1n1p2 /mnt
This topic: [SOLVED] Can't recover bad superblock on BTRFS filesystem has a similar No valid Btrfs found on error and was solved by recovering the superblock using btrfs rescue.

I try using btrfs rescue but it not working

➜  ~ lsblk                                       
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
zram0       254:0    0    4G  0 disk [SWAP]
nvme1n1     259:0    0  1.8T  0 disk 
├─nvme1n1p1 259:2    0  512M  0 part /boot
└─nvme1n1p2 259:3    0  1.8T  0 part /var/log
                                     /var/cache/pacman/pkg
                                     /home
                                     /.snapshots
                                     /
nvme0n1     259:1    0  1.8T  0 disk 
├─nvme0n1p1 259:4    0  512M  0 part 
└─nvme0n1p2 259:5    0  1.8T  0 part 
➜  ~ sudo btrfs rescue super-recover -v /dev/nvme0n1p2
No valid Btrfs found on /dev/nvme0n1p2
Usage or syntax errors
➜  ~ sudo 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.

here is command I run as @Maniaxx and @seth suggest

sudo xxd -c16 -l135168 /dev/nvme0n1p2 | curl -F 'file=@-' 0x0.st

here the link output:
https://0x0.st/X-Sp.txt

Maniaxx · 2024-04-12 17:38:28

The 1st superblock (0x10000) is filled with 0xff.

Let's check the second one (68159488 [0x4100800]) :

sudo xxd -c16 -l12288 -s68155392 /dev/nvme0n1p2 | curl -F 'file=@-' 0x0.st

Also try this:

sudo btrfs check --super 1 /dev/nvme0n1p2
sudo btrfs check --super 2 /dev/nvme0n1p2

How much data should be (roughly) on the partition (in MB/GB)?

Last edited by Maniaxx (2024-04-12 18:00:59)

breadegg4 · 2024-04-13 09:05:09

Maniaxx wrote:

The 1st superblock (0x10000) is filled with 0xff.
Let's check the second one (68159488 [0x4100800]) :
sudo xxd -c16 -l12288 -s68155392 /dev/nvme0n1p2 | curl -F 'file=@-' 0x0.st
Also try this:
sudo btrfs check --super 1 /dev/nvme0n1p2
sudo btrfs check --super 2 /dev/nvme0n1p2
How much data should be (roughly) on the partition (in MB/GB)?

http://0x0.st/X-_S.html

sudo btrfs check --super 1 /dev/nvme0n1p2

using SB copy 1, bytenr 67108864
Opening filesystem to check...
No valid Btrfs found on /dev/nvme0n1p2
ERROR: cannot open file system

sudo btrfs check --super 2 /dev/nvme0n1p2

using SB copy 2, bytenr 274877906944
Opening filesystem to check...
No valid Btrfs found on /dev/nvme0n1p2
ERROR: cannot open file system

seth · 2024-04-13 12:16:41

~900 bytes of svg, then some data, the last ~3.3kB are blank again

Have you checked whether testdisk can find some filesystem?

Maniaxx · 2024-04-13 16:46:37

The xxd address equals the one provided by 'btrfs check --super 1' so the dump should be correct. But the result is suspicious indeed. As if btrfs would never been there. Testdisk is a good idea.

arch64 · 2024-04-14 13:39:29

There's also

 btrfs rescue chunk-recover /nvme0n1p2

but without superblocks it will likely fail.

btrfs restore -D /dev/nvme0n1p2 /path/to/recovered/data

The -D option will only list what files it can recover.

Other btrfs recovery tools:
https://www.lukeshu.com/blog/btrfs-rec.html
https://github.com/theY4Kman/btrfs-recon

Arch Linux

#1 2024-04-10 08:32:58

ERROR: device 'UUID=...' not found. Skipping fsck.

#2 2024-04-10 18:47:28

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#3 2024-04-11 07:37:05

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#4 2024-04-11 14:43:07

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#5 2024-04-11 16:59:12

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#6 2024-04-11 17:16:23

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#7 2024-04-11 20:40:12

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#8 2024-04-11 22:04:21

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#9 2024-04-11 22:50:19

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#10 2024-04-12 07:40:18

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#11 2024-04-12 15:19:48

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#12 2024-04-12 17:23:42

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#13 2024-04-12 17:38:28

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#14 2024-04-13 09:05:09

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#15 2024-04-13 12:16:41

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#16 2024-04-13 16:46:37

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

#17 2024-04-14 13:39:29

Re: ERROR: device 'UUID=...' not found. Skipping fsck.

Board footer