Entxawp
-
Posts
33 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by Entxawp
-
-
7 hours ago, JorgeB said:
It's not the superblock, first error lines are the important ones, it's extent tree corruption, loos like part of it was wiped/trimmed, if it's just the extent tree btrfs restore should be able to recover most of your data.
Neither of the three options given worked in my situation
root@entxvault:~# mkdir /x mkdir: cannot create directory ‘/x’: File exists root@entxvault:~# mount -o usebackuproot,ro /dev/nvme1n1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme1n1, missing codepage or helper program, or other error. root@entxvault:~# mount -o usebackuproot,ro /dev/nvme2n1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme2n1, missing codepage or helper program, or other error. root@entxvault:~# mount -o degraded,usebackuproot,ro /dev/nvme1n1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme1n1, missing codepage or helper program, or other error. root@entxvault:~# root@entxvault:~# mount -o degraded,usebackuproot,ro /dev/nvme2n1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme2n1, missing codepage or helper program, or other error. root@entxvault:~# mount -o ro,notreelog,nologreplay /dev/nvme1n1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/nvme1n1, missing codepage or helper program, or other error. root@entxvault:~# btrfs check --repair /dev/nvme1n1 enabling repair mode WARNING: Do not use --repair unless you are advised to do so by a developer or an experienced user, and then only after having accepted that no fsck can successfully repair all types of filesystem corruption. Eg. some software or hardware bugs can fatally damage a volume. The operation will start in 10 seconds. Use Ctrl-C to stop it. 10 9 8 7 6 5 4 3 2 1 Starting repair. Opening filesystem to check... No valid Btrfs found on /dev/nvme1n1 ERROR: cannot open file system root@entxvault:~#
-
Sep 12 17:27:06 entxvault root: mount: /mnt/cache: can't read superblock on /dev/nvme1n1p1.
It seems to be a damaged superblock. On these threads from before I found that there are backups of the superblocks but I am unsure of how to fix it in my situation.
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-543490
-
Here is the diagnostics
entxvault-diagnostics-20200912-2022.zip
Sep 12 17:27:05 entxvault emhttpd: shcmd (91): mkdir -p /mnt/cache Sep 12 17:27:05 entxvault emhttpd: /mnt/cache uuid: da42f43c-1bfa-495a-a654-77d5e00d774d Sep 12 17:27:05 entxvault emhttpd: /mnt/cache TotDevices: 2 Sep 12 17:27:05 entxvault emhttpd: /mnt/cache NumDevices: 2 Sep 12 17:27:05 entxvault emhttpd: /mnt/cache NumFound: 2 Sep 12 17:27:05 entxvault emhttpd: /mnt/cache NumMissing: 0 Sep 12 17:27:05 entxvault emhttpd: /mnt/cache NumMisplaced: 0 Sep 12 17:27:05 entxvault emhttpd: /mnt/cache NumExtra: 0 Sep 12 17:27:05 entxvault emhttpd: /mnt/cache LuksState: 0 Sep 12 17:27:05 entxvault emhttpd: shcmd (92): mount -t btrfs -o noatime,space_cache=v2 -U da42f43c-1bfa-495a-a654-77d5e00d774d /mnt/cache Sep 12 17:27:05 entxvault kernel: BTRFS info (device nvme1n1p1): using free space tree Sep 12 17:27:05 entxvault kernel: BTRFS info (device nvme1n1p1): has skinny extents Sep 12 17:27:06 entxvault kernel: BTRFS info (device nvme1n1p1): enabling ssd optimizations Sep 12 17:27:06 entxvault kernel: BTRFS info (device nvme1n1p1): start tree-log replay Sep 12 17:27:06 entxvault kernel: BTRFS error (device nvme1n1p1): bad tree block start, want 4529101275136 have 0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Sep 12 17:27:06 entxvault kernel: BTRFS: error (device nvme1n1p1) in __btrfs_free_extent:3080: errno=-5 IO failure Sep 12 17:27:06 entxvault kernel: BTRFS: error (device nvme1n1p1) in btrfs_run_delayed_refs:2189: errno=-5 IO failure Sep 12 17:27:06 entxvault kernel: BTRFS: error (device nvme1n1p1) in btrfs_replay_log:2243: errno=-5 IO failure (Failed to recover log tree) Sep 12 17:27:06 entxvault root: mount: /mnt/cache: can't read superblock on /dev/nvme1n1p1. Sep 12 17:27:06 entxvault kernel: BTRFS error (device nvme1n1p1): open_ctree failed Sep 12 17:27:06 entxvault emhttpd: shcmd (92): exit status: 32 Sep 12 17:27:06 entxvault emhttpd: /mnt/cache mount error: No file system Sep 12 17:27:06 entxvault emhttpd: shcmd (93): umount /mnt/cache Sep 12 17:27:06 entxvault root: umount: /mnt/cache: not mounted. Sep 12 17:27:06 entxvault emhttpd: shcmd (93): exit status: 32 Sep 12 17:27:06 entxvault emhttpd: shcmd (94): rmdir /mnt/cache Sep 12 17:27:06 entxvault emhttpd: shcmd (95): mkdir -p /mnt/vmdrive Sep 12 17:27:06 entxvault emhttpd: shcmd (96): mount -t btrfs -o noatime /dev/nvme0n1p1 /mnt/vmdrive Sep 12 17:27:06 entxvault kernel: BTRFS info (device nvme0n1p1): disk space caching is enabled Sep 12 17:27:06 entxvault kernel: BTRFS info (device nvme0n1p1): has skinny extents Sep 12 17:27:06 entxvault kernel: BTRFS info (device nvme0n1p1): enabling ssd optimizations
-
-
I have an issue with 6.9.0-beta25. The server crashed/froze for the first time on the 8th (updated to beta25 on the 30th) but now turns off every few hours. I have no idea what is going on but here is my log and a foto of the server's monitor.
I turned of Containers, updated plugins and removed my overclock but it doesn't seem to help.
Hope someone can help, Ent
Unraid OS version 6.9.0-beta25 available
-
-
-
-
-
in Prereleases
Posted
I had a backup from 2 days ago and ended up going that route after going back to unraid 6.8.3 that also stopped my issues with plex crashing/freezing the server