Everytime I restart my server, disk19 shows as "blue" and the array says "Start will bring the array on-line, start Data-Rebuild, and then expand the file system."

 

Brand new drive, precleared fine, 0 smart ERRORS. There is 0 data on the drive, yet unRAID somehow thinks its corrupt or something.

 

I added 3 of these drives at the same time, did the same process for all 3. Only one is having issues.

 

Running 5.0 Beta4.

 

SMART Results:

http://img25.imageshack.us/img25/6011/smartz.png

syslog.txt

Also, any idea what this is? It was added to my flash drive 7 days ago (the day I added these 3 hard drives).

 

Can I delete either of these? It seems like they are the same file, but one fails to include my new disks (17-19). Is this something to do with them being 4k alligned?

That file in your image means you probably ran "New Slots" at some point (available in "Utils")

 

Have you tried booting with 4.7 to see if the behaviour is the same? It may be a beta issue (I've had this happen to me on a 500GB drive.

 

My recommendation would be to try 4.7 to make sure it's nothing that was "changed" in the 5.x branch.. Could also be a bug..

 

Cheers,

 

That file in your image means you probably ran "New Slots" at some point (available in "Utils")

 

Have you tried booting with 4.7 to see if the behaviour is the same? It may be a beta issue (I've had this happen to me on a 500GB drive.

 

My recommendation would be to try 4.7 to make sure it's nothing that was "changed" in the 5.x branch.. Could also be a bug..

 

Cheers,

 

 

I don't know how to go back to 4.7 since I had to run the permissions thing when upgrading to 5.X.

 

I ran "New Config" and resynced parity, restarted server and same thing. I feel this is definitely a bug... in my log is says "missing disk" when its not.

It is most definitely a bug, fixed whenever beta5 comes out.

 

Swapped an old (known to be 100% working) drive to disk19 and disk20. Same thing.

 

Definitely a bug. A rather major one at that... Not sure how this got through testing.

You are running a beta of the 5.0 series.

 

There is a known issue with disks not staying in the same place with 5.0b4, though your issues sounds a little bit different.

 

You can go back to 4.7 if you like, just make a back of the contents of your config folder and make a screen print of the devices page as you will have to reassign drives more than likely.

This is the entire point of betas, to test. It's also why next-gen betas should not be applied to production servers.

 

Not all hardware behaves the same. Sometimes the same hardware doesn't even behave the same. Something like this could easily pass internal tests but not be seen until it was used on the many different setups.

 

 

Confirming that going back to 4.7 fixed the issue.

Confirming that going back to 4.7 fixed the issue.

 

Good to here that did indeed fix the issue.

 

You may want to send an email to LimeTech with a link to this thread.

 

If you can also provide a syslog running under 4.7 then boot 5.0b4 and provide another syslog that may help LimeTech nail down the issue you were seeing.

Ok good I am seeing this in the beta too with 500MB drives.  The order changes.  I was thinking this was related to being inside a VM (qemu-kvm).