We are running 4.2.1. Whenever we restart the server we have to do a parity sync. We use the stop button in admin. When everything stops we then hit the shutdown button. This should bring the server down gracefully. Before we bring down the server the admin page says parity is valid. But when we reboot parity is not valid.

 

This will be a big problem if one of our drives goes bad & we have to rebuild from the parity drive. When we ran 4.1 we never had this problem. We could go weeks and never had to rebuild parity.

 

We have since bought the pro key & we purchased the supermicro 8 port sata card. Unfortunatly only version 4.2.1 has drivers for this card so we cannot revert back to 4.1

 

Another problem we have is if we map our user shares to a network drive. If we do this and copy a few gig to this then the server will loose connection. So we have not been able to map network drives. We are running XP service pack 2.

 

One other problem we have is if we write to a disk share then we have to always to a parity resync.

 

We still love our unraid box we are just concerned if we do have a hard drive go bad then we will loose data.

 

Thanks for listening.

 

Phil

I have just completed the parity sync. Everything looks fine & the admin page says parity is valid.

 

I have not written anything to this server after the parity sync.

 

I told the drives to spin up from the admin page in case this was the problem. I hit the stop button to stop the array. I then used the power down button to shut down the server. I watched on the monitor for my unraid server & saw it shutting down the drives & also syncronysing them. Then the machine powered down normally.

 

The only thing I noticed was at the tower login it sayed disabling intrupt #7. I never saw this with version 4.1

 

I brought up the server & it started to do a parity sync. I just can't figure out what is wrong. Any help would be appreciated.

 

Thanks

 

Phil

The flag that indicates that the array was stopped cleanly while parity is sane is stored on the flash drive as part of the superblock file (super.dat)

 

Is it possible you have a "write protect" switch on your flash drive and it cannot update the super.dat file located in the /boot/config folder?

Thanks for the reply. I just checked and the super.dat file at least in windows under properties says hidden & archive. The file was updated today at 2:32 PM . So that does not seem to be the problem. Any other help would be appreciated.

I think I fixed the problem. I removed the cable from the parity drive. It was connected to the Supermicro 8 port sata card. I connected the drive to the sata ports on the motherboard. I rebuilt parity & cannot break it now. I have powered down my unraid server about 10 times & each time parity was valid. I hope this can help someone else who might have the same problem.

 

By the way all of our data drives running on the Supermicro card seem to be doing fine.

 

Thanks