I recently had an issue where I found my server was unresponsive. So I did a hard reset, and took a look - I saw lots of read only filesystem warnings, and looking in the plugins directory it looked like the file system was corrupted.

 

SO I put my USB stick in my desktop and it reported it was corrupted. So I did a repair, put it back in the server. It booted, noted an unclean shutdown, then started  aparity check. A minute or so later it went unresponsive again.

 

SO I tried a completely clean install. Just copied the super.dat file and the key file. Same thing happen - system came up, started parity check and then became unresponsive.

 

Interestingly each time I took the USB stick out to try a fix it was reported as corrupted.

 

So im leaning towards a duff USB stick, where its OK enough to boot but once the array starts to come up it breaks, but before I go and get another I was wondering if anyone had any other things I could try?

I think your investigation was pretty conclusive. I suppose you could try to grab diagnostics while the parity check is underway before you lose control of the system, or you could make a new USB stick and test it first with a trial licence but there probably isn't much point. Just make a new one and copy your configuration onto it and let it go through the key replacement process.

 

Looks like its not the USB stick. Bought a new one, clean install, started up, same symptom.

 

I connected a monitor up to it after it went unresponsive, and it looks like there was a kernel panic. By that time the root cause had scrolled off the screen, but I did see part of the error mentioned reiserFS.

 

So presumably I should restart the server, but not the array, then do a file system check?

Check box for Maintenance mode when starting for filesystem check

Thanks. One of the drives needs a tree rebuild apparently...