July 6, 20232 yr Hey! So I went to go and restart one of my docker containers, and it spit out an error, so I tired to update it, but then it spat out another error. So I decided to restart the server, but when it posted, I was greeted with the tragic Unmountable disk present: Cache (sdd1) error. I tried to see what the error was, but I'm only in my first year of CS school, so no luck. I also tried unplugging both ends of the sata power and data in, with no avail. Below is something maybe useful, if not, the full logs are attached. Thanks to whoever decides to even look at this case Jul 5 22:09:27 DarthVader kernel: BTRFS error (device sdd1): incorrect extent count for 24718082048; counted 5503, expected 5502 Jul 5 22:09:27 DarthVader kernel: BTRFS: error (device sdd1) in btrfs_replay_log:2414: errno=-5 IO failure (Failed to recover log tree) Jul 5 22:09:27 DarthVader kernel: BTRFS error (device sdd1: state E): open_ctree failed Jul 5 22:09:27 DarthVader root: mount: /mnt/cache: can't read superblock on /dev/sdd1. Jul 5 22:09:27 DarthVader root: dmesg(1) may have more information after failed mount system call. Jul 5 22:09:27 DarthVader emhttpd: shcmd (49): exit status: 32 Jul 5 22:09:27 DarthVader emhttpd: /mnt/cache mount error: Unsupported or no file system darthvader-diagnostics-20230706-0008.zip
July 6, 20232 yr Community Expert If the log tree is the only problem this may help: btrfs rescue zero-log /dev/sdd1
July 6, 20232 yr 50 minutes ago, JorgeB said: If the log tree is the only problem this may help: btrfs rescue zero-log /dev/sdd1 I had a similar error, JorgeB's solution above worked for me. Restart the array after you have run the above command in the terminal.
July 7, 20232 yr Author Hmmmm, so I did that, but now it seems to let the array start with it, but then only lets the cache drive act in a read only mode. I restart the array and then the "Unmountable disk present" comes back. Any suggestions?!? ?Would it be a bad idea to try:? btrfs check --repair /dev/sdd1 New logs attached. darthvader-diagnostics-20230706-2159.zip And here's the btrfs check status for the drive: [1/7] checking root items [2/7] checking extents tree extent[9551872, 16384] root 2199023255554 has no tree block found tree extent[9551872, 16384] root 2 has no backref item in extent tree incorrect global backref count on 9551872 found 2 wanted 1 backpointer mismatch on [9551872 16384] ref mismatch on [18227200 4096] extent item 2199023255553, found 1 tree extent[152092672, 16384] root 7 has no backref item in extent tree tree extent[152092672, 16384] root 2199023255559 has no tree block found incorrect global backref count on 152092672 found 2 wanted 1 backpointer mismatch on [152092672 16384] tree extent[1093713920, 16384] root 7 has no backref item in extent tree tree extent[1093713920, 16384] root 2199023255559 has no tree block found incorrect global backref count on 1093713920 found 2 wanted 1 backpointer mismatch on [1093713920 16384] ref mismatch on [24721977344 4096] extent item 2199023255553, found 1 ref mismatch on [24855019520 4096] extent item 2199023255553, found 1 ref mismatch on [24860209152 16384] extent item 2199023255553, found 1 ref mismatch on [24987209728 4096] extent item 2199023255553, found 1 ref mismatch on [25040871424 81920] extent item 2199023255553, found 1 ERROR: invalid generation for extent 25110953984, have 2199028982132 expect (0, 5726902] ref mismatch on [120194207744 565248] extent item 2199023255553, found 1 ERROR: errors found in extent allocation tree or chunk allocation [3/7] checking free space tree free space info recorded 83 extents, counted 84 There are still entries left in the space cache cache appears valid but isn't 13631488 free space info recorded 5502 extents, counted 5503 There are still entries left in the space cache cache appears valid but isn't 24718082048 free space info recorded 1861 extents, counted 1862 There are still entries left in the space cache cache appears valid but isn't 29013049344 [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdd1 UUID: 379d2adb-c393-4dc8-b1b6-c5e33b0eb77d found 67234181120 bytes used, error(s) found total csum bytes: 43489204 total tree bytes: 148865024 total fs tree bytes: 78905344 total extent tree bytes: 10371072 btree space waste bytes: 38937740 file data blocks allocated: 142248374272 referenced 67044220928 Edited July 7, 20232 yr by popcicle2003
July 7, 20232 yr Community Expert Pool has other issues, it's not just a bad log tree, you can see here for some recovery options, then pool should be recreated.
July 8, 20232 yr Author Solution Ok, I created a backup of the cache on my main array. I then ran btrfs check --repair /dev/sdd1 and it seems to have worked™. We will see if it holds, but if not, yeah, I might have to format and recreate the pool. Thanks guys for the help! (Slso for anyone who might have a similar issue, it's not too late to make a backup of your cache before you mess with stuff)!!!
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.