Hi All,

I'm trying to replace a drive that was reporting read/write errors.  I stopped the array, powered down the machine and swapped a 750 GB for a brand new 2TB drive.  Started the machine, then went to web console and saw the new drive with the blue icon.  Clicked "I want to do this"; and pressed the "Start and expand file system button".

The system seems to not have found the drives after the new drive, and is stuck in a "Mounting state".

 

The new drive was not pre-cleared, did not try and use it in another system, so perhaps the drive is bad?

 

Any suggestions on how to proceed?  My first inclination is to power the system down via a telnet window, remove the drive and see if the new 2TB mounts in another system.

 

Syslog, and screensnaps of before/after are attached.

 

Any suggestions?

 

Thanks in advance

syslog.zip

Try to refresh the browser. Don't user the "refresh" button, reload the page.

It does not seem to be a browser refresh problem.  None of the drives that should be displayed are displayed.

 

The syslog  is complaining about failing to mount disk9:

 

Jul 20 19:55:04 Tower emhttp: disk9 mount error: -117

 

I've removed the drive and will try and see if the drive works in another PC.

 

I tried the new 2TB drive in another Windows system, it mounted/formatted without complaint.

 

Then I put the 2TB drive back into the unraid  system, and now all the 14 drives (+parity+cache) show up, with an orange ball next to the new 2TB drive.  The text under the Start button now is just "start data rebuild", not "expand file system and start data rebuild"

 

But when I click Start the browser just re-displays the same screen with the Start button re-enabled. If i remember from the last time I expanded the array it should have gone into a rebuild process.

 

The tail end of the syslog has an message about a lock error:

Tower kernel: md: do_run: lock_rdev error: -6

 

I've attached the full syslog.

 

I'm no sure what to suspect - the SATA cables seemed well seated, the system has been running fine for a couple years without problems.  I'm not adverse to picking up a new motherboard as an 'upgrade', but really, really need to have the data persisted across a possible new build.

 

Any pointers or suggestions would be most welcome, I've a non-trivial amount of data on this system that means a great deal to me.

 

Thanks in advance

 

unraid_syslog_after_2ndi_Insertof2TB.zip

Why are you still using 4.3.3??

Because I've not had a reason to upgrade.  System has been stable until now.  All previous (~11) disk upgrades went very smoothly.

Hi All.  I'm stopped on this and would really appreciate any suggestions/opinions/input...

 

I thought that maybe the SATA port on the motherboard was bad, so I connected the drive to another port on the motherboard with a new sata cable.  Once the system started drive 9 was reported as missing, so I assigned the drive to drive 9 in the devices tab (all normal up till now)

 

The UI reports the array as "Stopped. Configuration valid", with the Start button indicating "Start will bring the array on-line and start Data-Rebuild". 

 

Alas, the symptoms remain the same, the drive shows up with an orange button.  Clicking the start button just re-displays the same page, and the syslog reports the error below.  Pressing the Refresh button, refreshing the page, re-connecting from a different browser on diff machine -no difference still just a re-display of the page.

 

Jul 24 11:09:40 Tower kernel: md: do_run: lock_rdev error: -6

 

Any ideas/comments on where to look/change next?

 

Some Options I've thought of include:

 

1) I've a second unraid USB key, originally bought two Pro licenses.  I can try that USB, but not sure what that will prove.

 

2) upgrade to a newer version of unraid.  Not sure if this will solve the problem - The drive was a replacement, not adding a new drive.

 

3) remove the new 2TB drive from the devices tab, start the array and copy the data off to another system.  I'm a little concerned as the initial drive was 750GB, and the new drive is 2Tb - I'd hope that unraid would recreate the contents of the 750 from the parity drive, but I'm not 100% sure, as unraid right now seems to be stuck in the middle of expanding/recreating the file system, and I really don't want to lose any data.  I'd have to purchase the drives for the 'other array', but if that what it takes to insure I can get to my data, the it is what it is, as it were.

 

So some direct questions:

1) If I remove the new 2TB from the devices tab would you expect the array to start?

2) Would data be lost?

3) Has anyone hit this type of error, and what did they do to resolve?

 

Syslog is attached, thanks in advance,

unraid_syslog_after_move_2nd_sata_port.zip

The array should start with one drive missing and your data should be available. You can then telnet in or use the console to copy the data from the simulated missing drive to a working drive if you have space.