aiden

In my build I could never get the hot swap bay to seat snugly in the ODD because the mounting mechanism is squirrelly. Did you have any problems?

I can confirm the package.conf file works perfectly for installing handbrake. I installed it, set it for reinstall on reboot, and rebooted, and it came up as installed with the correct checksum. As far as confirming handbrake works, I don't know that yet.

Basically because not enough people have confirmed that it works as desired and that is a good candidate to be included as currently defined. Have you used the package.conf file? Did it work as expected? Does it need any changes/improvements? Joe L. No, I have not. I was about to embark on an experiment since I have not used handbrake before, and thought I would check its level of integration with the package manager before I installed it manually.

Hm... why is this not in the list of packages within unMENU?

Wouldn't something like a Memtest approach be more appropriate for SSDs?

Very nice and clean. I dig your project link too. What SATA cables are you using?

Hm... TB maybe? LOVE the look of that case. That all drive look is very sexy.

Yes, my unraid was on the same system and was up during the preclear cycles. In fact, I was writing over 100 GB of data to the array at one point, and only using the onboard SATA ports for all of it. This is all on a D510 Atom system. I would venture a guess that processor speed has little to do with preclearing the drive, and that it is most likely RAM and bus related.

Hm... that's interesting that your speeds are that low. I have precleared several 2 TB drives, from 7200 rpm down to 5400 rpm, and the lowest I've seen was 45 Mb/s. The 7200 scales roughly 40 - 50% faster as a whole, which is what one might expect. Never had one take 52 hours for a preclear cycle. They usually finish @ 35 - 38 hours. That's running off the motherboard ports. My system has 2 GB ram in it, but if I remember correctly, when memory becomes an issue, the script either hangs or exits.

Run preclear two more times and post the differences again.

A few preclear cycles should clear up any worries about a new drive. Either it's stable, or it's not. As far as the fail rate goes, I think the manufacturers are playing the consumer market like a song. We constantly replace drives because new capacities are released, or because a drive fails in 3 years. Planned obsolescence?

The 253 on the first drive is an initialization value indicating the drive has never been used before. The other drives look fine. It's odd that you had a dead drive from Limetech, as they supposedly preclear the drives themselves before shipment. Did you buy the drives from somewhere else?

Thanks Joe. It's all new to me, but thanks for the encouragement. lboregard - Just an FYI, you can open multiple sessions to your server remotely and run cycles on all your drives simultaneously.

If you look here the value 253 refers to the drive being completely virgin and brand new. After your first cycle, that value drops to 200 indicating that the drive has no failures, but is no longer new. That SMART report looks clean to me, and I would bet that your second or third cycle will contain no changes. What 2TB drive are you using? I have 2 of them running 10 cycles atm and they are averaging about 28 hours for a full cycle. The old mobo I'm using is only SATA 150.

Okay, this is the first preclear of a Hitachi Deskstar 2TB 7200rpm drive, model HD32000IDK7. Am I correct in assuming this drive is healthy? Why did the value go from 95 up to 100 after the preclear? =========================================================================== = unRAID server Pre-Clear disk /dev/sda = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 42C, Elapsed Time: 27:22:47 ============================================================================ == == Disk /dev/sda has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activity < was never started. --- > Offline data collection status: (0x84) Offline data collection activity > was suspended by an interrupting command from host. 52c52 < 1 Raw_Read_Error_Rate 0x000b 095 095 016 Pre-fail Always - 1114112 --- > 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 ============================================================================