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.

System Crash when trying to connect

Featured Replies

I tried saving a syslog but it happens so fast I can't get the command in in time. We added 4 new drives and upgraded to Pro. Everything was running fine when one of the older drives became red.  I replaced the drive and let it rebuild. Since the rebuild the system crashes when ever anyone on the netwrok tries to connect to it.

 

As I said, I don't have a syslog but I did take a shot of the screen that appears on the UnRaid right after the crash. I am hoping this will suffice for some type of information on how to resolve this issue.

 

Thanks 

 

B5CwC.jpg

  • Author

Running 5.0 RC3

Replace the go file on the flash with a stock version. Or comment out the changes.

  • Author

Replace the go file on the flash with a stock version. Or comment out the changes.

 

I did that with the Go file, Thanks for the suggestion. In fact I replaced everything but my drives and share information and started from scratch. The same thing happened. Couldn't connect via the network and it would crash the system. I then ran reiserfs on disk 1 and disk 2. Disk 2 had no problems. Disk 1 was messed up and was told to do the --rebuild-tree. Ran that and rebooted afterwards. I can now access over the network. Now, one folder on my main share is not showing up. Via telent I can see the folder but I get a Permission denied when trying to "cd" into it.

 

I brought up my monitor on the unraid and I'm seeing this on the screen.

 

REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in the biock 32777. Fsck?

REISERFS error (device sdc1) : vs-13070 reiserfs_read_locked_imode: i/o failure occurred trying to find stat of [2 520 0x0 SD]

 

When I try to access the share via the UnRaid menu I see almost all the directories except for our main folder. I also see this error on the screen above all the directories.

 

Warning: filetype(): Lstat failed for /usr/local/emhttp/mnt/user/ServerPlus/.AppleDB in /usr/local/emhttp/plugins/indexer/Browse.php on line 21 Warning: filectime(): stat failed for /usr/local/emhttp/mnt/user/ServerPlus/.AppleDB in /usr/local/emhttp/plugins/indexer/Browse.php on line 31 Warning: filetype(): Lstat failed for /usr/local/emhttp/mnt/user/ServerPlus/.AppleDesktop in /usr/local/emhttp/plugins/indexer/Browse.php on line 21 Warning: filectime(): stat failed for /usr/local/emhttp/mnt/user/ServerPlus/.AppleDesktop in /usr/local/emhttp/plugins/indexer/Browse.php on line 31 Warning: filetype(): Lstat failed for /usr/local/emhttp/mnt/user/ServerPlus/New File System in /usr/local/emhttp/plugins/indexer/Browse.php on line 21 Warning: filectime(): stat failed for /usr/local/emhttp/mnt/user/ServerPlus/New File System in /usr/local/emhttp/plugins/indexer/Browse.php on line 31

 

New File System is the Folder I need access to but I can't get into it.

 

  • Author

Click on the "New Permissions" button.

 

Did that as well. Sorry I didn't mention it.

You have some corruption in the file-system on a disk.

REISERFS error (device sdc1): vs-5150 search_by_key: invalid format found in the biock 32777. Fsck?

REISERFS error (device sdc1) : vs-13070 reiserfs_read_locked_imode: i/o failure occurred trying to find stat of [2 520 0x0 SD]

 

See here:

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

Not sure which disk is /dev/sdc1, but you need to fix it by running

reiserfsck --check /dev/mdX

and then following its guidance.

(You should run reiserfsck on the /dev/mdX device affiliated with /dev/sdc1 to keep parity in sync, otherwise you will fix the error but not parity, and a subsequent parity sync will be needed to fix parity.  It is explained in the wiki link I posted above.)

  • Author

I have it running now. The sdc was the cache drive. I'll give feedback when this is complete.

I have it running now. The sdc was the cache drive. I'll give feedback when this is complete.

in that case, thee is no md device.  run the reiserfsck on /dev/sdc1 after un-mounting it.

 

umount /dev/sdc1

reiserfsck --check /dev/sdc1

 

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.