This problem started early this morning appears to be continuing.  I attempted to replace some memory in my unRAID server this morning, but I'm guessing a module was bad as I encountered a couple of spontaneous reboots on the next couple of reload attempts.  I put in two known working modules (a downgrade to 2GB) and all was working well.  When it finally came up, all my disks were blue (I have 9, including parity), so I checked off Restore and started the parity calculation.  All data was fine and 10 hours later it was working as before.

 

Now, I have a 1TB drive that I've been wanting to put in as an upgrade to a 500GB for a while now and finally found the time tonight.  I stopped the array and did a clean power down, swapped the drives and booted back up.  All of my drives were blue again.  I put the 500GB back in, started it up and it's going through parity calc again.

 

I'm not real sure how to continue.  I need to get this drive upgraded, but I'll never get there if it's going to wipe my config out every time I reboot.  Syslog attached (from last reboot only, unfortunately.  I'll be sure to save if I try and fail again tomorrow).

 

 

 

 

Ugh.  I'm having my array show up as new upon every reboot now.  Anyone have an idea what I need to do to clear this up?  4.5b6.

wow you're a brave man setting up a real server with a beta version. It might be a bug. Get syslog and email it to Tom? I'm sorry i cant be any more help as i'm very new to unRAID.

 

Some veteran users should chime in and figure if this is indeed a bug.

 

The features in the 4.5beta6 version that make it "beta" have to do with active directory support and expansion of capacity to > 16 drives.  Neither involve the creation or establishment of a new array.  I'd not worry about using it on a new array.

 

The symptoms you describe would occur if your flash drive was not writable.  Unfortunately, the syslog you posted does not show you assigning drives.

 

Please assign your drives, start the array, let it calc parity, then stop the array and post a syslog.  Then we'll be able to see how it fails to save the configuration in the config/super.dat file.

 

Do not reboot at that point, just re-start the array.  Odds are we'll see messages in the syslog showing the flash drive is not writable.   You might run chkdisk or scandisk on it in your PC if it shows its FAT file-system is corrupted (perhaps you did not eject it safely from the PC after setting it up)

 

Also, when you get a chance, run a memory test overnight... (or at least for a few cycles) It it a choice on the boot menu when you first start the unRAID server. 

 

Joe L.

Thanks Joe...it has just about an hour left on the parity check to go since starting it last night.

 

I don't know why the flash would not be writable...I've been using it for a year and a half without problems (always upgrading to the latest and greatest when available).  Hopefully it's not going bad on me...I've never taken it out of that server since the initial setup last March.  Come to think of it though, I do remember failing to install BubbaRAID due to some directories not being able to be created or missing.  That was after the first issue with this though,

 

I'll post the syslog in about an hour and I'll run the memory check on it tonight when it's not in use.

 

EDIT:

 

Flash is definitely not writable.  I tried to copy a file and create a text file on it and both failed.  Still running parity, but I'm guessing that's a lost cause since it won't be able to write to the super.dat.

Flash is definitely not writable.  I tried to copy a file and create a text file on it and both failed.  Still running parity, but I'm guessing that's a lost cause since it won't be able to write to the super.dat.

At least you know what the root cause is...  might be as simple as running chkdisk or scandisk on it.

That's what I'll do when I get home then.  Hopefully that's all it is and it does make sense.  I'd assume that file system got partially corrupted when it had those two reboots due to the bad memory module.

 

I'll report back this evening after I get a chance to run a check against my flash drive.  Thanks again!

FYI, the flash drive did have errors after running scandisk against (super.dat, to be exact).  It was able to fix them and after plugging it back into my unRAID box and starting up, I was able to write to it again.

 

I'm still going through a parity calc which will last until early tomorrow morning, but I'm pretty certain that's going to fix it.  If not, I'll be sure to put it here

 

Thanks again for the tip, Joe!