December 31, 20223 yr Hi, I'd had 40+ days uptime but an i/o error so tried a reboot but now get an Unmountable disk present error. Diagnostics attached - would appreciate any suggestions. Strangely the array starts and nothing is emulated wopr-diagnostics-20221231-0327.zip Edited December 31, 20223 yr by folic86
December 31, 20223 yr Author 2 minutes ago, trurl said: Check filesystem on disk9 Quote Quote Phase 1 - find and verify superblock... - block cache size set to 1405232 entries Phase 2 - using internal log - zero log... zero_log: head block 2277807 tail block 2277803 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... agf_freeblks 2113990, counted 2130358 in ag 8 agf_freeblks 5972432, counted 5965260 in ag 1 sb_ifree 25068, counted 25065 sb_fdblocks 276419936, counted 294386184 - 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 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (1,227963528-227966967) only seen by one free space btree free space (1,227969448-227973179) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 2 - agno = 4 - agno = 5 - agno = 3 - agno = 6 - agno = 1 - agno = 0 - agno = 8 - agno = 10 - agno = 7 - agno = 9 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 setting reflink flag on inode 17181236961 Missing reference count record for (12/60941802) len 262096 count 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (2:2289784) is ahead of log (2:2277807). Would format log to cycle 5. No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Sat Dec 31 03:38:23 2022 Phase Start End Duration Phase 1: 12/31 03:37:47 12/31 03:37:47 Phase 2: 12/31 03:37:47 12/31 03:37:48 1 second Phase 3: 12/31 03:37:48 12/31 03:38:21 33 seconds Phase 4: 12/31 03:38:21 12/31 03:38:21 Phase 5: Skipped Phase 6: 12/31 03:38:21 12/31 03:38:23 2 seconds Phase 7: 12/31 03:38:23 12/31 03:38:23 Total run time: 36 seconds Ok, what is the best option now?
December 31, 20223 yr Community Expert Solution 5 minutes ago, folic86 said: No modify flag set Do it again without -n, if it asks for it add -L
December 31, 20223 yr Author Thanks @trurl - seems to have worked with -L. Will that have lost data though??
December 31, 20223 yr Community Expert 21 minutes ago, folic86 said: mounting the filesystem to replay the log The repair utility doesn't know Unraid already failed to mount the filesystem so no choice but to delete the log. Check if you have a lost+found share now
December 31, 20223 yr Author Nothing on the shares list, do I need to use terminal? Krusader also can't see one in the media folder where all other shares are.....
January 2, 20233 yr Author @trurl I rebooted again, and have the same disk as unmountable again. Any suggestions what I can do? Maybe swap the Sata cable? A data rebuild from parity?? wopr-diagnostics-20230102-0315.zip Edited January 2, 20233 yr by folic86
January 2, 20233 yr Community Expert Rebuild won't fix unmountable. On 12/30/2022 at 10:36 PM, trurl said: Check filesystem on disk9 Have you done memtest recently?
January 2, 20233 yr Author 4 minutes ago, trurl said: Rebuild won't fix unmountable. Have you done memtest recently? I have not. Can you remind me how?
January 2, 20233 yr Community Expert 28 minutes ago, folic86 said: I have not. Can you remind me how? It is an option on the Unraid boot menu. If you use UEFI boot then you should download the latest version from the memtest site and use that instead.
January 3, 20233 yr Author On 1/2/2023 at 4:06 AM, itimpi said: It is an option on the Unraid boot menu. If you use UEFI boot then you should download the latest version from the memtest site and use that instead. Great, thanks I am running that now. It took me a while as I forgot my cpu doesn't have inbuilt gfx and couldn't find my mini DP convertor for my P400 ahaha. Will post results when I get them.
January 4, 20233 yr Author 5 hours ago, folic86 said: Great, thanks I am running that now. It took me a while as I forgot my cpu doesn't have inbuilt gfx and couldn't find my mini DP convertor for my P400 ahaha. Will post results when I get them. So memtest passed with 0 errors. Any other suggestions @trurl @itimpi? Try the basic stuff like cables?
January 4, 20233 yr Community Expert Update to v6.11.5 and run xfs_repair again, then if it happens again to the same disk suggest backing it up and reformatting to create a new filesystem.
January 4, 20233 yr Author 4 hours ago, JorgeB said: Update to v6.11.5 and run xfs_repair again, then if it happens again to the same disk suggest backing it up and reformatting to create a new filesystem. How would I go about backing it up if it's unmountable?
January 4, 20233 yr Author @JorgeB so I did that and it gave me the same issue with the log as previously in the thread. I have run it as -L and it now mounts with no evidence on the drive of a lost+found. But this is the same place I was, before I had the same issue and had to restart all of this. So I'm still puzzled as to what is going on? If I try another restart in a few days, could I not just have the same issue?
January 4, 20233 yr Community Expert 10 minutes ago, folic86 said: But this is the same place I was, before 5 hours ago, JorgeB said: Update to v6.11.5 and run xfs_repair again, then if it happens again to the same disk suggest backing it up and reformatting to create a new filesystem.
January 19, 20233 yr Author On 1/4/2023 at 4:28 PM, JorgeB said: Hey Jorge, Same issue unfortunately again - reported 5206 udma errors, disabled the drive and on reboot is unmountable due to filesystem error, so I guess I need to back it up - is there an easy way? I don't have a spare sata port, but do (I think) have an 18tb drive
January 20, 20233 yr Community Expert Btrfs is also detecting data corruption, start by running memtest.
January 20, 20233 yr Author 5 minutes ago, JorgeB said: Btrfs is also detecting data corruption, start by running memtest. I've already done that. Didn't report any issues.
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.