August 22, 200817 yr I think time would be better spent trying to find a solution to your problem rather than me trying to prove i dont have one. I am not asking you to test to prove you, that you have a problem, but we might help others to choose between drives.
August 22, 200817 yr The reason to use the built-in standby timer in the drives is to handle the case: if the server software crashes for some reason, the hard drives would still spin down. Considering all the problems with spin-down/spin-up, I think we'll switch back to the daemon method. Glad to hear that. That would most probably solve this issue as well.
August 23, 200817 yr I have a 2-drive UnRaid. Parity was Samsung HD501LJ. It refused to spin down. And after 24 hours reported errors and was disabled. So I replaced Parity with a new Seagate ST3500320AS. And new cables. And tried it on a different SATA2 port. It too refused to spin down. And after 24 hours it too reported errors and was disabled. Two faulty disks? It's always a possibility. On the other hand... Anyway, here's the spec if it helps anyone: M/B: Gigabyte GA-945GCM-S2L USB: Kingston DataTraveler 1GB Other HDD: Hitachi Deskstar HDP72505GLA360. Which spins down fine. Case is well ventilated with multiple fans. UnRaid v4.2.4 Basic. 2008-08-23 addition: Changed SATA port again, which seems to have fixed the errors (time will tell) so that's probably a m/b fault. Also powered down and powered up, which is proposed in other threads as a possible solution for a new disk not spinning down. Too soon to tell.
August 23, 200817 yr I have a 2-drive UnRaid. Parity was Samsung HD501LJ. It refused to spin down. And after 24 hours reported errors and was disabled. So I replaced Parity with a new Seagate ST3500320AS. And new cables. And tried it on a different SATA2 port. It too refused to spin down. And after 24 hours it too reported errors and was disabled. Two faulty disks? It's always a possibility. On the other hand... Anyway, here's the spec if it helps anyone: M/B: Gigabyte GA-945GCM-S2L USB: Kingston DataTraveler 1GB Other HDD: Hitachi Deskstar HDP72505GLA360. Which spins down fine. Case is well ventilated with multiple fans. UnRaid v4.2.4 Basic. Or, one bad cable, or one bad disk controller, or you need to use one of the options in syslinux.cfg to eliminate I/O conflicts. Knowing you have multiple fans is nice, but does not help us otherwise. Only way to know more about what is happening is for you to supply a copy of your syslog. and also to run smart tests on the individual drives to determine their health. Check out the wiki for how to supply a copy of your syslog. Joe L.
August 23, 200817 yr I have an Abit AB9pro based system currently loaded with 9 Seagate 1tb drives... I noticed that, not always, but most of the time when the drives spin down bythemselves, the parity drive is left running... this morning (3am) we had a power glitch and I discovered that my UPS needs a new battery At any rate, when I woke and logged in, I founf it had completed a parity check 2 hours before and all drives were spun down except parity. I hit the spin down button on the management page and when it refreshed, all were spun down except drive 6 All drives are identical models. Weird....
August 23, 200817 yr Hi Joe L, Thanks for the response. I've changed SATA port again, and haven't had errors reported after two parity checks and 50GB written and read. Cable was changed when I changed the HDD, so pretty much ruled that out. Could well be a m/b disk controller fault. If errors persist I'll change m/b (they're only £25), and only if it then still persists will I post a new thread with a cry for help, syslog and all. Cheers, Ian.
Archived
This topic is now archived and is closed to further replies.