Unraid_Pi Posted October 22, 2023 Share Posted October 22, 2023 After reverting OS back from 6.12.4 to 6.11.5, my data disc became "unmountable" status. (1 data disc, 1 parity disc) Any chance to recover the data on the disc? tower-diagnostics-20231022-0212.zip Quote Link to comment
itimpi Posted October 22, 2023 Share Posted October 22, 2023 Have you followed the process here for handling unmountable disks in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release. Quote Link to comment
JorgeB Posted October 22, 2023 Share Posted October 22, 2023 Also change you docker network to ipvlan. Quote Link to comment
Unraid_Pi Posted October 22, 2023 Author Share Posted October 22, 2023 Ok, I will give it a try and post an update here. Thanks. Quote Link to comment
Unraid_Pi Posted October 23, 2023 Author Share Posted October 23, 2023 I ran the Check Filesystem and below is the log. Should I go ahead and run repairing file system? Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 1 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (1:937421) is ahead of log (1:936905). Would format log to cycle 4. No modify flag set, skipping filesystem flush and exiting. Quote Link to comment
Unraid_Pi Posted October 23, 2023 Author Share Posted October 23, 2023 Update: I ran the check repair with "-L" option, then I re-started the array. It recovers the folders, but most data are gone. Posting the repair log below. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x44108d, xfs_bnobt block 0x280e43488/0x1000 btree block 5/1869462 is suspect, error -74 bad magic # 0 in btbno block 5/1869462 Metadata CRC error detected at 0x44108d, xfs_bnobt block 0x1077388b0/0x1000 btree block 2/15626520 is suspect, error -74 bad magic # 0xfcbc7c09 in btbno block 2/15626520 Metadata CRC error detected at 0x44108d, xfs_bnobt block 0x180588698/0x1000 btree block 3/725206 is suspect, error -74 bad magic # 0xd678e519 in btbno block 3/725206 Metadata CRC error detected at 0x44108d, xfs_bnobt block 0x302c6aeb8/0x1000 btree block 6/5821917 is suspect, error -74 bad magic # 0 in btbno block 6/5821917 Metadata CRC error detected at 0x44108d, xfs_bnobt block 0x386ce8500/0x1000 btree block 7/14274727 is suspect, error -74 bad magic # 0x424d4133 in btbno block 7/14274727 Metadata CRC error detected at 0x44108d, xfs_bnobt block 0x20df75db0/0x1000 btree block 4/29289402 is suspect, error -74 bad magic # 0xf20dc4ff in btbno block 4/29289402 Metadata CRC error detected at 0x44108d, xfs_cntbt block 0x302c6aec0/0x1000 btree block 6/5821918 is suspect, error -74 bad magic # 0 in btcnt block 6/5821918 Metadata CRC error detected at 0x44108d, xfs_cntbt block 0x3903a84f8/0x1000 btree block 7/34033830 is suspect, error -74 bad magic # 0x424d4133 in btcnt block 7/34033830 Metadata CRC error detected at 0x44108d, xfs_cntbt block 0x2004efc40/0x1000 btree block 4/647052 is suspect, error -74 bad magic # 0x491cdf76 in btcnt block 4/647052 Metadata CRC error detected at 0x4728bd, xfs_refcountbt block 0x302e57ab8/0x1000 btree block 6/6074205 is suspect, error -74 bad magic # 0 in refcount btree block 6/6074205 bad refcountbt block count 0, saw 1 agf_freeblks 213292643, counted 0 in ag 6 agf_longest 213096795, counted 0 in ag 6 Metadata CRC error detected at 0x4728bd, xfs_refcountbt block 0x20df75d18/0x1000 btree block 4/29289383 is suspect, error -74 bad magic # 0x875cd072 in refcount btree block 4/29289383 bad refcountbt block count 0, saw 1 agf_freeblks 241373574, counted 0 in ag 4 agf_longest 231902952, counted 0 in ag 4 Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0x3006aa7b8/0x1000 btree block 6/873725 is suspect, error -74 bad magic # 0 in inobt block 6/873725 Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0x200b23e10/0x1000 btree block 4/1460166 is suspect, error -74 bad magic # 0x5c0053b8 in inobt block 4/1460166 Metadata CRC error detected at 0x46fd5d, xfs_finobt block 0x302d0fbc8/0x1000 btree block 6/5906303 is suspect, error -74 bad magic # 0 in finobt block 6/5906303 agi_count 3584, counted 0 in ag 6 agi_freecount 13, counted 0 in ag 6 agi_freecount 13, counted 0 in ag 6 finobt Metadata CRC error detected at 0x44108d, xfs_cntbt block 0x108cec388/0x1000 btree block 2/18471027 is suspect, error -74 bad magic # 0x2a583e0 in btcnt block 2/18471027 Metadata CRC error detected at 0x4728bd, xfs_refcountbt block 0x107738858/0x1000 btree block 2/15626509 is suspect, error -74 bad magic # 0x122b49e in refcount btree block 2/15626509 bad refcountbt block count 0, saw 1 agf_freeblks 196128181, counted 0 in ag 2 agf_longest 195969725, counted 0 in ag 2 Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0x100630e10/0x1000 btree block 2/811460 is suspect, error -74 bad magic # 0xe114252e in inobt block 2/811460 Metadata CRC error detected at 0x46fd5d, xfs_finobt block 0x103c84ee8/0x1000 btree block 2/7932383 is suspect, error -74 bad magic # 0xc8916251 in finobt block 2/7932383 agi_count 4352, counted 0 in ag 2 agi_freecount 42, counted 0 in ag 2 agi_freecount 42, counted 0 in ag 2 finobt Metadata CRC error detected at 0x44108d, xfs_bnobt block 0x805ec1a0/0x1000 btree block 1/776245 is suspect, error -74 bad magic # 0x323618de in btbno block 1/776245 Metadata CRC error detected at 0x4728bd, xfs_refcountbt block 0x150ba080/0x1000 btree block 0/44135440 is suspect, error -74 bad magic # 0x8f031873 in refcount btree block 0/44135440 bad refcountbt block count 0, saw 1 Metadata CRC error detected at 0x44108d, xfs_cntbt block 0x180650e60/0x1000 btree block 3/827855 is suspect, error -74 bad magic # 0xa81fb5f6 in btcnt block 3/827855 Metadata CRC error detected at 0x46fd5d, xfs_finobt block 0x208f17dd8/0x1000 btree block 4/18755519 is suspect, error -74 bad magic # 0x48321108 in finobt block 4/18755519 agi_count 4032, counted 0 in ag 4 agi_freecount 42, counted 0 in ag 4 agi_freecount 42, counted 0 in ag 4 finobt Metadata CRC error detected at 0x44108d, xfs_cntbt block 0x28213ac50/0x1000 btree block 5/4355471 is suspect, error -74 bad magic # 0 in btcnt block 5/4355471 Metadata corruption detected at 0x4726c0, xfs_refcountbt block 0x38132b000/0x1000 btree block 7/2512391 is suspect, error -117 bad magic # 0x41423342 in refcount btree block 7/2512391 bad refcountbt block count 0, saw 1 agf_freeblks 8025413, counted 0 in ag 7 agf_longest 4455209, counted 0 in ag 7 agf_btreeblks 6, counted 0 in ag 7 Metadata CRC error detected at 0x44108d, xfs_cntbt block 0x80deec88/0x1000 btree block 1/1826194 is suspect, error -74 bad magic # 0x68747470 in btcnt block 1/1826194 Metadata CRC error detected at 0x4728bd, xfs_refcountbt block 0x18022b5a0/0x1000 btree block 3/284343 is suspect, error -74 bad magic # 0x93aebd4f in refcount btree block 3/284343 bad refcountbt block count 0, saw 1 agf_freeblks 242085895, counted 0 in ag 3 agf_longest 242061326, counted 0 in ag 3 Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0x180000040/0x1000 btree block 3/11 is suspect, error -74 bad magic # 0xc3319bf9 in inobt block 3/11 Metadata CRC error detected at 0x4728bd, xfs_refcountbt block 0x2809c97c8/0x1000 btree block 5/1282814 is suspect, error -74 bad magic # 0 in refcount btree block 5/1282814 bad refcountbt block count 0, saw 1 agf_freeblks 238039766, counted 0 in ag 5 agf_longest 237867577, counted 0 in ag 5 Metadata corruption detected at 0x46fc78, xfs_inobt block 0x380186c80/0x1000 btree block 7/200087 is suspect, error -117 bad magic # 0x41423343 in inobt block 7/200087 Metadata CRC error detected at 0x4728bd, xfs_refcountbt block 0x804248a0/0x1000 Metadata CRC error detected at 0x46fd5d, xfs_finobt block 0x180103f98/0x1000 btree block 3/133110 is suspect, error -74 bad magic # 0x4c5b3012 in finobt block 3/133110 btree block 1/542997 is suspect, error -74 agi_count 3008, counted 0 in ag 3 agi_freecount 12, counted 0 in ag 3 agi_freecount 12, counted 0 in ag 3 finobt bad magic # 0x3d6ab5b3 in refcount btree block 1/542997 bad refcountbt block count 0, saw 1 agf_freeblks 22622799, counted 0 in ag 1 agf_longest 19495401, counted 0 in ag 1 Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0x80000060/0x1000 btree block 1/13 is suspect, error -74 bad magic # 0x58444233 in inobt block 1/13 Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0x28092aa88/0x1000 btree block 5/1201494 is suspect, error -74 bad magic # 0 in inobt block 5/1201494 Metadata corruption detected at 0x46fc78, xfs_finobt block 0x3801ddc78/0x1000 btree block 7/244630 is suspect, error -117 bad magic # 0x41423342 in finobt block 7/244630 agi_count 4736, counted 0 in ag 7 agi_freecount 68, counted 0 in ag 7 agi_freecount 68, counted 0 in ag 7 finobt Metadata CRC error detected at 0x46fd5d, xfs_finobt block 0x28097b048/0x1000 btree block 5/1242638 is suspect, error -74 bad magic # 0 in finobt block 5/1242638 agi_count 3648, counted 0 in ag 5 agi_freecount 23, counted 0 in ag 5 agi_freecount 23, counted 0 in ag 5 finobt Metadata CRC error detected at 0x46fd5d, xfs_inobt block 0x6bb6760/0x1000 btree block 0/14118124 is suspect, error -74 bad magic # 0xa4aa9d04 in inobt block 0/14118124 Metadata CRC error detected at 0x46fd5d, xfs_finobt block 0x800bed70/0x1000 btree block 1/97711 is suspect, error -74 bad magic # 0x9c97dbd7 in finobt block 1/97711 agi_count 3264, counted 0 in ag 1 agi_freecount 20, counted 0 in ag 1 agi_freecount 20, counted 0 in ag 1 finobt Metadata CRC error detected at 0x46fd5d, xfs_finobt block 0x8a13378/0x1000 btree block 0/18097775 is suspect, error -74 bad magic # 0x1288e8be in finobt block 0/18097775 agi_count 3456, counted 0 in ag 0 agi_freecount 37, counted 0 in ag 0 agi_freecount 37, counted 0 in ag 0 finobt sb_icount 30080, counted 0 sb_ifree 257, counted 0 sb_fdblocks 1376581299, counted 215013022 root inode chunk not found Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap correcting imap - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 5 - agno = 4 - agno = 7 - agno = 3 - agno = 6 - agno = 1 entry "BT" in shortform directory 128 references non-existent inode 17821005 junking entry "BT" in directory inode 128 entry "isos" in shortform directory 128 references non-existent inode 140840373 junking entry "isos" in directory inode 128 entry "domains" in shortform directory 128 references non-existent inode 6498036969 junking entry "domains" in directory inode 128 entry "UnRAID" in shortform directory 128 references non-existent inode 140840380 junking entry "UnRAID" in directory inode 128 entry "Private Backup" in shortform directory 128 references non-existent inode 6504089926 junking entry "Private Backup" in directory inode 128 entry "backups" in shortform directory 128 references non-existent inode 4428694024 junking entry "backups" in directory inode 128 entry "system" in shortform directory 128 references non-existent inode 8825581612 junking entry "system" in directory inode 128 corrected i8 count in directory 128, was 4, now 0 corrected directory 128 size, was 27, now 19 entry "Pics and Video" in shortform directory 131 references non-existent inode 2147483776 junking entry "Pics and Video" in directory inode 131 entry "Music" in shortform directory 131 references non-existent inode 136743310 junking entry "Music" in directory inode 131 entry "Movie" in shortform directory 131 references non-existent inode 4419979442 junking entry "Movie" in directory inode 131 entry ".DS_Store" in shortform directory 131 references non-existent inode 144811673 junking entry ".DS_Store" in directory inode 131 entry "._.DS_Store" in shortform directory 131 references non-existent inode 144811674 junking entry "._.DS_Store" in directory inode 131 corrected i8 count in directory 131, was 1, now 0 corrected directory 131 size, was 10, now 6 entry ".." at block 0 offset 80 in directory inode 132 references non-existent inode 15032385664 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... fixing ftype mismatch (0/2) in directory/child inode 128/131 entry ".." in directory inode 132 points to non-existent inode 15032385664 bad hash table for directory inode 132 (no data entry): rebuilding rebuilding directory inode 132 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 132, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 128 nlinks from 11 to 4 resetting inode 131 nlinks from 5 to 2 resetting inode 1952896 nlinks from 2 to 3 Maximum metadata LSN (2107695393:-1244259813) is ahead of log (4:0). Format log to cycle 2107695396. done Quote Link to comment
JorgeB Posted October 23, 2023 Share Posted October 23, 2023 Look for a lost+found folder, if the missing data isn't there you'll need to restore from a backup. Quote Link to comment
itimpi Posted October 23, 2023 Share Posted October 23, 2023 Do you have a lost+found folder on the drive that is full of folder/files with cryptic names (which will result in a share of that name showing up on the Shares tab)? That is where the repair process puts any folders/files for which it cannot find the directory entry to give the correct name. Unfortunately sorting these out is a manual process, although the Linux file command can be useful to at least give you the likely extension for each file. You have to decide if the effort is worth it, but if you have decent backups it is normally easier to restore from them. Quote Link to comment
Unraid_Pi Posted October 23, 2023 Author Share Posted October 23, 2023 Yes, there is a lost+found folder, but only 1% files has been recovered there. I guess I have to use backup to recover. Thanks guys. Quote Link to comment
Unraid_Pi Posted October 23, 2023 Author Share Posted October 23, 2023 On 10/22/2023 at 5:37 AM, JorgeB said: Also change you docker network to ipvlan. How do I change my docker network to ipvlan? I am in setting but it wasn't editable. Quote Link to comment
Solution JorgeB Posted October 23, 2023 Solution Share Posted October 23, 2023 You need to stop the docker service first. Quote Link to comment
Unraid_Pi Posted October 23, 2023 Author Share Posted October 23, 2023 Thanks guys. Solution: rebuild from backup 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.