November 23, 20232 yr So I did a clean reboot of my system and when it booted back up disk 3 now says unmountable wrong or no file system. The drive has been working up to this point (I put this drive in probably 2 months ago or so). Additionally until stopping and starting the array a few times it also failed to load the docker (but they are now being loaded). I have three drives, they are all btrfs (which i know i should change that and might do that with unbalance after i get this drive back up and running if i can). Any suggestions on how I can get it mountable and move the stuff off of it? I appreciate all of your help and have attached diag. saber-diagnostics-20231122-2235.zip Edited November 23, 20232 yr by SaberTreasures
November 23, 20232 yr Community Expert Looks like there's no valid btrfs filesystem on disk3, post the output of: btrfs fi show
November 23, 20232 yr Author 1 hour ago, JorgeB said: Looks like there's no valid btrfs filesystem on disk3, post the output of: btrfs fi show Thats strange, its been btrfs for the 2 months now and no problem and it has about 2TB of data on it prior to restart - here's the output of your command - Appreciate any and all help and your time. root@Saber:~# btrfs fi show Label: none uuid: 10091590-8586-45b5-82b5-654bd5cd3b71 Total devices 1 FS bytes used 7.01TiB devid 1 size 10.91TiB used 7.05TiB path /dev/mapper/md1 Label: none uuid: 7860e9cf-a7d1-4473-adfb-b67685f33db2 Total devices 1 FS bytes used 5.47TiB devid 1 size 10.91TiB used 5.53TiB path /dev/mapper/md2 Label: none uuid: e2bcedfe-609f-40ce-9531-11ef1b201d31 Total devices 1 FS bytes used 70.76GiB devid 1 size 931.51GiB used 556.02GiB path /dev/nvme1n1p1 Label: none uuid: e6def48b-8343-4c23-b729-d0e6bf475ca6 Total devices 1 FS bytes used 16.34GiB devid 1 size 232.88GiB used 23.02GiB path /dev/nvme0n1p1 Label: none uuid: 31006f9a-9233-4419-a454-43b4e4bdb1c0 Total devices 1 FS bytes used 15.58GiB devid 1 size 35.00GiB used 22.02GiB path /dev/loop2 Label: none uuid: c9ad3558-6606-44e2-b4ef-6a95aac5ceaf Total devices 1 FS bytes used 988.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop3 Also a screenshot of the device array area (they are all btrfs encrypted) - Edited November 23, 20232 yr by SaberTreasures
November 23, 20232 yr Community Expert Yep, no btrfs filesystem there, and the output of: fdisk -l /dev/sdb
November 23, 20232 yr Author 7 minutes ago, JorgeB said: Yep, no btrfs filesystem there, and the output of: fdisk -l /dev/sdb Output below - root@Saber:~# fdisk -l /dev/sdb Disk /dev/sdb: 10.91 TiB, 12000138625024 bytes, 23437770752 sectors Disk model: ST12000NM001G-2M Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 079AAD43-C6C4-4769-BB43-B69CFE630BFD Device Start End Sectors Size Type /dev/sdb1 64 23437770718 23437770655 10.9T Linux filesystem root@Saber:~#
November 23, 20232 yr Community Expert At least the partition is there, try these recovery options in case it's a superblock issue.
November 23, 20232 yr Author 33 minutes ago, JorgeB said: At least the partition is there, try these recovery options in case it's a superblock issue. Hey JorgeB - Again appreciate all of your time - I tried some of your methods, before I go to your 3rd dangerous option wondering if you could see if I am doing your other two options correctly or not? Here's what I tried in terminal - root@Saber:~# mkdir /temp3 root@Saber:~# mount -o rescue=all,ro /dev/mapper/sdb1 /temp3 mount: /temp3: special device /dev/mapper/sdb1 does not exist. dmesg(1) may have more information after failed mount system call. root@Saber:~# mount -o degraded,rescue=all,ro /dev/mapper/sdb1 /temp3 mount: /temp3: special device /dev/mapper/sdb1 does not exist. dmesg(1) may have more information after failed mount system call. root@Saber:~# cd /mnt/disk2 root@Saber:/mnt/disk2# mkdir restore root@Saber:~# btrfs restore -v /dev/mapper/sdb1 /mnt/disk2/restore ERROR: mount check: cannot open /dev/mapper/sdb1: No such file or directory ERROR: could not check mount status: No such file or directory root@Saber:~# btrfs restore -v /dev/md3 /mnt/disk2/restore No valid Btrfs found on /dev/md3 Could not open root, trying backup super No valid Btrfs found on /dev/md3 Could not open root, trying backup super No valid Btrfs found on /dev/md3 Could not open root, trying backup super root@Saber:~# btrfs restore -v /dev/mapper/md3 /mnt/disk2/restore No valid Btrfs found on /dev/mapper/md3 Could not open root, trying backup super No valid Btrfs found on /dev/mapper/md3 Could not open root, trying backup super No valid Btrfs found on /dev/mapper/md3 Could not open root, trying backup super root@Saber:~#
November 23, 20232 yr Community Expert There are also no backup superblocks, I'm afraid the last option won't work either, best bet is to restore from a backup or if none exists you can try a file recovery util, like UFS explorer.
November 23, 20232 yr Author 2 minutes ago, JorgeB said: There are also no backup superblocks, I'm afraid the last option won't work either, best bet is to restore from a backup or if none exists you can try a file recovery util, like UFS explorer. Couple more newbie questions - 1. I dont think I have any backups other than like parity? First off, how would i start doing backups for future (any articles there or something I can read)? Secondly, is there someway to utilize parity for this or not a good idea? 2. Does this mean the drive is bad in general? I've run smart checks on it, did all the pre clear stuff and everything seemed fine (prior to using it a few months ago). Or something just happened to the file system? Would you suggest trying the drive again or getting another? 3. Any articles to suggest how to use UFS explorer on unraid on a particular drive? I'll also start googling that. Atleast it was only about 1.5TB of data (and not one of the other hard drives, if I have to lose the data then I guess it's not the worst situation, but of course would rather not. Appreciate your help!
November 23, 20232 yr Community Expert Parity usually won't help with filesystem issues, but you can try to see if the emulated disk mounts. Disk looks fine, though if the same thing were to happen again to the same disk I would replace it. Sorry, never used it, I just know that some users have.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.