Web interface doesn't see second drive, Linux does

Could you try a factory default (wipes all data, settings, everything)?: http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu

Midtskogen - When you refer to the web interface, are you talking about RAIDar, RAIDiator or the volume seen by your PC?

Could you provide a screenshot?

I'm referring to what I get when I direct my browser to the ip address of the NAS. Anyway, I tried the factory reset and that worked. I think the reason why I got into trouble was that I bought a demo used unit. When I ran RAIDar for the first time, I never got the question what kind of RAID to use. It probably already was in 1 disk RAID0. I still had to do the first time setup in the web interface, though, which made me believe that it already was fully factory reset.

Thanks for the help!

Perhaps OT, but I'm curious about the LCC readings on those WD drives?

viewtopic.php?f=24&t=66720
viewtopic.php?f=11&t=59700

/f

Those are brand new disks, and the LCC readings are around 6400 so far. I don't know what their rating is.

My two WD Green Caviar 2TB disks broke the 300.000 LCCs (head parkings) marker in less than a year.
Some say the LCC MTBF is around 300.000 for these disks... :(

Green Caviar disks may not be ideal for NAS 24x365 use since they park their heads after just 8 seconds.

I recently got both disks replaced on warranty, and since setting the IDLE3 setting to 254 (>1 hr) on the replacement units, the LCC counters does not move in thousands every day. I've configured my NAS to spin down the disks after 1 hour of idling.

If I were you I'd definitely do something to prevent the disks from hitting supposed MTBF figures prematurely.


/f

Thanks for sharing this. The power on hours were just 44 hours, and I hadn't yet written anything useful to the disks apart from formatting and letting the ReadyNAS set up its things, yet the disks were both 2% of the expected lifetime, if you're right. I downloaded an idl3ctl tool from sourceforge, and the setting was 80, which I changed to 254. But what will happen if I disable the idle3 timer?

Apart from that the green WD drives are cheap (I prefer cheap disks, since expensive ones also fail randomly), these drives seemed to fit my intended use since I expect the disks to be idle much of the time. But I may have been fooled.

My disks were (past tense) also at 80 = 8 seconds before I set the value to 254.

And yeah, before learning about the WD Green's parking behavior, all sounded nice: low amps, low temp, etc.

The WD Red (http://www.wd.com/Red) were not available when I bought my disks a year ago, and the store where I just claimed warranty replacement didn't have them in their stock.

I was close to cut a deal with a colleague also buying 2 TB disks (but not WD) to swap one drive with each other (I get one of his non-WDs and he gets one of my WDs) to attempt to mitigate a "bad stock" problem. But I chose to not follow that through.

Its hard to tell at what LCC a disk will fail, but for sure - I'd prefer a low value before a high (if the effort does not hit some other MTBF factor negatively) and I can afford the extra milliamps spent by not parking heads (and inhibiting not used circuits) before spinning down one hour later.

I spent some days looking around for a good delay setting to use with the idletool, and since some people wrote (here and there) that disabling the timer (substitute value 0) may have resulted in bad behavior/problems I decided to go for 254 which I learnt from a few others. Since 254 corresponds to a period larger than one hour, my NAS's idle disk spindown timeout will occur first resulting in parking and winding down the disks instead of just parking the heads.

What the effects of totally disabling parking are hard to tell - some few more amp hours throughout the lifetime of the disks?
Some people gets annoyed of the clicking sound that you can hear when the heads are moved to the parking track, this sound will probably also be gone with disabling.

/f