See check file systems in my sig.

Smart results are ok. So now the filesystem check, issue will be there..

 

 

Sent from my iPad using Tapatalk HD

So I tried following the directions from the reiserchck. It rebuilt a few things and then gave up saying I need to pay $25 to get real help. I do not really feel like going down that path. I thought why don't I run preclear on this thing and start from scratch...nope that is not an option, since unraid thinks it is a valid disk (really need to have a way of marking a disk as invalid). So I went out and bought another disk, and started the rebuild over again.

 

Once again...approximately 12 hours into it I lost connectivity...nothing on the console.  I let it run another 10 hours...still nothing:( I reboot and this time at least it is attempting to rebuild again, because I really don't want to go buy yet another HD.

 

I have feeling that something on the network maybe trying to access it during the rebuild and causing it to wedge, so I'm disconnecting it from the network this time. Which raises another question: Is there away to monitor the rebuild progress from the command line?

 

Sorry, but I am baffled on this and would not know how to give more help..

 

Joe ?

Why does unraid use reiser format? I would feel a lot more comfortable now if I were able to read my disks from one of my other PCs.

 

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

 

 

Unraid=unix not windows

Why does unraid use reiser format? I would feel a lot more comfortable now if I were able to read my disks from one of my other PCs.

 

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

 

You can read them. Install a reiserfs driver.

Any recommendations for reiserfs drivers for Win7? It appears there are several out there, just trying to avoid weeding thru the chaff:)

 

B2

Ok my new hardrive cpmpleted the rebuild!! I had the system disconnected from the network to insure no other computers tried to access it during the rebuild process and I was using a vanilla Unraid 4.7 image. Now it appears that it has marked the filesystem on this disk as readonly. From some googling, this appears to be due to reiser problem...really? A freshly rebuilt HD has a reiser problem? so I performed a reiserfsck --check on it and it told me I needed to rebuild-tree. So I am currently rebuilding the tree. How long does this typically take? So could bad parity information screw up the reiserfsck? I am pretty sure I had corruption and bad parity.

 

Unraid REALLY REALLY needs a way to reset the configuration back to the original HD and recompute parity!!! I think I would be good if I did that. Of course now I am concerned about data on my other drives being corrupted due to the bad parity.

 

B2

Bad parity can't screw up the data on your other drives. The only drive that is written during parity checking is the parity drive... except... when you are rebuilding a new disk. Then it's working backwards from parity data to get what should be on that drive. That's the beauty of unraid, each disk is an independent file system so if you do loose 2 drives, you only loose data on those drives.

 

Remember:

 

Drive 1 + Drive 2 + Drive 3 + Drive 4 = Parity

 

When you replace Drive 2, it rebuilds the data by this:

 

Parity - Drive 1 - Drive 3 - Drive 4 = Drive 2

 

To me it sounds like a bad filesystem on one of your drives had made your parity bad when you started (correct parity for the corrupted data), so when it tried to rebuild the new drive, all hell broke loose. The parity process doesn't care what's on your disks (or if the file system is bad) as it just sums up bit by bit across the drives and stores the check bit on the parity drive. I had major problems with a disk upgrade (my was due to a read-only flash drive not storing the new drive configuration) and here's what i did.

 

NOTE: I'm on 5.0rc6 when this happend.. so I don't know if this applies to 4.7 as I have never used it. 5.0 can figure out how to organize your disks (or at least it doesn't care), as long as you can identify which is the parity drive. I don't know if 4.7 can do that.... maybe someone else can weigh in on this?

 

I upgraded one disk and rebuilt, did a parity check, rebooted and then upgraded a second disk. Everything broke because unraid didn't know that the first new disk was good... so it was trying to emulate that disk, and now I had taken a second disk from the system. I also think that some data had been written to the array (changing the correct parity values) at some point during the process making things even worse.

 

1) fix my read only boot drive and ensured the array was not being used.

2) put both old disks back in and reset the drive configuration.

3) selected the parity drive in the parity slot, and then just added the other drives and started the array

4) it came online and wanted to do a parity check - this rebuilt valid data for the old array of disks.

5) replaced a single disk and let it rebuild the data - since no data had changed, the parity data was still valid - did a check just to make sure.

6) rebooted to make sure the drive configuration had been saved and it worked properly - all data was in tact

7) replaced the second disk and let it rebuild the data

 

Upgrading a disk relies on the safety net that the parity drive provides to rebuild the data - so you have no drive redundancy while this is happening. To me, it would be nice if there was a system to do a raw copy from an old drive to a new one so you are protected the entire time. I don't know if that would work given the bit level parity check that is happening - but it seems like it would be good in theory. Using the current disk upgrade process, your array must be perfect before you upgrade. I would have thought that unraid would have given you a red ball if one of the file systems was bad, but I guess not.

 

If someone can confirm that 4.7 will find the correct array drives from a clean configuration, I'd start over, rebuild a new parity and the try the upgrade again.

 

Good luck..

 

whiteatom

This sounds like what I want to do. It is step 2 that I do not know how to do: how do you reset the drive configuration back to the old configuration? BTW I have 8 drives plus a parity and a cache drive.

Rebuilding a drive will not fix file system errors.