So everything was running smooth and silk for about a month (Sickbeard and Sabnzbd).

 

Well, I came home today and saw that the server wasn't downloading. When I navigated to the sabnzbd and sickbeard url I got this error. I have no idea what this means or what I should do.

 

The only thing I can think of is I upgraded to RC8 from RC-5 yesterday, but everything still ran fine after the upgrade yesterday so I don't know what happened.

"

500 Internal Server Error

 

The server encountered an unexpected condition which prevented it from fulfilling the request.

 

Traceback (most recent call last):

  File "/mnt/cache/apps/sabnzbd/cherrypy/_cprequest.py", line 618, in respond

  File "/mnt/cache/apps/sabnzbd/cherrypy/_cpdispatch.py", line 25, in __call__

  File "/mnt/cache/apps/sabnzbd/sabnzbd/interface.py", line 281, in index

  File "/usr/lib/python2.6/site-packages/Cheetah/Template.py", line 1259, in __init__

    self._compile(source, file, compilerSettings=compilerSettings)

  File "/usr/lib/python2.6/site-packages/Cheetah/Template.py", line 1546, in _compile

    self._fileMtime = os.path.getmtime(file)

  File "/usr/lib/python2.6/genericpath.py", line 54, in getmtime

    return os.stat(filename).st_mtime

OSError: [Errno 13] Permission denied: '/mnt/cache/apps/sabnzbd/interfaces/Plush/templates/main.tmpl'

"

 

500 Internal Server Error

 

The server encountered an unexpected condition which prevented it from fulfilling the request.

 

Traceback (most recent call last):

  File "/mnt/cache/apps/sickbeard/cherrypy/_cprequest.py", line 660, in respond

  File "/mnt/cache/apps/sickbeard/cherrypy/lib/encoding.py", line 193, in __call__

  File "/mnt/cache/apps/sickbeard/cherrypy/_cpdispatch.py", line 25, in __call__

  File "/mnt/cache/apps/sickbeard/sickbeard/webserve.py", line 1953, in index

  File "/mnt/cache/apps/sickbeard/sickbeard/webserve.py", line 120, in _munge

  File "/usr/lib/python2.6/site-packages/Cheetah/Template.py", line 1010, in __unicode__

    return getattr(self, mainMethName)()

  File "_mnt_cache_apps_sickbeard_data_interfaces_default_home_tmpl.py", line 105, in respond

  File "/mnt/cache/apps/sickbeard/sickbeard/db.py", line 51, in __init__

OperationalError: disk I/O error

I then checked the log file and got this:

 

Nov 12 13:32:53 unRAID last message repeated 9 times

Nov 12 13:33:02 unRAID kernel: sd 4:0:0:0: [sde] Unhandled error code

Nov 12 13:33:02 unRAID kernel: sd 4:0:0:0: [sde] Result: hostbyte=0x04 driverbyte=0x00

Nov 12 13:33:02 unRAID kernel: sd 4:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 04 13 10 00 00 08 00

Nov 12 13:33:02 unRAID kernel: end_request: I/O error, dev sde, sector 267024

Nov 12 13:33:02 unRAID kernel: REISERFS error (device sde1): clm-6001 reiserfs_truncate_file: grab_tail_page failed -5

Nov 12 13:35:42 unRAID /usr/local/emhttp/plugins/webGui/scripts/pre: pre cat /var/log/syslog: exit status:1

Nov 12 13:36:33 unRAID kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

Nov 12 13:37:00 unRAID last message repeated 23 times

Nov 12 13:38:20 unRAID /usr/local/emhttp/plugins/webGui/scripts/pre: pre cat /var/log/syslog: exit status:1

Nov 12 13:39:39 unRAID kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

Nov 12 13:39:39 unRAID last message repeated 3 times

Nov 12 13:39:43 unRAID /usr/local/emhttp/plugins/webGui/scripts/pre: pre cat /var/log/syslog: exit status:1

-------

 

I went into the plugin setting of each app and they showed as "Uninstalled"

sdE is my cache drive

The drives has a green circle next to it and is showing 0 errors in the console.

 

Can someone please help me out here?

Oh my goodness.

So I figured I would stop the array and look inside maybe a cable got unplugged or something (even though the server is stationary). Well I click on "stop" and it seems like unraid can't stop! It can't seem to unmount the discs and won't shut down. I am getting this message

 

Stop SMB...Spinning up all drives...Sync filesystems...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)...Unmounting

 

Now I can't even log back into the console, or do anything but the actual server computer isn't powering down? I guess I'm gonna have to force a cold shut down...

 

Can someone help me figure out what's going on? This sucks just as I am in the middle of building another server

 

**EDIT**

Okay so I had to just unplug the power from the server to get it to turn off. There was no other way, no?

Powered everything back on and it is now working beautifully as if nothing had even happened (Parity check is now in progress of course).

 

What happened guys?

 

Wow, no one could help me out? I don't know what do ...

It sounds like something is wrong with the cache drive. Maybe a filesystem issue. I'd run the reiserfsck checks as listed in the Wiki on it. Make sure to use sde1 and not just sde (or the new drive letter if it changed at boot). I believe a "killall -9 python" on the command line would have helped by killing the python that was still running. You can also watch during the shutdown. I've had all the drives but the cache get unmounted and then you can force a reboot since the array is safe.

 

My cache drive goes read-only every now and then. There is no indication of the issue on the unRAID or unMENU interfaces. I have to check the log to find out.

I decided to just replace the cache drive. It was an old 2.5" SATA drive from a laptop. I ordered a new one for $50 that should arrive tomorrow, hopefully everything will work now. Although I will have to set up the applications all over again.

 

I don't understand why it had a green light on the console though, I would expect it to be red to tell me that something is wrong..

I decided to just replace the cache drive. It was an old 2.5" SATA drive from a laptop. I ordered a new one for $50 that should arrive tomorrow, hopefully everything will work now. Although I will have to set up the applications all over again.

 

I don't understand why it had a green light on the console though, I would expect it to be red to tell me that something is wrong..

I have no idea how the "red" indicator works on a cache drive, but on the protected data drive is it "red" only when a "write" to the disk fails.    Probably the same on the cache drive.

 

Your issue seems to be applications of programs you've installed are keeping the cache drive busy, so it cannot be un-mounted, so the array cannot be stopped.  There are many add-ons that require you to stop them first, before the array.  (Some do stop themselves, others are not as sophisticated)

 

A read-only file system is just one where corruption of the file-system was detected, so the file-system was made read-only to prevent more corruption.  A reiserfsck would fix those issues.