Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Read-Only File System issue

Featured Replies

I set up a small unRAID Plus server for my parents and am now running into some issues that im hoping you guys can help me solve. Right now the only plugins it is running are SAB, SickBeard, CouchPotato and it has about 2.2TB of free space left. Right now what happens is everything will run just fine for some amount of time and then eventually everything just stops functioning until i stop/start the array.

 

If i try to stop/start any of the applications it mentions a read-only filesystem as an error.

 

It currently has a 1TB, 2TB, 3TB drive in it and a 500G cache drive and no parity. There is 270G, 220G, 1.83TB of space left respectively on each drive.

 

I have added a portion of the syslog as it was too big to attach and it seems to reference some out of space issues even though it clearly is not out of space. If someone needs the entire log let me know and i can email it to them or host it somewhere.

 

Please let me know what my next steps should be

 

EDIT: This box is currently running on rc11

syslog.txt

EDIT: Im fairly positive that it is running rc12 but im not sure how i can check it. The web interface doesnt appear to be responding, however unMENU is. Is there somewhere in unMENU i can find out which version it is using?

 

If you are on the UnMenu main screen and click on "UnRAID Main" you should get to the primary Web GUI display, which will show the version # you're running.

 

If you can in fact get to the main UnRAID screen, post a picture of it here - it may provide some clues.

 

Meanwhile, I'd revert to a "stock" UnRAID (no plugins) to confirm whether or not you're having an issue with UnRAID or if it's plug-in related.

 

  • Author

If you look at the syslog to me it appears that having the plugins installed would be the only way to know if the issue is occurring. Maybe im missing something though as im not really sure how to read it in the first place.

If you look at the syslog to me it appears that having the plugins installed would be the only way to know if the issue is occurring. Maybe im missing something though as im not really sure how to read it in the first place.

 

Possibly, but the first step in isolating a problem is to determine whether it's an UnRAID issue or a plug-in issue.

 

I also noted you indicated "... EDIT: This box is currently running on rc11 "  ==>  the FIRST thing you should upgrade to RC12a to confirm you're not dealing with an obsolete issue.

 

  • Author

Agreed, however, that box is 4 hours away from me and im a little bit afraid of remotely upgrading it when im not there to fix it if something goes awry

  • Author

I just re-started the array and then invoked the mover and noticed some new issues in the syslog. Maybe these will help

 

May 21 16:07:25 Tower logger: mover started

May 21 16:07:25 Tower logger: moving TV/

May 21 16:07:26 Tower logger: ./TV/Psych/Season 6/Psych - s06e02 - Last Night Gus.mkv

May 21 16:07:26 Tower logger: .d..t...... TV/Psych/

May 21 16:07:26 Tower logger: >f..t...... TV/Psych/Season 6/Psych - s06e02 - Last Night Gus.mkv

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS (device sdc1): Remounting filesystem read-only (Drive related)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

May 21 16:07:38 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 61739 does not match to the expected one 1 (Minor Issues)

May 21 16:07:38 Tower kernel: REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in block 34205276. Fsck? (Errors)

  • Author

I assume isnt normal behavior but i started running the command as the link in your sig suggested. My telnet session died and when my parents checked the box out it was turned off. I had them turn it back on, however, now i can ping the box but cannot access anything else and it has been 4 hours. Any thoughts on this one?

My telnet session died and when my parents checked the box out it was turned off.
Sounds like a hardware issue. Beating on the software while you have dodgy hardware is likely going to cause more harm than good. I know it's a trip, but I think it would be better to retrieve the box and troubleshoot for real.

Agreed, however, that box is 4 hours away from me and im a little bit afraid of remotely upgrading it when im not there to fix it if something goes awry

 

You need to visit your parents this weekend; bring the system home;  FIX it next week;  and then visit them again the following weekend  :)

 

... as jonathanm said in the post above (just noticed it), you don't want to "beat on the software" when the issue isn't obvious -- it could be "dodgy hardware", or it could be a software configuration issue.  But it will be MUCH easier to resolve if you simply go get the system and fix it at home ==> in fact, the total time spent may actually be less even when you factor in the drives [AND I'm sure your parents will appreciate a chance to visit  :) ]

it could be a software configuration issue.
I've never seen a running linux system power itself off after a command was issued for a disk check. Either there was a power blip, or the PSU or motherboard or CPU is having issues. Could be heat, could be lots of things. My bet is a failing or overheating PSU.

 

There's been at least one instance of a well meaning relative cooking a pc to death because they tried to muffle the fan noise by putting a blanket over the machine.

 

That PC needs some hands on troubleshooting.

  • Author

So it appears that there was a power flicker while i was running it. I was able to run the reiserfsck --check on all disks and it reported no corruptions. Any suggestions now?

So it appears that there was a power flicker while i was running it. Any suggestions now?

Get a battery backup installed, stat.
  • Author

How does one go about checking the cache drive for file system errors? I just had a thought that maybe thats where the issue is as i see errors when the mover is running and the apps that run on the cache drive

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.