Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About oh-tomo

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well I can't login to the WD site. I can't rest my password on the WD site. And the WD site's customer portal apologizes for the inconvenience when my case details won't go through. And my email to wdsupport@wdc.com bounces back with "this email is not monitored, please use customer portal." And unRAID now says "Disk 6 in error state (disk dsbl)" This is the third time I've tried, the first with a new drive cage. But I guess the new drive cage ain't helping. Any other ideas?
  2. "Last smart test result: Completed without error" Now what? WDC_WD60EFRX-68MYMN1_WD-WX21DC43D5UZ-20190804-0808.txt
  3. So I got a new iStar dock and have now re-added this same HDD yesterday as a new disk and this morning I see a "Array has 1 disk with read errors" warning. How can the same HDD pass the WD Diagnostics extended test and then get read errors in unRAID, now connected via a brand new dock? Currently 10% into a SMART extended self-test of HDD.
  4. Tried to print for the first time in my Win 10 VM and Brother printer driver wouldn't install. Microsoft support suggested updating Windows because I wasn't on the latest Windows and the latest is supposed to have printer fixes, so we downloaded and ran the Microsoft Windows MediaCreation updater a few hours ago. Checked on it just now via VNC and screen is Tianocore over black. Forced stop VM (because normal stop didn't stop) and restarted to just see Tianocore and spinning dots over black for a while. Forced stop again and unchecked CPU 1 and 2 leaving 3 checked and 0 unchecked. Spinning dots frozen. Forced stop again and checked CPU 0 and unchecked 1-3. Two frozen dots on black Tianocore. (Four single CPUs) Any ideas? Back to CPUs 1-3 checked because then the dots were at least spinning? update: Went to CPUs 0-3 checked and unplugged all USB devices and finally got to blue update screen and spinning white dots with 90% "working on updates" message.
  5. New HDD in Disk 4 position working fine so far. Ran an extended test on the old HDD with WD Diagnostics in Windows (connected via USB 3.0 HDD dock) and it passed. So not sure why it got disabled twice in unRAID array if WD Diagnostics can't find a problem. I'll wait until new iStar dock arrives and add it as a new disk and see if it fails a third time.
  6. Disk 4 disabled again. Replaced with new disk and reconstruction started again. Still waiting for replacement iStar dock to arrive. I’ll feel safer adding more drives when that arrives.
  7. SMART extended self-test passed and reconstruction started. ETA 9 hours 23 minutes. While the test was running I went to the local computer store looking for a new 10TB drive and none were to be found. I guess that's a popular size. They had 14TB but that seemed like overkill since it was bigger than my parity or data drives so I bought a 12TB which I'll add as a second parity when the reconstruction is done.
  8. Powered down unRAID and checked the connections -- they seemed okay. Then checked slots in iStar dock where drive is in slot one. Noticed drive did not pop out easily when latch opened. Then noticed lever at back of dock slot not in place -- it was completely loose. So I moved the drive from iStar dock slot 1 to slot 4 and powered up. Disk 4 is still marked with a red x and disabled. Unraid notification appeared: Unraid array errors: 12-05-2019 00:53 Notice [SERVER2018] - array turned good Array has 0 disks with read errors Then I ran a SMART short self-test of Disk 4, results attached. Currently running SMART extended self-test and ordered a new iStar dock -- I didn't realize the back levers were so delicate. Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 30381 - server2018-smart-20190512-0114.zip
  9. Diagnostics attached. How should I proceed? Should I get a new drive? Unraid Disk 4 error: 09-05-2019 07:24 Alert (SERVER2018) - Disk 4 in error state (disk dsbl) server2018-diagnostics-20190511-1533.zip
  10. Use rclone-beta plugin (yes the plugin)......not the Docker Container. Then open a shell and type "rclone config" to begin your setup I've just installed the beta but I still only see rclone (not beta) in my plugin list. Should there be two rclones in the installed plugins tab -- rclone and rclone-beta? update: trying again after uninstalling rclone and installing rclone-beta
  11. Installing the virtio-win display driver is triggering the vm to crash -- neither Chicken of the VNC nor the unRAID built-in VNC viewer can log in. Is the crash because I installed my LSI 9300-8i card in the 8x slot where graphics cards usually go and the display driver setup is confused?
  12. Amidst initial Windows 10 setup of VM over VNC, went to Device Manager and selected Display adapters / Update drivers / Browse to drive E: for virtio-win disk and VNC connection aborted after selecting OK with reconnection refused. update: tried restarting VM which caused it to stop, so restarted VM and went through the Display adapter steps in top paragraph only to end in same VNC connection aborted scenario.
  13. That fits! Thanks! I notice the 2nd SATA port on the iStar cage is messed up -- looks like parts of that port and one cable got stuck inside one another. I guess I wasn't using the cable's latching/unlatching mechanism properly. Bypassing to 3rd SATA port for now.
  14. So I bought a LSI 9300-8i card (and SAS to SATA cable adapters) but it is 8x and my ASUS PRIME H310M-A motherboard has two PCI Express 2.0 x1 slots and one PCI Express 3.0/2.0 x16 slot. Are there LSI 1x cards or do I have to switch motherboards?
  15. When I run AJA System Test Lite I get 2 MB/sec on the write speed. Why is that so low? On the read side I'm getting 86 MB/sec which is better. That's wired. Then I got a TP-Link AV2000 2-port Gigabit Powerline Starter Kit (TL-PA9020 KIT) to see if I can eliminate cable runs between rooms and the 86 MB/sec read dropped to 11 MB/sec. (Write stayed at 2 MB/sec). Why is that? The TP-Link app says the speed between the powerline adapters is currently 644 Mbps. Shouldn't that translate into higher MB/sec read speeds with the AJA test?