I am working on my uncle's unRAID box and his array is showing one of the disks in the array as being "unformatted." I checked the log file and found the following messages for the "unformatted" disk:

 

Tower kernel REISERFS warning (device md2): jdm-2006 create_privroot: xattrs/ACLs enabled and couldn't find/create .reiserfs_priv. Failing mount.

 

Tower emhttp: disk2 mount error 32

 

I've done some checking on the forums and ran the following command:

 

resierfsck -y /dev/md2

 

I let the program run but it did not find any errors in the file system.  His box is running unRAID 4.5 and the emhttp reports that the parity is valid.  Should I rerun with the --fix-fixable tag or what should be my next step on this drive?

 

I am working on my uncle's unRAID box and his array is showing one of the disks in the array as being "unformatted." I checked the log file and found the following messages for the "unformatted" disk:

 

Tower kernel REISERFS warning (device md2): jdm-2006 create_privroot: xattrs/ACLs enabled and couldn't find/create .reiserfs_priv. Failing mount.

 

Tower emhttp: disk2 mount error 32

 

I've done some checking on the forums and ran the following command:

 

resierfsck -y /dev/md2

 

I let the program run but it did not find any errors in the file system.  His box is running unRAID 4.5 and the emhttp reports that the parity is valid.  Should I rerun with the --fix-fixable tag or what should be my next step on this drive?

 

Send an e-mail to support@lime-technology 

This seems to be a bug in handling the reiserfs file-system  mount (Or at least, googling for the error string make me think so) 

 

Since the "mount" command is apparently trying to use extended access-control-list attributes, you might try changing the "security" on your server to "simple"  and perhaps it will not look for the .reiserfs_priv file it seems to be complaining about.  I do not think you have file-system corruption based on what you've reported.    (And no, you would not run fix-fixable unless the prior reiserfsck requested you do so.)

 

Joe L.

Thanks Joe, I sent Lime Tech and email and will await their response.  The security on the server is already set to simple but I'll try resetting it just in case.  As you have correctly gathered, the disk and its contents are good, unRAID just isn't recognizing it as formatted for one reason or another.

All,

 

I was able to work with Tom on this issue and here is what happened.  The disk that appeared unformatted in 4.5 was because it was filled to capacity.  Tom suggested that I downgrade to a previous version.  I downgraded to 4.4.2 and was able to successfully mount the disk.  I then found the disk only had 4kb free.  On 4.5 this causes problems due to how unRAID handles the file system. Tom explained it best and here is how he described the issue:

 

"The error being reported has to do with creating objects in the file system related to extended attributes.  Extended attributes have been enabled in unRAID's linux kernel for a few releases now - it's necessary for supporting Active Directory, and if you're not using Active Directory, it does still create a few 'placeholder' objects.  The error message in the code is related to a failure to create such an object, which would indicate the disk is completely full."

 

So after I cleared some files with the disk mounted in 4.4.2 I upgraded back to 4.5 and the disk was able to be successfully mounted.

All,

 

I was able to work with Tom on this issue and here is what happened.  The disk that appeared unformatted in 4.5 was because it was filled to capacity.  Tom suggested that I downgrade to a previous version.  I downgraded to 4.4.2 and was able to successfully mount the disk.  I then found the disk only had 4kb free.  On 4.5 this causes problems due to how unRAID handles the file system. Tom explained it best and here is how he described the issue:

 

"The error being reported has to do with creating objects in the file system related to extended attributes.  Extended attributes have been enabled in unRAID's linux kernel for a few releases now - it's necessary for supporting Active Directory, and if you're not using Active Directory, it does still create a few 'placeholder' objects.  The error message in the code is related to a failure to create such an object, which would indicate the disk is completely full."

 

So after I cleared some files with the disk mounted in 4.4.2 I upgraded back to 4.5 and the disk was able to be successfully mounted.

Wow... excellent news...  This definitely is a new one for me. 

 

Joe L.

I have been running 4.5-beta6 for about a year without any issues. Decided it was time to upgrade to 4.5-final for the new year. Today I did a clean shutdown (by stopping the array and then powering down using the web interface). I backed up my USB and then copied over bzroot/bzimage/memtest from the 4.5-final zip onto the USB. Immediately upon booting 5 of my 8 hard drives appear as "unformatted". These hard drives weren't completely full (as PhatalOne had reported), but were mostly drives that had a large amount of free space. In fact, it seems that my drives with nearly no free space mounted correctly.

 

I again did a clean shutdown, loaded back 4.5-beta6, and all of the drives mount correctly.

 

Not sure what to do here? I don't understand why these drives would be having trouble mounting...

I have been running 4.5-beta6 for about a year without any issues. Decided it was time to upgrade to 4.5-final for the new year. Today I did a clean shutdown (by stopping the array and then powering down using the web interface). I backed up my USB and then copied over bzroot/bzimage/memtest from the 4.5-final zip onto the USB. Immediately upon booting 5 of my 8 hard drives appear as "unformatted". These hard drives weren't completely full (as PhatalOne had reported), but were mostly drives that had a large amount of free space. In fact, it seems that my drives with nearly no free space mounted correctly.

 

I again did a clean shutdown, loaded back 4.5-beta6, and all of the drives mount correctly.

 

Not sure what to do here? I don't understand why these drives would be having trouble mounting...

 

We can't do much to help unless you caprture a syslog after booting with 4.5 final.  If you can do that again, capture the syslog and then post it we may be able to point you in the right direction

Hmmm. I put 4.5-final back on the USB, booted up, and everything seems fine this time. Very strange. Hopefully that last boot was just a fluke.

Just experienced a similar issue (4.5.3). I had my server up and running without my parity drive assigned so i could transfer data to my server. Once this completed i stopped the array, assigned the parity drive and then restarted the array.

 

Upon restarting, my disks showed up as "unformatted", however parity is building now and fingers crossed (and from reading the numerous threads) this is just a GUI glitch and all that data is still there!  

 

I have sent an email with my syslog to [email protected]

 

Just experienced a similar issue (4.5.3). I had my server up and running without my parity drive assigned so i could transfer data to my server. Once this completed i stopped the array, assigned the parity drive and then restarted the array.

 

Upon restarting, my disks showed up as "unformatted", however parity is building now and fingers crossed (and from reading the numerous threads) this is just a GUI glitch and all that data is still there!  

 

I have sent an email with my syslog to [email protected]

 

Just do NOT press the Format button.  If anything, give the disks some time to come online initially. (It could take 5 minutes or more before they replay their transactions)

 

Once parity is calculated, you should stop the array, reboot, and with any luck it should all come online.  (The parity calc should not care if the disk was mounted or not, as it is at a much lower level than the mounted file-system.) 

 

Joe L.

I am also having this problem as of today. I am running 4.5.3 and had the computer turned off for a couple of days. Before that, it was running perfectly fine; 2 data disks, one parity, one cache. I just brought it up again, and the data disks are being reported as unformatted and a parity check was started. I'll let that run through to see what happens afterwards and will report back. Attached is the syslog, in case somebody in the know can have a look.

 

Thanks,

Carsten

 

p.s.: Really would hate to have lost all my data ...

 

update: The parity check didn't find any problems with the disks, but they are still listed as unformatted. I would like to try a re-boot, but the system hangs when trying to shut it down. It seems to try to unmount the cache disk ... I am forcing a reboot via ssh and '/sbin/shutdown -r now'.

 

update 2: Reboot didn't do anything for me, so I ran reiserfsck --rebuild-sb on /dev/md1 and /dev/md2 using the values found http://lime-technology.com/forum/index.php?topic=1483. After completion, it recommended running reiserfsck --check, which I did. This time, two errors were found, "0 after last valid bit" and something about a "bitmap" difference. It guessed that using the --fix-fixable option would do the trick on these errors, which it did. Yet, after another reboot, unRAID still showed the data drives as unformatted. I stopped the array form the GUI and restarted it (from the GUI). This time, the data disks came up clean and I ran a parity check overnight; no problems reported. Glad to have my data back and I am currently running a backup ... I might switch back to 4.5.1 for now. It's not clear to me how a reboot of the system isn't equivalent to stopping and starting the array from the GUI, but there you go.

 

update 3: I am having the same problem once again. Both data disks are being reported as unformatted. Upon restart, the mdrecoveryd process gets started and I cannot access the web gui. I'll wait a little while to see if that daemon terminates by itself.

syslog.txt

update:

 

parity completed over night with no errors

 

I stopped the array, waited a few moments and then restarted the array. Hey presto, everything is fine and the UI is showing all the correct info and my data is still there!

 

Happy days! 

 

just doing my parity check now... hmm another 8 hours to wait, i am so impatient