Problem 1: My tower has 13 500GB disks. When adding disk number 14 it showed as new, I cleared it, formated it and started moving files to it - all worked great. After a restart of the tower the new disk was gone... When I re-assigned it, it appeard again as new and suggested clearing it (which I didn't do as I dont want to loose the data I just moved to it). Trying to 'restore' so all disks appear as new and the parity will get rebuilt does nothing (very odd). I'm on 4.0b9. My guess is that the configuration files that hold the disk info got screwed up or something? Can I just delete them and assign all disks from scratch and get the parity disk to rebuild or something?

 

Problem 2: after a while the tower looses network connectivity. It responds to ping, but the web access doesn't work nor can I telent to it (and obviously the shared disks are gone as well). I can access it through its console and it looks alive, and I can ping from it to the outside world. It happens after a few hours of being online. Very odd and very upsetting as i need to reboot it everytime this happens.

 

Problem 3: i wanted to upgrade to 4.0final, but when accessing the flash drive over the network, I get 'permmision denied' when trying to copy bzroot etc on to it. I could take the thumb drive out, plug it to another PC and overwrite the files, but i thought that i should be able to do this from remote? the share page does allow read/write to the flash drive, obviously.

 

Thanks for your help,

Shahar

bump?

Hello? Is there anybody out there? 

Start troubleshooting...

Change cables, check seating, all the usual like,,,hmm. post syslog.

Read up on the many posts from Joe.L, and the rest of the frequent writers.

/Rene

 

 

Are you writing to the "User-Shares" ?  or to /disk1,/disk2,/disk3, etc?

 

If you write to User-Shares, you stand a good chance of running out of memory... User-Shares should always be set to read-only.

 

Your symptoms seem to indicate that processes are being terminated because memory is not available.

 

How much ram in your array?  Do you have the recommended 512 Meg of ram?

 

As others have said... post a copy of the syslog when errors occur.

 

Of course, once you get things working, you might want to upgrade to a newer release of unRaid.

 

Joe L.

 

To close the loop on this:

I deleted all configuration files, copied them from the installation package again, rebooted the tower, assigned all 14 disks the same order they were assigned before and 'restore'd the array, having the parity rebuilt. All is working great now for 48 hours with no glitches. As I suspected one of the configuration files got corrupted or something and that caused all these odd stuff.