Hello!

 

I used Dell GX290 computer with 2.8Ghz Pentium processor and 2Gb RAM to build basic unRaid server.

Initially I had 2 750Gb SATA drives that worked perfectly and today I wanted to add 320Gb PATA drive to increase disk space a bit.

To my surprise even though unRaid sees the 320Gb drive it doesn't do anything with it as there are apparent problems with 320Gb hard drive or maybe IDE controller upon boot up.

I'm attaching complete log in hopes someone can help me figure out what needs to be done.

Thanks.

log.txt

Wow... if you look in the sections that talk about hda1 you will see a whole list of FAIL.  Have you run a preclear cycle on the disk to check for errors?

No I didn't. I know that drive is OK, it was just running in XBMC.

 

The errors indicate otherwise. You should run the preclear script.

Got it, will run and return with results, although when I looked at preclear instructions they looked complicated to me Thanks for all input.

Gents, preclear did not run properly indicating some problems with drive according to SMART so I threw in 40Gb drive and low and behold after assigning to array drive started to clear, log is clean.

I can't believe that 320gb drive is dead. It was just working in my xbox. Is it possible that it's not dead and something can be done?

The drive in question is Seagate, I used Seatools and it failed both short and long tests showing 249 bad lba's, go figure. Just confirms one more time why backup systems like unRaid are necessary if data needs to be protected from loss.

Another newbie question;

 

How come there is a reference to the pre-clear script - shouldnt Unraid peform a pre-clear by default?

I thought the script was purely there to safe time so that the array doesnt need to be down.

How come there is a reference to the pre-clear script - shouldnt Unraid peform a pre-clear by default?

 

Yes, unRAID will clear it.  Kind of.  But while it's doing that, your array will be down, which on some disks may take 20 hours or so.

So you need a tool that wil prepare your disk off-line.  Read this post, it explains a lot:

http://lime-technology.com/forum/index.php?topic=2817.msg23246#msg23246

 

 

cheers m8 - got confused there for a sec 

I'm having second thoughts on that 320gb drive. Since I took it out of modded original XBOX it needs to be lnlocked? Perhaps it needs to be returned back to non XBOX condition in order to be recognized/used in PC/Linux environment?

I'm having second thoughts on that 320gb drive.

 

That disk is dead, dude.  Let it go.

 

 

Because of the usage pattern in a dedicated system like an XBox, you could have significant bit-rot on the formatting info in certain locations.

 

If you are a hell-bent on reviving the drive, (it might make a good cache drive, but I wouldn't trust it with critical data), set up a machine that can boot DOS.  Then get a copy of HDD Regenerator:

 

  http://www.dposoft.net/

 

You don't need to buy it right off the bat... the eval will run until it finds a bad spot, and repair it, then quit.  Then you can restart HDDREG, tell it to restart at a position close to where it stopped, and continue.  Repeat as needed.

 

I have revived several drives this way that would not format or even partition, and then used them in non-critical operations.

Well, if the only problem with a drive is that it is locked then unlocking and using it would be ok by me, if it is really dead I still have warranty until 2012. I guess I win either way

I just need to figure out if problems in a log and Seatools where due to drive being locked or they are genuine drive failure problems.

Gents, turns out that unlocking drive did the trick, no more errors of any kind. Please see attached log if interested.

Thanks to all for taking time to help me out, I appreciate it very much.

log2.txt