Nanuk_

Noted, hmmm guess I need to decide if I want to switch or not.

Ah! Thanks for clearing that up! That really helps! Thanks chief!

I was referring to the I believe was a promo that I missed out on.

Sadly not for $19 anymore. It's now at $69. Which may no be that cost efficient for me as I can only fit 3 more drives in my NAS.

Oh man, I just saw this. Is there going to be an extension? I want to upgrade my plus license.

Nevermind, I was able to restore off of the USB by copying the contents of the "Previous" folder and overwriting the root of the Unraid USB stick. Please note I'm from the set of users that have a " Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller" and am using the drivers from the " "

Hello I just updated to stable 6.12.8 and am now regretting it. Whatever fix for realtek drivers you had broke mine. Now unraid doesn't detect my network card and I need to figure out how to rollback from 6.12.8 to the 6.12.6.

I think I got it to work. Did a reboot and version 20.00.07.00 in the bios. Thank @itimpi that explains why I can't load the flashdrive in krusader.

Nvm I think I found the paths: /mnt/disks/MSI_DISK/lsi /boot/lsi Going to try your walkthrough now.

Yup that didn't work.

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.

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.

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.

Looks normal now, no emulation. But if errors start happening again. Do I just repeat the procedure? What what point should I RMA?

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

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

Sorry how do I run it from gui. I didn't want to ask but a google search only yielded the CLI version.

Ah darn I already started the rebuild last night. I'll run and xfs_repair -v /dev/md8p1 after it's done rebuilding.

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

Did the extended SMART check not have anything?

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

Still showing this: Can I ask which log file in the diag are you looking at? trojancarabao-diagnostics-20230920-2016.zip

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

Sorry, was waiting for the extended smart test to finish. trojancarabao-diagnostics-20230920-1900.ziptrojancarabao-smart-20230920-1900.zip

ATA Error Count: 44315 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 44315 occurred at disk power-on lifetime: 30 hours (1 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 41 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 e0 08 a8 bc b9 40 00 1d+06:57:46.041 READ FPDMA QUEUED 2f 00 01 10 00 00 00 00 1d+06:57:46.041 READ LOG EXT 60 00 50 b8 c9 b9 40 00 1d+06:57:45.929 READ FPDMA QUEUED 60 40 70 78 c7 b9 40 00 1d+06:57:45.928 READ FPDMA QUEUED 60 18 68 60 c7 b9 40 00 1d+06:57:45.928 READ FPDMA QUEUED Error 44314 occurred at disk power-on lifetime: 30 hours (1 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 41 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 80 18 c8 bb b9 40 00 1d+06:57:45.898 READ FPDMA QUEUED 2f 00 01 10 00 00 00 00 1d+06:57:45.898 READ LOG EXT 61 00 a0 50 ae b9 40 00 1d+06:57:45.892 WRITE FPDMA QUEUED 61 c0 00 90 ad b9 40 00 1d+06:57:45.891 WRITE FPDMA QUEUED 60 c0 a0 90 ad b9 40 00 1d+06:57:45.883 READ FPDMA QUEUED Error 44313 occurred at disk power-on lifetime: 30 hours (1 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 41 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 c0 38 90 ad b9 40 00 1d+06:57:45.882 READ FPDMA QUEUED 2f 00 01 10 00 00 00 00 1d+06:57:45.882 READ LOG EXT 60 c0 b0 d0 bd b9 40 00 1d+06:57:45.865 READ FPDMA QUEUED 60 48 a8 88 bd b9 40 00 1d+06:57:45.864 READ FPDMA QUEUED 60 e0 b8 a8 bc b9 40 00 1d+06:57:45.862 READ FPDMA QUEUED Error 44312 occurred at disk power-on lifetime: 30 hours (1 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 41 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 28 68 c0 ac b9 40 00 1d+06:57:45.856 READ FPDMA QUEUED 2f 00 01 10 00 00 00 00 1d+06:57:45.856 READ LOG EXT 61 38 78 a0 ab b9 40 00 1d+06:57:45.847 WRITE FPDMA QUEUED 60 08 c8 c0 bb b9 40 00 1d+06:57:45.841 READ FPDMA QUEUED 60 08 c8 98 4c 45 40 00 1d+06:57:45.841 READ FPDMA QUEUED Error 44311 occurred at disk power-on lifetime: 30 hours (1 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 41 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 38 60 a0 ab b9 40 00 1d+06:57:45.789 READ FPDMA QUEUED 2f 00 01 10 00 00 00 00 1d+06:57:45.789 READ LOG EXT 60 08 10 68 b2 b9 40 00 1d+06:57:45.778 READ FPDMA QUEUED 60 08 10 b0 46 45 40 00 1d+06:57:45.778 READ FPDMA QUEUED 60 08 10 a0 45 45 40 00 1d+06:57:45.778 READ FPDMA QUEUED