Jump to content

sonofdbn

Members
  • Content Count

    279
  • Joined

  • Last visited

Everything posted by sonofdbn

  1. I get the disk being rewritten, but wasn't sure about the additional capacity - does the rebuilding of the data onto the larger disk then just automatically clear the additional capacity?
  2. Unfortunately the drive is in the array, so preclearing or anything destructive is going to erase the data on it. I think I might replace the drive anyway with a larger one that I have, and then use it somewhere else (after some testing).
  3. I'm on unRAID 6.19, and one of my data disks failed a SMART test. It's a 1.5TB disk, and I want to replace it with a new 4TB disk (same size as parity). I have already tested the new drive quite thoroughly using WD Digital Lifeguard Diagnostics. Should I still run a preclear on the new disk before using it to replace the smaller one?
  4. Well, what do you know? Dug out an old Windows 7 PC, ran Full Erase Write Zeros and the HGST drive passed with no errors! Thanks, garycase. I would never have thought that the USB interface would be at fault. I'm calling this drive OK: it's been through two Quick Tests and two Extended Tests and now it's passed the Full Erase Write Zeros test. Valuable lesson learned: test my drives on native SATA.
  5. In my unRAID array I have a 1.5TB data drive that showed some read errors after, I think, a parity check. I finally got round to running a SMART self-test, but don't know how to interpret the results. Near the start of the report it says: === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Near the end it says: SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 40% 2639 2129605537 Should the disk be replaced? It doesn't have a "red ball"; it's still showing green.
  6. OK, the Extended Test passed again, but the Full Erase Write Zeros failed again - after about 3 hours. If it's a USB interface anomaly, I would have thought that after this it should consistently fail after this point. However, I've restarted the Full Erase Write Zeros test again, and it's trundling along just fine. But still, perhaps using a pure native SATA connection will be the definitive test. I'm going to have to do some fiddling around with old PCs and spare parts, so this might take a while.
  7. Thanks for the suggestions. I'll post back here once the various tests are done.
  8. The laptop is set to never sleep. Unfortunately the USB kludge is all I can use without major PC disassembly, but I suppose that might have to be the next step.
  9. No, I don't think I've initialised the disk, and definitely did not create a partition. I just took the disk out of the packaging and connected it to a laptop using a SATA-to-USB 3 adapter. (The laptop is set to never sleep.) I should have mentioned that the write zeros failed when I did a full write zeros test; after that I tried the Quick Erase write zeros test, and that passed. Then I did another Quick Test, which was OK,and now in about 6 hours the Extended Test will be completed. When I ran the full write zeros test, it seemed to run fine for quite some time. I watched it when it started, and then left it to run. I checked it again a few hours later, and there were no error messages. Then I went out for a while and when I got back I saw the error message. The progress bar was about 1/3 to 1/2 way through. So it doesn't look as if the write zeros failed immediately.
  10. I just purchased a 4TB HGST Deskstar NAS and ran the WD Digital Lifeguard Diagnostics on it. It passed the Quick Test and Extended Test, but came up with lots of errors in the Write Zeros test. (I got tired of hitting continue after each error...). So I tried Quick Test again (OK) and am now running the Extended Test again, which is going to take a lot of time. Since the disk is new, I should be able to return it fairly easily. But I'm not sure whether there is a real problem: Should I expect no errors in the Write Zeros test? If the second Extended Test is OK, should I run the Write Zeros test again? If a second Write Zeros test produces errors, what does this indicate?
  11. Thanks, Ashe. Yes, it was a BIOS issue. The Supermicro motherboard/BIOS saw the new flash drive as a USB hard disk, and placed it at the bottom of the list of hard disk devices for booting. I moved it to the top and now I'm up and running again - well as soon as the parity check is completed. Not sure why unRAID detected an unclean shutdown, but I haven't run one for a few months, so probably good to do. Thanks to everyone for their suggestions.
  12. Hmm, not having much luck here. I copied the files on the current very old flash drive (Sandisk Cruzer Micro, from Lime-Tech in the early days) to a Sandisk Cruzer Blade, which I had done a guick format on (FAT32, labelled UNRAID). I then ran the make_boot as administrator. But the Blade doesn't seem to boot. I see the motherboard logo then just a flashing cursor. It doesn't get to the Memtest option screen. I'm now trying to do a full format and retry the above, although I think that's unlikely to be the problem.
  13. Thanks for the suggestions. When I ran diagnostics I had a problem: I get a mkdir error, saying it can't create the /boot/logs directory. There is a message saying diagnostics file has been created, but when I transfer the flash device to another PC, there is no such file, and there's no /boot/logs directory. I've checked the flash drive for system errors on a Windows 10 PC. Good old Windows tells me there's a problem with the flash drive and that I should scan it for errors, but when I do that Windows tells me there are no errors. My suspicion is that the flash drive is failing. I've tried it on three PCs, and only one of the PCs "sees" it. I think I'm going to have to replace the drive.
  14. I was away for a few days, and did a clean shutdown on my tower, which is on unRAID 6.1.7. When I got home today I restarted the machine, which is usually headless, and found I couldn't connect to it from other PCs in the network. I attached a monitor and keyboard, and started the server again. I haven't done a cold boot in a long time, so can't remember what is meant to happen, but it did seem that unpacking bzroot took a longer time than I recalled. Then the boot process reached "cpuload started" and after that I got an error "gzip: stdin" Input/output error" followed by "tar: Unexpected EOF in archive" twice, then "tar: Error is not recoverable: exiting now". The process continues, and I get the login prompt "Tower login:" Now, my memory is poor on this, but I thought that this should indicate that the server is up and running, but I couldn't connect to it from other PCs on the same (wired) network. I logged in as user root, but still couldn't see the server. I can ping "tower" with no problem, but I just can't get to the files on the server, or the web interface. Also, my USB drive has a green light and my recollection is that this was always on while the server was running, but now there's no light. I don't know if this is relevant. Any suggestions?
  15. Thanks for the point about Nvidia GPUs. OK, I understand that I lose the console, but I assume I can still at least get to the web-based GUI? And what is the console used for after unRAID has booted up successfully?
  16. I'm thinking of getting a motherboard that has no IPMI and a CPU without integrated graphics. Can I boot the unRAID server using a graphics card to set up BIOS, etc. if necessary, and then start up a VM and assign the same graphics card to the VM? I just want to be able to monitor the unRAID startup when necessary, but don't want to waste a slot and graphics card just for that purpose, if possible.
  17. According to the case specs, it holds only 2 x 3.5 inch drives (and 2 x 5.25 inch). Glad to see the OP found a way to install more.
  18. The Asrock mb form factor is SSI-EEB, whereas the Corsair 540 is E-ATX. Did you have any difficulties mounting the mb? Also, how are you squeezing in all those 3.5 inch drives?
  19. Thanks for the advice. I'm avoiding "ES" CPUs and looking at the S-Spec as well.
  20. I've been spending far more time than I should browsing around eBay, and came across various "non-Intel" Xeons. The "manufacturers" are companies like HP, Lenovo and Dell. I'm assuming that the Xeons are in fact the real deal, and it's just that the processors came from servers manufactured by the companies quoted. I'm hoping someone can confirm this before I go out and buy something that turns out to be proprietary or non-standard in some way.
  21. Not sure if it applies to your MB, but came across this from a FAQ on the Asus website http://www.asus.com/support/FAQ/1009608/ For the Adaptec 6805E it says "There are some compatibility problem of latest Adaptec firmware 19147. If it’s necessary for you to use this controller, please downgrade the firmware to previous version 19109 or contact Adaptec for technical support." Don't know what version you downgraded to.
  22. According to http://www.cpu-world.com/sspec/SR/SR0H8.html this S-Spec (SR0H8) doesn't support VT-d; or at least it isn't listed under "Features", whereas the same CPU with the SR0KX S-Spec does have VT-d listed. I don't know whether this is just an omission on CPU World, and I can't find anything definitive on the Intel website.
  23. Supermicro Sc933. Those are technically 2u coolers. Ah, my mistake. I was mixing up your coolers with another poster who was buying the SNK-P0050AP4 cooler.
  24. What case are you using? Those coolers don't stick up nearly as much as I thought they would.