May 26, 201115 yr I'm using 5.0b2 and recently added a 2Tb Hitachi (HDS5C3020ALA632_ML0220F30RES8D) as a cache drive. The drive works fine until it's spun down (asleep). After that, going to the main page and clicking SPIN UP all drives- spins up every drive except it. (It remains asleep, according to the menu). If I STOP then START the array, it shows up as UNFORMATTED. If I STOP and REBOOT (all thru the menu/soft reboot), it comes back to life and all is well. Any data that was on it is preserved, and the move script works just fine... Also, issuing a SPIN DOWN command does not cause the drive to spin down. So, apparently, it's going to sleep on its own and choosing NOT to wake up to normal commands.... All the drives in the array (Samsung, Seagate and WD) work normally. Ideas? Suggestions? Thanks!
May 26, 201115 yr I'm using 5.0b2 and recently added a 2Tb Hitachi (HDS5C3020ALA632_ML0220F30RES8D) as a cache drive. The drive works fine until it's spun down (asleep). After that, going to the main page and clicking SPIN UP all drives- spins up every drive except it. (It remains asleep, according to the menu). If I STOP then START the array, it shows up as UNFORMATTED. If I STOP and REBOOT (all thru the menu/soft reboot), it comes back to life and all is well. Any data that was on it is preserved, and the move script works just fine... Also, issuing a SPIN DOWN command does not cause the drive to spin down. So, apparently, it's going to sleep on its own and choosing NOT to wake up to normal commands.... All the drives in the array (Samsung, Seagate and WD) work normally. Ideas? Suggestions? Thanks! yes. upgrade to 5.0beta6a and then see if it acts the same. ( I did not see anything specific to this in the release notes, so it might still exist) You are not likely to get anyone on the older beta2 release, and even lime-tech will tell you to upgrade first. If you wish, it appears as if 5.0beta7 will be out shortly, so you can wait for it. The cache drive is not part of the protected unRAID array, so it is no surprise it does not spin up down with the command on the management interface. Did you send a trouble report to lime-technology? either via e-mail or PM? That would at least get the problem some attention if it still exists.
May 27, 201115 yr Author Copied the information to LimeTech. No response...yet. I don't have a practice machine, so I'm very cautious about updating it. (And I know I'm already running a beta, but at the time I started my server, I couldn't get the then-current version to work for me, so I've been using beta2 since day 2) I do, however, have two licenses for two USB keys. Is there any practical advantage to applying the update to the second key for testing purposes? My PRIMARY concern is for the integrity of my data already in the array. Reloading it from DVDs would be just dreadful....
May 27, 201115 yr Copied the information to LimeTech. No response...yet. I don't have a practice machine, so I'm very cautious about updating it. (And I know I'm already running a beta, but at the time I started my server, I couldn't get the then-current version to work for me, so I've been using beta2 since day 2) I do, however, have two licenses for two USB keys. Is there any practical advantage to applying the update to the second key for testing purposes? My PRIMARY concern is for the integrity of my data already in the array. Reloading it from DVDs would be just dreadful.... I know the feeling - I recently upgraded from 4.7 to 5.0b6 to get support for Plex Media Server (which is *amazing* and worth the 30 mins of elevated heart rate!!!) As I understand it, you just have to be careful after the upgrade not to start the array if the disks are reported as "MBR: Unknown" or "MBR: Error". It's all in this thread. Probably not telling you anything you don't already know, but provided you're careful, you should be fine.
Archived
This topic is now archived and is closed to further replies.