Fireball3

Long SMART is OK. Save the report. I would run the preclear again to see if there are further changes in bad sectors. I've never seen so many reallocated sectors... What's the threshold value for reallocated sector count in the SMART report? If you're still in warranty period I would RMA the drive.

Preclearing a 4 TB Seagate took me about 44 hours (1 pass)

Indeed, a good question! My mind tricked me. I understood he updated to 5.0.3. I thought you referred to the driver update when you posted the link... Completely wrong thinking on my side.

I did. No problems with 5.0.3 But I read a thread where a guy reported problems with the new Realtek NIC driver. So if you have such a NIC, better postpone it or prepare to revert to 5.0 in case.

That's right. Unfortunately many things are not standard in unRAID. Too many in fact. (status notification, clean powerdown, standby, task planer aka. cronjobs, backup, ...) Use the GUI only and the plugins that cause it to crash every now and then (you can read it in every GUI related post) and you end up parity checking every week. You can't even copy a syslog without accessing the shell.

</blockquote> So it is possible that the enterprise drives are in a better operating environment than the consumer drives. So maybe it's a wash with the heavier usage. Who knows. What we do know is that from their data there is not a significant difference in drive failure rate - at least nothing even close to approaching the difference in reliability that the OEM's claim in their specs. While enterprise drives produce considerably more heat it is necessary to cool them really good. Asuming they are at the same temperature level it is still not the same load they are working at. If testing is done at different load levels you can't compare reliability figures.

probably with this [pre][/pre] net use * /delete [pre][/pre]

What about this? Comparing apples and oranges???

OK, I see (pretty quiet during the second parity check) SMART looks good. Luckily you have unRAID and the parity. As explained by binhex, the unreadable sectors have been rewritten from parity information. For your information: A friend of mine had 2 WD drives (1,5TB greens) in an external enclosure. Just a few days ago he got himself a NAS and he copied the movies from those drives. In the process he ended up with lots of unreadable files. Many of his stored movies are gone now. (I will try to ddrescue them) One of mine 1,5TB WD drives died a few months ago during preclearing. Reported bad sectors during 1st and 2nd preclear and during the 3rd preclear it stopped responding. Probing it with the WD diagnostic tool reported "drive failure". This draws a bad picture of WD drives. Imagine your second drive also reports bad sectors at the same location...bad luck! Furthermore, it's questioning the practice of storing backups on standalone drives (like many do).

There must be a mistake: Apart from a few lines at the end the log files are identical!

To make sure that Tom gets your attention, please mail him! [email protected] He probably can't test every driver/hardware so things like this just happen.

Screen should still be running. Have you tried screen -r? But that won't show you the results of the passed cycles. To see them you have to look for the log files in /var/logs I think (not sure about the path). There are a couple of files for each cycle.

Sorry to disappoint you but it is a windows issue. One of the many windows & networking mysteries. Edit: Read up on this. This is invaluable!

Why isn't anybody answering his question? I think it is very important for him to know what it is! No, even more! If it comes to preclearing at the latest. Just pointing at the GUI is not sufficient! Well, what you're seeing is the login to the shell. You may also want to read this. When you're logged in as root ... you have the full control over your rig! The GUI is only "the tip of the iceberg".

I'm also interested in how to do that!

NP, you're welcome. Glad you got it working in the end. 5.0 is the latest final. 5.0.x are patch releases - also safe to go with Tend to say, everything that's not -rc is a final.

Just rewieved my proposals that I made some time ago. I was told to "Send a Pull Request" or "make a feature recommendation on Github". Not sure how to deal with that. Did you collect the wishes sent along with the survey or do we have to "send a Pull Request" for each of them? I suppose you got plenty feedback and wishes from us within the surveys. Would you mind updating the roadmap and add a feature list that you're planning to include?

Just compared your logfile and found that your go file is not called. In my log it looks like: logger: Starting go script Did you manually edit the go file? The probably fastest way is to prepare the Stick from scratch. Just use the 5.0 final or if you need the newes features go for the 5.0.3

True, you can't. What I tried to tell you. You're doing it right by accessing it from another machine. Is your LAN OK? Router ping-able from the unRAID? Did you configure the NIC? Edit: OK, checked your log. You get an IP from your DHCP. You mean after u start it manually the GUI is accessible?

I understand you want to have a GUI running on the server on the attached screen? You can't access the GUI that way! You can access the GUI only by browsing from another computer! Type the name of your server in the url or use its IP.

He's obviously looking for a "on top" solution like flexraid or snapraid. He probably won't build a new unRAID server...

I have this old drive laying around and decided to include it into my array since there are enough slots left and I don't need them at the moment. Strange thing are the SMART temp readings. Just after start-up of the machine where the temps should be about 22°C (ambient temperature) the SMART value is reported as of 40°C. During preclear it goes up to 71°C - pretty unbelievable to me. Anybody in here who ever had this type of drives in use? I suppose it's just an offset in temp. Maybe a SMART issue as well? Considering it's a 12W drive and that it is build in a 3in2 enclosure a steady temp of 50°C - 55°C during preclearing/parity checks is reasonable to me. Anyway, if it dies I finally get rid of it. I will use it as a backup storage. Just wanted to know if this is a known issue with this drive model.

I've also been successfully preclearing 3x 4TB drives at a time without additional parameters on a 4GB machine. Pretty stock unRAID although! If you run plugins or cause any other load on the server it may get hairy.

Argh... The fragment I posted was cut out while the server was still running via the unMENU GUI. When I "powerdown"ed the server and it failed to shut down it obviously didn't save the syslog. I should have copied the syslog when I logged in to powerdown but I knew that the powerdown script saves the log. Did not expect that script to hang up also. Have to remove the syslog in the other post...

Thx for looking into this. See here...