Sad long story.  My unRAID is the following:

 

13 HD’s, 6 Shares. 5 Shares have access to 12 HD’s, and 1 Share *(Music) is restricted to HD 13 (750GB).

 

*Music share is (was) my iTunes collection at about 600GBs.

 

Needed HD at work so ran parity check and replaced HD 13 (Music Share) with a new 2TB HD. Started rebuild and was going fine at about 5%.  Went to work (with 750 HD, voice in the back of my head being ignored). Came home hours later and progress was only about 15%. HD 8 was not showing a temperature reading and had errors (the ball was green though).  24 hours later rebuild finished but HD 9 now has red ball. HD 13 says about 600GB of data and I see the folder system so I get excited that my iTunes is saved.    Replace HD 9 (1TB) with a new 2TB and rebuild. No data or folders show up on HD 9 but iTunes was far more important. Went to look at files on HD 13 and unRAID would “freeze up” for several minuets but it is hit or miss at opening folders. Files are (mostly) missing, incomplete, inaccessible or unplayable.  So despite the unRAID showing 600GB’s of data and a file system it looks to be gone.  Also I can’t stop the unRAID now.  I think that the corrupt files system on HD 13 is the problem.  Tried to delete all folders/files on HD 13 but it’s not accessible because of the data corruption.

 

To add insult to injury I took the old HD 9 and plugged into Windows and nothing.  Then “beat” on it with back of screwdriver and now it’s accessible. Reinstalled in unRAID but would not start saying that the HD was too small.

 

Obviously my music is lost from HD 13 but can I salvage the data on old HD 9 (if it will work work long enough). Would I need to install it and use the Restore function. I guess this would wipe out my Shares but can I manually put the files back in “new” Shares?

Sad long story.  My unRAID is the following:

 

13 HD’s, 6 Shares. 5 Shares have access to 12 HD’s, and 1 Share *(Music) is restricted to HD 13 (750GB).

 

*Music share is (was) my iTunes collection at about 600GBs.

 

Needed HD at work so ran parity check and replaced HD 13 (Music Share) with a new 2TB HD. Started rebuild and was going fine at about 5%.  Went to work (with 750 HD, voice in the back of my head being ignored). Came home hours later and progress was only about 15%. HD 8 was not showing a temperature reading and had errors (the ball was green though).  24 hours later rebuild finished but HD 9 now has red ball. HD 13 says about 600GB of data and I see the folder system so I get excited that my iTunes is saved.    Replace HD 9 (1TB) with a new 2TB and rebuild. No data or folders show up on HD 9 but iTunes was far more important. Went to look at files on HD 13 and unRAID would “freeze up” for several minuets but it is hit or miss at opening folders. Files are (mostly) missing, incomplete, inaccessible or unplayable.  So despite the unRAID showing 600GB’s of data and a file system it looks to be gone.  Also I can’t stop the unRAID now.  I think that the corrupt files system on HD 13 is the problem.  Tried to delete all folders/files on HD 13 but it’s not accessible because of the data corruption.

 

To add insult to injury I took the old HD 9 and plugged into Windows and nothing.  Then “beat” on it with back of screwdriver and now it’s accessible. Reinstalled in unRAID but would not start saying that the HD was too small.

 

Obviously my music is lost from HD 13 but can I salvage the data on old HD 9 (if it will work work long enough). Would I need to install it and use the Restore function. I guess this would wipe out my Shares but can I manually put the files back in “new” Shares?

Step 1.  Before you do anything else, post a system log.

Step 2. Save a copy of your "config" folder somewhere else. (copy it to your PC)

Step 3. Get a "smart" report on the failing disk.

Step 4. DO NOT PRESS the button marked as "restore" unless you do not want the contents on the failed drive.  It will immediately invalidate parity as it is actually a button that sets a new disk configuration.  The contents of the failed disk would be forever lost. 

 

You can install the old disk9 and access its contents without it being assigned to the array.

 

You can run the file system checks - running reiserfsck - on the disk13 and see what happens. They are in the Wiki. You can search there or just look the command up to find what to run. Basically, do a check first and then it will tell you if you need to run it again with some specific switches. However, each read error from disks 8 & 9 while rebuilding likely means that disk 13 had an error thrown onto it to match.

 

I believe you could also reset the system to believe all drives are good but drive 13 and then rebuild it again. This is only assuming disk 8 and disk 9 will both work long enough to survive the rebuild of disk13 without having read errors. You basically use a variation of the trust my parity procedure except you use 13 instead of 99 and that tells unRAID that disk 13 needs to be rebuilt. I'd confirm this with others here first. You may want to try this with the 2T drive you tried for disk9 and hold onto the new disk13 in case it has data that can be recovered.

 

I suspect the new rebuilt disk9 is likely messed-up so badly it's useless to try and recover anything from it.

 

You had some major issues when rebuilding a drive. You really should have stopped and evaluated the disk9 and the health of the array before going any further. You might have been able to get disk9 working again and tried another rebuild of disk13.

 

Hopefully, one of the more experienced members can help with some specific recommendations.

 

Peter

Step 1.  Before you do anything else, post a system log.

Step 2. Save a copy of your "config" folder somewhere else. (copy it to your PC)

Step 3. Get a "smart" report on the failing disk.

Step 4. DO NOT PRESS the button marked as "restore" unless you do not want the contents on the failed drive.  It will immediately invalidate parity as it is actually a button that sets a new disk configuration.  The contents of the failed disk would be forever lost.  

 

You can install the old disk9 and access its contents without it being assigned to the array.

 

Step 1. Looking at logs. The last two and other 25 or so are 1MB size but the one from the HD failure is 1.9GB which fills up the Flash drive. I copped it to my Mac but I'm not allowed to delete it. Could this be causing the won't "Stop" problems? If so how do I delete it?

Step 2. Made a copy of the Config folder to my Mac.

Step 3. Not sure about how to run Smart report. Do you have a link or can I find it in the Wiki? Also do I replace the new 2TB disk9 with the old 1TB disk9 to run it (how do I start array?) or do I put old disk9 in unused disk14?

 

How do I install the old disk9?

 

Also I can't attach the log because it says the file is too large.

 

EDIT: Attached about 1st 1/2 of log.

syslog-20101220-163632-1.pdf

I cut the log into about 1/2.

syslog-20101220-163632-2.pdf

Any help or advice. I need to get my unRAID back into operation. Can I take the "old" disk9 and instal as disk14 and copy the files into the Movies share (if it will work)?

Someone Please Help.

 

How do I remove/delete/format disk13 and delete the Share Music off of it to uncorrupt my file system?

 

How do I mount the old disk9 in the unRAID and copy the contents back to the Movies and TV shares?

Do you trust the old disk9? I assume you have given up on the rebuilt disk13 and want to try again?

 

If so, you can try this;

Re-install the old disk9 and assign it to the disk9 slot.

Make sure all the others are as they were assigned including the new disk13.

Click the Restore button. Do not press Start at this time.

At the command prompt type the following

-> mdcmd set invalidslot 13

 

Now, if you go back to the main unRAID web page (refresh or open it again) it should say that disk13 is a replacement disk. If you start the array then disk13 will be rebuilt again.

 

Once you are done with the rebuild you may have to run a file system check/rebuild on disk13 to get it working again. Report back what happens with the rebuild.

 

Peter

 

Do you trust the old disk9? I assume you have given up on the rebuilt disk13 and want to try again?

 

If so, you can try this;

Re-install the old disk9 and assign it to the disk9 slot.

Make sure all the others are as they were assigned including the new disk13.

Click the Restore button. Do not press Start at this time.

At the command prompt type the following

-> mdcmd set invalidslot 13

 

Now, if you go back to the main unRAID web page (refresh or open it again) it should say that disk13 is a replacement disk. If you start the array then disk13 will be rebuilt again.

 

Once you are done with the rebuild you may have to run a file system check/rebuild on disk13 to get it working again. Report back what happens with the rebuild.

 

Peter

 

I can't reassign and replace the new disk9 (2TB) with the old disk9(1TB) because it says it's too small.  It's a 1TB and I rebuilt with a 2TB.  How do I "force" the unRAID to accept the smaller disc?

Do you trust the old disk9? I assume you have given up on the rebuilt disk13 and want to try again?

 

If so, you can try this;

Re-install the old disk9 and assign it to the disk9 slot.

Make sure all the others are as they were assigned including the new disk13.

Click the Restore button. Do not press Start at this time.

At the command prompt type the following

-> mdcmd set invalidslot 13

 

Now, if you go back to the main unRAID web page (refresh or open it again) it should say that disk13 is a replacement disk. If you start the array then disk13 will be rebuilt again.

 

Once you are done with the rebuild you may have to run a file system check/rebuild on disk13 to get it working again. Report back what happens with the rebuild.

 

Peter

 

I can't reassign and replace the new disk9 (2TB) with the old disk9(1TB) because it says it's too small.  It's a 1TB and I rebuilt with a 2TB.  How do I "force" the unRAID to accept the smaller disc?

If you followed the steps peter outlined it would let you use the old disk9.

 

As peter said... you need to force a new disk configuration and force the array to think disk13 is the disk to be rebuilt.

 

quoting:

Re-install the old disk9 and assign it to the disk9 slot.

Make sure all the others are as they were assigned including the new disk13.

Click the Restore button. Do not press Start at this time.

At the command prompt type the following

/root/mdcmd set invalidslot 13

 

Now, if you go back to the main unRAID web page (refresh or open it again) it should say that disk13 is a replacement disk. If you start the array then disk13 will be rebuilt again.

 

Once you are done with the rebuild you may have to run a file system check/rebuild on disk13 to get it working again. Report back what happens with the rebuild.

If you followed the steps peter outlined it would let you use the old disk9.

 

As peter said... you need to force a new disk configuration and force the array to think disk13 is the disk to be rebuilt.

 

quoting:

Re-install the old disk9 and assign it to the disk9 slot.

Make sure all the others are as they were assigned including the new disk13.

Click the Restore button. Do not press Start at this time.

At the command prompt type the following

/root/mdcmd set invalidslot 13

I should have some time later this morning and will give it a try.  Hope old drive9 will work long enough to rebuild.

Now, if you go back to the main unRAID web page (refresh or open it again) it should say that disk13 is a replacement disk. If you start the array then disk13 will be rebuilt again.

 

Once you are done with the rebuild you may have to run a file system check/rebuild on disk13 to get it working again. Report back what happens with the rebuild.

 

Sorry understand now. It was when I hit the Start button that it gave the message.  I will give it a try about lunch time today (I hope).

 

So I will after reassign/restore (but NOT start) on the web/browser page go to the console and type /root/mdcmd set invalidslot 13 [enter] .  Does this command format and/or delete the (corrupt?) file system on drive13?

it forces unraid to think the disk13 has ffailed and the others are ok.

 

It does nothing to the data or formatting.

If the fiile system is corrupt,it will be reconstucted onto disk13 as corrupt.

 

 

it forces unraid to think the disk13 has ffailed and the others are ok.

 

It does nothing to the data or formatting.

If the fiile system is corrupt,it will be reconstucted onto disk13 as corrupt.

 

 

 

I want to format disc13 and remove all data because the file system is corrupt (can't delete or read files/folders) and it causes the unRAID to hang up and become unresponsive.  Also I can't Stop the unRAID (I believe because of disk13 corrupt file structure) and must hard reset or hard cut off (which starts parity check on the next power up).

 

Is there a command that will just format disc13 (and the allow the unRAID to forget all of disk13's (corrupt) files/Shares (just 1 named Music) allowing me to mount it back in the unRAID as a "new" disc13?

 

Also should I be concerned that my flash drive (2GB) if full because of the 1.8GB log file?

I think I understand that you are trying to get bak my ORIGINAL file system.

 

Just replaced disk9 with old, powered up unRAID, disk9 was assigned so I checked Restore box and hit Restore button (but not Start).  Went to the console and typed:

 

/root/mdcmd set invalidslot 13

 

and it retured:

 

cmdOper=set

cmdResult=ok

 

Back at the (refreshed and reloaded) web page all balls are blue. Do I still hit Start or is something wrong?

 

While you are waiting for Joe L. (and you should), did you refresh the web management page?

William,

 

I just did these steps on my test server. Yes, the display should be all blue like you posted. The next step is to start the array. All disks should turn green and disk13 should be orange. A reconstruction of the data on disk13 should be in process the disk will be unformatted until you format it, which you can do at any time during the reconstruction process.

William,

 

I just did these steps on my test server. Yes, the display should be all blue like you posted. The next step is to start the array. All disks should turn green and disk13 should be orange. A reconstruction of the data on disk13 should be in process the disk will be unformatted until you format it, which you can do at any time during the reconstruction process.

OK it says it's formatting disc13. I was confused because the original instructions didn't say they would all be blue. After formatting it should just start rebuilding disk13?  Also will this will be a rebuild of the ORIGINAL data before the corruption and loss?

 

Will post back after it through formatting.

 

Thanks

it would not be formatting disk13 unless you pressed the format button

it would not be formatting disk13 unless you pressed the format button

I did press Format per ohlwiler instructions.  Was this wrong? It's through formatting and at 0.2% rebuild.

if there was nothing on the disk you wanted, it was fine. Gets you off to a clean start with it.

if there was nothing on the disk you wanted, it was fine. Gets you off to a clean start with it.

No, but wouldn't the rebuild wipe everything off anyway?  Also while I have no errors on old disk9 the rebuild is moving slow. Still at 0.2%, estimated speed is 116KBps and estimated time is 278241 minutes (over 6 months).  Maybe I should have used a bigger hammer to repair the HD.

Have you refreshed the web management page? If not, post a system log.

Have you refreshed the web management page? If not, post a system log.

About 2 dozen times and 5 seconds before I read this post. Up to .05%. At times it has been about 2000KBps but now says 238KBps. Cn I still post a log or does refreshing the web page reset or change it.

 

EDIT: Just looked and my last log is still from Dec 20 and I still have the 1.9GB log from the last rebuild try on Dec 16th.  Also my Flash only has 300KB available so it may not have room to save a log file (does it auto delete last log file for space?)

It appears you've got some type of disk error happening. At least open the syslog and see what drive is having the errors.

 

Delete the old syslog to save a new one.

 

Worst case is you have to give up and you have likely lost the data on disk9 and disk13.

 

It would be really good to know if there is another disk having trouble right now.

 

Peter

One step forward and 3 back. Old disk9 is obviously the problem.

 

1. Old disc9 has crashed again.

2. No files are visible on disk13 and the Music Share is not even showing up.

 

Before disk9 crashed I could see the files on it but didn't write them down. I accept that all my music is gone  :'( and I'm almost 1/2 way re-ripping all my CD's (should take about a month more to complete since I'm saving the classical (which require complex tagging and luckily I was able to salvage a data base out of my iTunes file) for last). Also I can easily re-rip the Blu-ray movies lost on old disk9, but....how can I determine the names of the files missing?

 

1. BUT FIRST: Do I stop the unRAID or let it finish?

2. TO GET LIST OF MOVIES can I take old disk9 out and hammer it, start up unRAID and look/note files on the disk9 (if it will work again)? Or is there another way to determine the lost files?

3. NEXT: Can I replace old disk9 and just start it up?

4. FLASH FULL: Do I need to worry about my flash drive being full with the 1.9GB log file?

EDIT: Following Peter's suggestion I deleted the 1.9GB syslog and no have free space on my flash (for some reason I thought I tried before and couldn't).

5. SHOULD I BUY a lotto ticket?  Having a drive crash during a rebuild must be a rare occurrence so I guess I beat the odds.

:'( :'( :'( :'( :'( :'(