Hiya,

 

I am having some ongoing problems where my Unraid server becomes unresponsive during sustained writes.  It locks up, all shares disappear and it becomes inaccessible either by webgui or terminal.

 

In my quest to identify the problem I have run a smartctl on each drive, with no glaring errors.  I figure the next step is to run a filesytem check on each of the drives to identify if there are any issues there.  I am aware that it is a bad to run a reiserfsck on the parity drive, but need clarification on how to identify which drive is parity.

 

The instructions in the FAQ are to run the below command.  What I need to identify is which device (mdx) the parity drive is, so I don't run this command against it.  Is parity drive always disk0 and hence md0?

 

reiserfsck --check /dev/md1 (disk1)

 

Thanks in advance!

 

Incidentally, is there are way to capture the log when a lock up of this nature occurs?

Parity is disk0 but has no md0 associated with it, no mdX at all. Post your current syslog. See here on how to capture a log just before a crash using Telnet and tail: http://lime-technology.com/forum/index.php?topic=9880.0. Post your system specs as well.

Thanks!

 

I have set up a Telnet and Tail, so hopefully it will capture something useful next time I have a crash.

 

I'll post all relevant info if and when that occurs.

 

Cheers!