JorgeB Posted September 20, 2023 Share Posted September 20, 2023 Diags are after rebooting so we can't see what happened, but based on this: 199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 44315 Replace the SATA cable. Quote Link to comment
Nanuk_ Posted September 20, 2023 Author Share Posted September 20, 2023 Replace the SATA Cable how do I get the HDD out of the disabled state though? Should I do a rebuild? Or Send another Diag?trojancarabao-diagnostics-20230920-2005.zip Quote Link to comment
Nanuk_ Posted September 20, 2023 Author Share Posted September 20, 2023 (edited) Still showing this: Can I ask which log file in the diag are you looking at? trojancarabao-diagnostics-20230920-2016.zip Edited September 20, 2023 by Nanuk_ Quote Link to comment
Nanuk_ Posted September 20, 2023 Author Share Posted September 20, 2023 Or should I just force a rebuild to remove this? Stop array Unassign drive Start array to make Unraid 'forget' assignment Stop array Assign drive Start array to initiate the rebuild Quote Link to comment
Nanuk_ Posted September 20, 2023 Author Share Posted September 20, 2023 (edited) Did the extended SMART check not have anything? Edited September 20, 2023 by Nanuk_ Quote Link to comment
trurl Posted September 20, 2023 Share Posted September 20, 2023 Emulated disk8 is mounted, extended SMART test passed. Should be OK to rebuild on top. Always try to get diagnostics BEFORE rebooting. Quote Link to comment
trurl Posted September 20, 2023 Share Posted September 20, 2023 33 minutes ago, Nanuk_ said: Can I ask which log file in the diag are you looking at? Several. They are all text files, you can examine them yourself. The smart folder contains SMART reports for all attached drives, and also shows that disk8 is disabled. The SMART report for disk8 shows that the extended test passed at 49 Power On Hours, just one hour less than the current value of that SMART attribute, so very recently. system/df.txt shows all mounted filesystems, you can see that disk8 is mounted and contains 904G data. system/vars.txt shows the state of all disks among other things. It says disk8 is disabled and mounted. In this case, it is the emulated disk that is mounted, and the contents of the emulated disk should be the result of rebuild. syslog is where I go to see I/O errors, but since you rebooted before getting diagnostics, nothing to see there. config folder in diagnostics is the settings from the webUI, including disk assignments. In other words, your configuration. It is all on flash, which is why you must always have a current backup of the flash drive. shares folder has your share settings, shareDisks.txt shows which disks they are on. Other things in system folder help figure out your hardware, which plugins you have, ... Quote Link to comment
trurl Posted September 20, 2023 Share Posted September 20, 2023 3 minutes ago, trurl said: In this case, it is the emulated disk that is mounted, and the contents of the emulated disk should be the result of rebuild. If the emulated disk was unmountable, then you would check filesystem on the emulated disk to try to get the filesystem repaired (mountable) before rebuilding. Quote Link to comment
Nanuk_ Posted September 20, 2023 Author Share Posted September 20, 2023 Ah I did xfs_repair after the extended SMART test and it still didn't mount. I'm doing a rebuild now. Luckily the drive didn't have that much data on it. So hopefully thing turn out okay. Thanks for the help @JorgeBand @trurl Quote Link to comment
JorgeB Posted September 20, 2023 Share Posted September 20, 2023 Post the output of xfs_repair -v Quote Link to comment
trurl Posted September 20, 2023 Share Posted September 20, 2023 1 hour ago, Nanuk_ said: did xfs_repair after the extended SMART test and it still didn't mount. The most recent Diagnostics you posted showed 3 hours ago, trurl said: Emulated disk8 is mounted Quote Link to comment
Nanuk_ Posted September 21, 2023 Author Share Posted September 21, 2023 Ah darn I already started the rebuild last night. I'll run and xfs_repair -v /dev/md8p1 after it's done rebuilding. Quote Link to comment
itimpi Posted September 21, 2023 Share Posted September 21, 2023 6 minutes ago, Nanuk_ said: I'll run and xfs_repair -v /dev/md8p1 after it's done rebuilding. It is normally better to run it from the GUI if at all possible and it is easy to make a mistake with the command when running it via the command line. Quote Link to comment
trurl Posted September 21, 2023 Share Posted September 21, 2023 5 hours ago, Nanuk_ said: Ah darn I already started the rebuild last night. Are you saying the drive became unmountable after those diagnostics I looked at? Quote Link to comment
Nanuk_ Posted September 22, 2023 Author Share Posted September 22, 2023 21 hours ago, itimpi said: It is normally better to run it from the GUI if at all possible and it is easy to make a mistake with the command when running it via the command line. Sorry how do I run it from gui. I didn't want to ask but a google search only yielded the CLI version. Quote Link to comment
itimpi Posted September 22, 2023 Share Posted September 22, 2023 1 hour ago, Nanuk_ said: Sorry how do I run it from gui. I didn't want to ask but a google search only yielded the CLI version. It is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. Quote Link to comment
Nanuk_ Posted September 22, 2023 Author Share Posted September 22, 2023 (edited) She's throwing errors again. Is it the cable or should I just RMA the drive? I'm starting to think it's the HBA that's borked, but I took it out and I can't seem to find any damage/singeing. trojancarabao-diagnostics-20230922-1445.zip Edited September 22, 2023 by Nanuk_ Quote Link to comment
Nanuk_ Posted September 22, 2023 Author Share Posted September 22, 2023 (edited) Finally found the section of the document that teach it. Thanks @itimpi Ran it with a -v flag Phase 1 - find and verify superblock... - block cache size set to 687056 entries Phase 2 - using internal log - zero log... zero_log: head block 25663 tail block 25663 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and 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 - 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 = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 5 - agno = 1 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Fri Sep 22 15:08:29 2023 Phase Start End Duration Phase 1: 09/22 15:08:27 09/22 15:08:27 Phase 2: 09/22 15:08:27 09/22 15:08:28 1 second Phase 3: 09/22 15:08:28 09/22 15:08:28 Phase 4: 09/22 15:08:28 09/22 15:08:28 Phase 5: 09/22 15:08:28 09/22 15:08:29 1 second Phase 6: 09/22 15:08:29 09/22 15:08:29 Phase 7: 09/22 15:08:29 09/22 15:08:29 Total run time: 2 seconds done Edited September 22, 2023 by Nanuk_ Quote Link to comment
itimpi Posted September 22, 2023 Share Posted September 22, 2023 23 minutes ago, Nanuk_ said: Finally found the section of the document that teach it. Thanks @itimpi Ran it with a -v flag Phase 1 - find and verify superblock... - block cache size set to 687056 entries Phase 2 - using internal log - zero log... zero_log: head block 25663 tail block 25663 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and 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 - 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 = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 5 - agno = 1 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Fri Sep 22 15:08:29 2023 Phase Start End Duration Phase 1: 09/22 15:08:27 09/22 15:08:27 Phase 2: 09/22 15:08:27 09/22 15:08:28 1 second Phase 3: 09/22 15:08:28 09/22 15:08:28 Phase 4: 09/22 15:08:28 09/22 15:08:28 Phase 5: 09/22 15:08:28 09/22 15:08:29 1 second Phase 6: 09/22 15:08:29 09/22 15:08:29 Phase 7: 09/22 15:08:29 09/22 15:08:29 Total run time: 2 seconds done That looks good. When you start the array in normal mode does it now mount OK and show the expected contents? It is what is shown on the emulated drive that is what you would end up with after a rebuild. Quote Link to comment
Nanuk_ Posted September 22, 2023 Author Share Posted September 22, 2023 Looks normal now, no emulation. But if errors start happening again. Do I just repeat the procedure? What what point should I RMA? Quote Link to comment
itimpi Posted September 22, 2023 Share Posted September 22, 2023 23 minutes ago, Nanuk_ said: Looks normal now, no emulation. But if errors start happening again. Do I just repeat the procedure? What what point should I RMA? The only time it is definite that you should RMA is if a drive starts failing the Extended SMART test as cable issues are by far the most common cause of situations like this However if a fault follows a drive even after things like cable swaps then maybe it is also time to RMA the drive. Quote Link to comment
Nanuk_ Posted September 22, 2023 Author Share Posted September 22, 2023 Okay, thanks for much for clearing that up @itimpi, my HDD supplier will probably thank you for that cause I've RMA'd like 3 drives just this year because of slight errors. Quote Link to comment
JorgeB Posted September 22, 2023 Share Posted September 22, 2023 LSISAS2308: FWVersion(20.00.00.00), Update the LSI firmware to 20.00.07.00, this one has multiple known issues. Quote Link to comment
Nanuk_ Posted September 23, 2023 Author Share Posted September 23, 2023 Thanks @JorgeB Any chance you know a good tutorial for this bit? I have Krusader setup using Space Invader One's walk through but I don't know how to copy them to the flashdrive/bootdrive (I believe you mean the Unraid flashdrive). Sorry his video doesn't teach how to move a file there and your walkthrough assumes I know how. Quote Link to comment
Nanuk_ Posted September 23, 2023 Author Share Posted September 23, 2023 (edited) I think I found his old walkthrough how to add the boot drive but I think it is no longer valid. It's timestamped. He basically says to add the /boot/ in Host Path: but it doesn't seem to be the path for the flash drive anymore. I'm assuming the video is too old (see bottom of post). I'm trying to search the forums for it but haven't found the flash drive path yet. Or is it a permissions that I have to change to allow me to access it? Going to try running "Docker Safe New Permissions" to see if that works. Edited September 23, 2023 by Nanuk_ 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.