hard disk broken?

Hello everyobdy,

 

after Nars helped me with my other problem, I ran into another problem :'(.

 

Yesterday I noticed that my disk 2 was "invalid disk". I thought that was because I shut down the computer without stopping the array. So I thought a reconfiguration of the disks woud fix this. Since there was no data on my raid yet, I decided to reassign the disks. My 2 western digitals green 2TB became Hard disk 1 and 2( before hard disk 1 was a western digital green, but hard disk 2 was a samsung F4 green 2TB) and I set my 2 TB samsung F4 as parity disk. I let the system build the parity and format the other drives over night. When I woke up this morning the computer was at sleep (I've set it this way after an hour it goes to sleep). I woke the computer up and now the parity disk was invalid (note: it's the same disk that was previously used as disk 2). When the computer woke up from sleep I heard a strange noise, like a disk was trying to start, but it wasn't able to. (maybe it was the samsung?). So I was at the webinterface and the parity disk wasn't valid. A few moments later it became disabled. And the webinterface became inaccessible.

I did a hard reboot with the powerbutton.

Now the webinterface works again, but parity drive is red and shows :Not Installed. If I stop the array the samsung disk isn't there either . I can't see the SMART values since the disk isn't found . I did run HDD tune bad block test before mounting the drive into my unraid server and everything was fine. Is this drive (samsung f4 ) broken? Should I buy a new one?

 

 

Here are my system logs and smart values of the hard disks:

https://dl.dropbox.com/u/64092960/unraidserver/smart.txt

https://dl.dropbox.com/u/64092960/unraidserver/syslog.txt

 

Thanks in advance

 

 

edit:

System specs:

cpu: Intel Celeron G1610

Motherboard: ASRock Intel H77 H77M

HDD 1: Western Digital Green WD20EZRX, 2TB

HDD 2: Western Digital Green WD20EZRX, 2TB

Parity: SAMSUNG HD204UI, 2TB

PSu: be quiet! System Power 7 300W

RAM: Crucial 4GB 1600mhz cl 9

Case: Cooler Master Elite 310

 

 

Two thoughts. Unraid does not support sleep, if you set it to sleep, you must be using a non limetech tested method to accomplish it, and sleep just may not work with your hardware. Second, from your description, it sounds like your power supply isn't providing clean power, since you mentioned funny noises from your hard drives when they start. I suspect your entire issue would be solved if you just let unraid power down the disks using the limetech provided disk spindown, and allow the system to stay running. If not, then your power supply would be my next suspect.

I use simple features and set it to sleep after 45 minutes after spin down. Hmmm why the power supply, two times I get invalid data, and two times it's the same drive. What does that have to do with psu?

I use simple features and set it to sleep after 45 minutes after spin down. Hmmm why the power supply, two times I get invalid data, and two times it's the same drive. What does that have to do with psu?

Simple features is not authored or supported by limetech. The PSU may not have enough power to spin up everything at once from sleep. If the drive is slow to start, it may not be fully awake when it is asked for a response.

I found this: http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks

But before I put the f4 in my unraid server I reflashed it with the latest firmware I could find. Maybe it didn't work

 

Edit: Think I'm Going To try To Flash The JP1 Firmware. Altought My Drive Isn'T The JP Model

I found this: http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks

But before I put the f4 in my unraid server I reflashed it with the latest firmware I could find. Maybe it didn't work

 

Edit: Think I'm Going To try To Flash The JP1 Firmware. Altought My Drive Isn'T The JP Model

 

Do NOT flash firmware unless it is specifically made for your drive! That is almost a 100% sure method of bricking the disk.

But If I Read The Thread I Linked To Many Other People Did That, Because The Non JP Firmware Doesn't Change The Firmware Number. I've Also Read The JP Model Is The Same AsThe Normal, but It Is For The Japanese Markrt. Maybe A Person Who Did Flash The JP Version On A Non-JP Hard Disk Can Confir This?

Yesterday I noticed that my disk 2 was "invalid disk". I thought that was because I shut down the computer without stopping the array. So I thought a reconfiguration of the disks woud fix this. Since there was no data on my raid yet, I decided to reassign the disks. My 2 western digitals green 2TB became Hard disk 1 and 2( before hard disk 1 was a western digital green, but hard disk 2 was a samsung F4 green 2TB) and I set my 2 TB samsung F4 as parity disk. I let the system build the parity and format the other drives over night. When I woke up this morning the computer was at sleep (I've set it this way after an hour it goes to sleep). I woke the computer up and now the parity disk was invalid (note: it's the same disk that was previously used as disk 2). When the computer woke up from sleep I heard a strange noise, like a disk was trying to start, but it wasn't able to. (maybe it was the samsung?). So I was at the webinterface and the parity disk wasn't valid. A few moments later it became disabled. And the webinterface became inaccessible.

I did a hard reboot with the powerbutton.

Now the webinterface works again, but parity drive is red and shows :Not Installed. If I stop the array the samsung disk isn't there either . I can't see the SMART values since the disk isn't found . I did run HDD tune bad block test before mounting the drive into my unraid server and everything was fine. Is this drive (samsung f4 ) broken? Should I buy a new one?

 

Here are my system logs and smart values of the hard disks:

https://dl.dropbox.com/u/64092960/unraidserver/smart.txt

https://dl.dropbox.com/u/64092960/unraidserver/syslog.txt

 

Nothing bad happens during the session of this syslog, so I can't be definitive.  It would have been useful to grab a copy of the syslog from the session in which the drive appeared to fail.

 

The SMART report for the Samsung does show a critically long startup in the past, probably when you heard the hard drive noises.  This *may* indicate a failing drive, bad motors or servos?  As others said though, if it could not get enough power when it tried to spin up, then that might also explain it.  The PSU you list is probably not very good, but I don't recognize it at all, so should not draw any conclusions.  I would strongly recommend you look into upgrading your PSU though.

Hmmm don't think that PSU is that bad.

http://be.hardware.info/productinfo/170749/be-quiet!-system-power-7-300w#tab:testresultaten

(it's in dutch)

http://www.anandtech.com/show/6013/350450w-roundup-11-cheap-psus/11

(but this is the 350 watt model)

Here is the website of my PSU: http://www.bequiet.com/en/powersupply/325

 

This evening I flash it with JP firmware and flash it and I put it back in the server. And if it fails again I will post a syslog.

 

 

found this: http://forum.qnap.com/viewtopic.php?p=184182

Hmmm don't think that PSU is that bad.

You are probably right at the limit of what that model is capable of. You only have 18 Amps available to spin up your hard drives. It's definitely not a storage server recommended PSU.

Isn't 18 amperes enough for 3 drives and a low power dual core cpu? How many amps do you suggest? How many disks can I go on this PSU?

 

(http://forum.qnap.com/viewtopic.php?f=182&t=41597 says the spin up of samsung drive is 2 amps adn for a western digital green its less than 2 amps , I must say I have other greens)

Isn't 18 amperes enough for 3 drives and a low power dual core cpu?

On paper it should be ok. Reality, however, can prove different. If your power supply isn't waking up cleanly and supplying full power smoothly, or your hard drive could have a slightly out of tolerance bearing that needs more power, or any other anomaly that increases power needs, you aren't leaving yourself much margin. Kind of like towing a big trailer with a small economy car, it will probably move it ok, but it's not going to be happy about it, and may wear out prematurely.

 

As I said before, I'm not saying for sure that your PSU is causing the issue, just that it seems a little weak for a server.

Since Other People Had The Same Problem With Their F4 On qnap Nas Box, I Think It Isn't Compatible With.Unraid/Sleep Because It's A Slow Waker. Didn't Got Time To Flash My Hdd Yesterday, Gonna Try This Evening.

 

thanks

 

edit: should I enable PM2 http://wdc.custhelp.com/app/answers/detail/a_id/958/~/how-to-enable-and-disable-pm2-%28power-management%29-on-wd-sata-drives ?

 

"Note: Power management allows the drive to be powered-up into the Standby power management state to minimize inrush current at power-up and to allow the host to sequence the spin-up of devices."