Self-Test Execution Status: Īverage Powered On Per Power Cycle: 7.5 h Total Time To Complete Off-Line Data Collection: 0 s Ran this on a kubuntu live USB on a totally different x86 device (not OMV). It's almost a brand new drive (albeit I could be hitting the early part of the bathtub curve). Have you looked look at SMART data for the drive you think is / has failed?Įverything looks fine. The PSU is 15V/4A Power Supply × 1 from Ameridroid. The HC4 has 2 onboard drives (3.5" desktop HDDs) and the USB drive (2.5 inch) all drawing power. USB powered, usb3 "p10" WD black …20BBK-WESN/dp/B07VMTNDMK/ An HC4 recommends a 4amp supply, minimum, for two on-board drives.
The added NTFS hard drive - is it USB powered (by the HC4)? Or is it in a drive dock or, maybe, powered by a USB hub? (The reason why this is mentioned is powering hard drives can be problematic with SBC's. I have the original data so I'll copy it again. Phonerec was taking forever and doesn't give me filenames, so I killed it. I still don't plan on making the NAS my single point of failure, but recovering from backup errors is annoying, takes time, and puts strain on my other drives. I'm not concerned about the drive I just don't want this flaw to come back once I turn this into a real NAS and not a toy system. This is a huge error and I still don't know what caused it. It's going to take several days for 2 TB. Photorec / TestDisk on an x86 linux distro seems to be able to recover the files. TestDisk 7.0, Data Recovery Utility, April 2015 The Network LED for the odroid is blinking and there are vibrations and noise from the drive(s). Rebooted my router and none of the dhcp leases are for the odroid.
0 kommentar(er)
