nicecube Posted February 2, 2018 Share Posted February 2, 2018 (edited) Hi, i need help, after a power failure my cache disk ask to be formatted and my docker will not boot anymore. I try to restart my server 2 times and the disk still does not boot. I was wondering if there is a way to do a disk check or enable parity to fix my array. Sorry for the big picture but i would like to add more information as possible. I hope to be able to fix the problem. Feb 1 19:31:07 Tower kernel: sd 9:0:7:0: [sdn] 234441648 512-byte logical blocks: (120 GB/112 GiB) Feb 1 19:31:07 Tower kernel: sd 9:0:7:0: [sdn] Write Protect is off Feb 1 19:31:07 Tower kernel: sd 9:0:7:0: [sdn] Mode Sense: 73 00 00 08 Feb 1 19:31:07 Tower kernel: sd 9:0:7:0: [sdn] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 1 19:31:07 Tower kernel: sdn: sdn1 Feb 1 19:31:07 Tower kernel: sd 9:0:7:0: [sdn] Attached SCSI disk Feb 1 19:31:07 Tower kernel: BTRFS: device fsid 2a6067f8-0a58-4f51-98ff-9522b8181eb8 devid 1 transid 563610 /dev/sdn1 Feb 1 19:31:24 Tower emhttpd: KINGSTON_SV300S3_50026B77580346E9_350026b77580346e9 (sdn) 512 234441648 Feb 1 19:31:24 Tower emhttpd: import 30 cache device: (sdn) KINGSTON_SV300S3_50026B77580346E9_350026b77580346e9 Feb 1 19:31:29 Tower emhttpd: shcmd (96): mount -t btrfs -o noatime,nodiratime /dev/sdn1 /mnt/cache Feb 1 19:31:29 Tower kernel: BTRFS info (device sdn1): disk space caching is enabled Feb 1 19:31:29 Tower kernel: BTRFS info (device sdn1): has skinny extents Feb 1 19:31:29 Tower kernel: BTRFS info (device sdn1): enabling ssd optimizations Feb 1 19:31:29 Tower kernel: BTRFS error (device sdn1): parent transid verify failed on 141355253760 wanted 563611 found 563400 Feb 1 19:31:29 Tower kernel: BTRFS warning (device sdn1): failed to read log tree Feb 1 19:31:29 Tower root: mount: /mnt/cache: can't read superblock on /dev/sdn1. Feb 1 19:31:29 Tower kernel: BTRFS error (device sdn1): open_ctree failed Feb 1 19:41:44 Tower emhttpd: shcmd (159): /usr/sbin/hdparm -S0 /dev/sdn Feb 1 19:41:44 Tower root: /dev/sdn: Feb 1 19:57:07 Tower emhttpd: shcmd (1167): mount -t btrfs -o noatime,nodiratime /dev/sdn1 /mnt/cache Feb 1 19:57:07 Tower kernel: BTRFS info (device sdn1): disk space caching is enabled Feb 1 19:57:07 Tower kernel: BTRFS info (device sdn1): has skinny extents Feb 1 19:57:07 Tower kernel: BTRFS info (device sdn1): enabling ssd optimizations Feb 1 19:57:07 Tower kernel: BTRFS error (device sdn1): parent transid verify failed on 141355253760 wanted 563611 found 563400 Feb 1 19:57:07 Tower kernel: BTRFS warning (device sdn1): failed to read log tree Feb 1 19:57:07 Tower root: mount: /mnt/cache: can't read superblock on /dev/sdn1. Feb 1 19:57:07 Tower kernel: BTRFS error (device sdn1): open_ctree failed Feb 1 20:55:54 Tower emhttpd: shcmd (1328): /usr/sbin/hdparm -S0 /dev/sdn Feb 1 20:55:54 Tower root: /dev/sdn: Feb 1 21:02:09 Tower emhttpd: shcmd (1802): mount -t btrfs -o noatime,nodiratime /dev/sdn1 /mnt/cache Feb 1 21:02:09 Tower kernel: BTRFS info (device sdn1): disk space caching is enabled Feb 1 21:02:09 Tower kernel: BTRFS info (device sdn1): has skinny extents Feb 1 21:02:10 Tower kernel: BTRFS info (device sdn1): enabling ssd optimizations Feb 1 21:02:10 Tower kernel: BTRFS error (device sdn1): parent transid verify failed on 141355253760 wanted 563611 found 563400 Feb 1 21:02:10 Tower kernel: BTRFS warning (device sdn1): failed to read log tree Feb 1 21:02:10 Tower root: mount: /mnt/cache: can't read superblock on /dev/sdn1. Feb 1 21:02:10 Tower kernel: BTRFS error (device sdn1): open_ctree failed Feb 1 21:04:04 Tower emhttpd: shcmd (1850): /usr/sbin/hdparm -y /dev/sdn Feb 1 21:04:04 Tower root: /dev/sdn: Feb 1 21:04:10 Tower emhttpd: shcmd (1851): /usr/sbin/hdparm -S0 /dev/sdn Feb 1 21:04:10 Tower root: /dev/sdn: Feb 1 21:05:57 Tower emhttpd: shcmd (1855): /usr/sbin/hdparm -y /dev/sdn Feb 1 21:05:57 Tower root: /dev/sdn: Feb 1 21:06:13 Tower emhttpd: shcmd (1857): /usr/sbin/hdparm -y /dev/sdn Feb 1 21:06:14 Tower root: /dev/sdn: Feb 1 21:06:34 Tower emhttpd: shcmd (1859): /usr/sbin/hdparm -y /dev/sdn Feb 1 21:06:34 Tower root: /dev/sdn: Feb 1 21:37:00 Tower emhttpd: shcmd (1920): /usr/sbin/hdparm -y /dev/sdn Feb 1 21:37:00 Tower root: /dev/sdn: Feb 1 21:37:05 Tower emhttpd: shcmd (1922): /usr/sbin/hdparm -y /dev/sdn tower-smart-20180201-2140.zip Edited February 2, 2018 by nicecube Quote Link to comment
JorgeB Posted February 2, 2018 Share Posted February 2, 2018 6 hours ago, nicecube said: parent transid verify failed on 141355253760 wanted 563611 found 563400 That's usually a fatal error, see here to try and recover your data before reformatting cache: https://lime-technology.com/forums/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490 Quote Link to comment
nicecube Posted February 2, 2018 Author Share Posted February 2, 2018 (edited) Ty for the help, i think the disk can't be repaired, this is the output of all command i have done. I think i ll buy a new SSD. This time i ll make a backup of all my docker in my array ... mount -o recovery,ro /dev/sdn1 /mnt/user/Backup/cachebck mount: /mnt/user/Backup/cachebck: wrong fs type, bad option, bad superblock on /dev/sdn1, missing codepage or helper program, or other error. btrfs restore -v /dev/sdn1 /mnt/user/Backup/cachebck No valid Btrfs found on /dev/sdn1 Could not open root, trying backup super No valid Btrfs found on /dev/sdn1 Could not open root, trying backup super ERROR: superblock bytenr 274877906944 is larger than device size 120034091008 Could not open root, trying backup super btrfs check --repair /dev/sdn1 enabling repair mode No valid Btrfs found on /dev/sdn1 ERROR: cannot open file system Edited February 2, 2018 by nicecube Quote Link to comment
JorgeB Posted February 2, 2018 Share Posted February 2, 2018 Try rebooting, and also post your diagnostics, before rebooting. Quote Link to comment
nicecube Posted February 2, 2018 Author Share Posted February 2, 2018 I include tower-diagnostics-20180202-0940 I ll reboot my server tower-diagnostics-20180202-0940.zip Quote Link to comment
JorgeB Posted February 2, 2018 Share Posted February 2, 2018 Nothing jumps out from the syslog but I'm finding it very strange that none of the recovery options work, try after rebooting. Quote Link to comment
nicecube Posted February 2, 2018 Author Share Posted February 2, 2018 I rebooted my server i tried the repair command again but i have the same output root@Tower:/# mount -o recovery,ro /dev/sdn1 /mnt/user/Backup/cachebck mount: /mnt/user/Backup/cachebck: wrong fs type, bad option, bad superblock on /dev/sdn1, missing codepage or helper program, or other error. root@Tower:/# btrfs restore -v /dev/sdn1 /mnt/user/Backup/cachebck No valid Btrfs found on /dev/sdn1 Could not open root, trying backup super No valid Btrfs found on /dev/sdn1 Could not open root, trying backup super ERROR: superblock bytenr 274877906944 is larger than device size 120034091008 Could not open root, trying backup super root@Tower:/# btrfs check --repair /dev/sdn1 enabling repair mode No valid Btrfs found on /dev/sdn1 ERROR: cannot open file system root@Tower:/# Quote Link to comment
JorgeB Posted February 2, 2018 Share Posted February 2, 2018 Looks like the superblock is damaged, you can try restore using a backup superblock: btrfs restore -v -u 2 /dev/sdn1 /mnt/user/Backup/cachebck Quote Link to comment
nicecube Posted February 2, 2018 Author Share Posted February 2, 2018 I got this message when im trying to do the command: root@Tower:/# btrfs restore -v -u 2 /dev/sdn1 /mnt/user/Backup/cachebck ERROR: superblock bytenr 274877906944 is larger than device size 120034091008 Could not open root, trying backup super root@Tower:/# Quote Link to comment
JorgeB Posted February 2, 2018 Share Posted February 2, 2018 Try the other backup superblock: btrfs restore -v -u 1 /dev/sdn1 /mnt/user/Backup/cachebck Quote Link to comment
nicecube Posted February 2, 2018 Author Share Posted February 2, 2018 This is the output of the above command: root@Tower:/# btrfs restore -v -u 1 /dev/sdn1 /mnt/user/Backup/cachebck No valid Btrfs found on /dev/sdn1 Could not open root, trying backup super ERROR: superblock bytenr 274877906944 is larger than device size 120034091008 Could not open root, trying backup super root@Tower:/# Quote Link to comment
JorgeB Posted February 2, 2018 Share Posted February 2, 2018 Can't help then, it's not usual for an unclean shutdown to damage a superblock, let alone all 3, but in any case you'll need to reformat the disk or ask for help from a btrfs maintainer on the mailing list: https://btrfs.wiki.kernel.org/index.php/Btrfs_mailing_list Quote Link to comment
nicecube Posted February 2, 2018 Author Share Posted February 2, 2018 I'm going to replace the SDD by a new Samsung, I'm no longer trust Kingston SSD. I'm reinstalling all my dockers, I have not lost important data just configurations that can be done again, thanks again for your help it was really appreciated,have a good day Quote Link to comment
JorgeB Posted February 2, 2018 Share Posted February 2, 2018 Before that you can also try btrfs check using the backup superblock: btrfs check -s 1 /dev/sdn1 Also try the lowmen mode which might give different result: btrfs check -s 1 --mode=lowmem /dev/sdn1 Quote Link to comment
nicecube Posted February 2, 2018 Author Share Posted February 2, 2018 root@Tower:/dev# btrfs check -s 1 /dev/sdn1 using SB copy 1, bytenr 67108864 No valid Btrfs found on /dev/sdn1 ERROR: cannot open file system root@Tower:/dev# btrfs check -s 1 --mode=lowmem /dev/sdn1 using SB copy 1, bytenr 67108864 No valid Btrfs found on /dev/sdn1 ERROR: cannot open file system root@Tower:/dev# Quote Link to comment
uniquegch Posted February 16, 2020 Share Posted February 16, 2020 hello everybody, I know that post is more than 2 years old. but I am having the same issue with two SSDs as RAID1 (as external USB Disk) for my SBC. on the USB Disk is BTRFS used as fs and while I just copied data yesterday it became slower till to the point it just stuck and didn't respond. My Linux system went in recovery mode and I can neither mount the disk nor do any of the check and rescue etc. Basic error message is always No valid Btrfs found on /dev/sda. In gparted it shows me that I am using 93 GB out of 450 GB. So this information is being proper shown. also the details are being shown properly in gparted. I will try doing more troubleshooting before I reformat that disk. Quote Link to comment
JorgeB Posted February 17, 2020 Share Posted February 17, 2020 15 hours ago, uniquegch said: My Linux system went in recovery mode and I can neither mount the disk nor do any of the check and rescue etc. Are you using Unraid? If yes you can post the diagnostics, if not this isn't a general Linux support forum. Quote Link to comment
EvilDoughnut Posted April 17, 2022 Share Posted April 17, 2022 Old thread I see but just came here to say I was just having exactly the same problem as OP, same errors - btrfs drive just would not get recognized and I tried all the steps in this thread. I thought it was done and dusted. Loaded up "sudo fdisk /dev/sdf" ready to format the drive, which threw up the following: Quote The device contains 'zfs_member' signature and it will be removed by a write command. See fdisk(8) man page and --wipe option for more detai ls. Device does not contain a recognized partition table. The size of this disk is 2.7 TiB (3000592982016 bytes). DOS partition table format cannot be used on drives for volumes larger than 21990232 55040 bytes for 512-byte sectors. Use GUID partition table format (GPT). Created a new DOS disklabel with disk identifier 0x078d2cf3. I hit "w" and wrote the change, then tried lsblk -f and the drive was assigned the correct label and UUID and became mountable. Quote Link to comment
Recommended Posts
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.