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.

Can't access server anymore

Featured Replies

I do not believe that this has anything to do with V6beta3, so I decided to post my issue here.

 

I was implementing a cache drive as the VM's are going to be installed on it - since then I had multiple issues. The final issue was when I was invoking "manual mover" via the WebGUI. The server can only accessed locally since then. After having tried to delete an old sparse bundle file I suddenly saw the picture that I attached (I was trying to delete the file as I have a new Mac and wanted to start over with a new Time Machine file plus reiserfsck was showing errors on /dev/md1).

 

Some more information that might help:

  • My cache drive is a mirrored SSD
  • A memtest ended w/o error

I'm desperate seeking for help  :-[

  • Author

You are right - of course. I was not sure how to get the syslog from the server but here it is and some new development.

 

I rebooted the router and have access to my unRAID server again. However it was crashing again.

 

I will run a reiserfsck for all 7 drives. (EDIT: saw that reiserfsck for /dev7md1 was killed):

Checking internal tree.. \/  3 (of  26\/ 65 (of 170|/139 (of 170\Killed

.

WebGUI was trying to unmount shares and I saw that one VM was still running. I had to xl destroy it.

 

Can you read something from the log? Seems to be ok.

  • Author

I ran reiserfsck for all disc's. No errors at all, e.g. disk1:

###########
reiserfsck --check started at Mon Feb 17 18:22:16 2014
###########
Replaying journal: Done.
Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed
Checking internal tree.. finished                                
Comparing bitmaps..finished
Checking Semantic tree:
finished                                                                       
No corruptions found
There are on the filesystem:
Leaves 668066
Internal nodes 4011
Directories 21
Other files 308679
Data block pointers 614930882 (28 of them are zero)
Safe links 0
###########
reiserfsck finished at Mon Feb 17 20:29:46 2014

 

I returned the server from maintenance mode. Deleting the sparse bundle directory where the server crashed last time. Seems to be working now and I don't know why.... ???

 

  • Author

I think I know why my server is crashing - whenever the cache drive is running full it crashes. Is that a known issue? Linked to V6beta3?

The syslog shows only 5 minutes of activity. Copy the syslog after the problem occurs. See SYSTEM LOG in my sig for various methods of copying the syslog.

  • Author

Thanks dgaschk - difficult to get the syslog when the server is continuously crashing. However, new syslog and dmesg is attached. This is also something that might cause issues:

FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Did you run reiserfsck on the cache drive? Run disk check on the flash in a Mac or PC.

  • Author

No reiserfsck on the cache. Would

reiserfsck /dev/sdb 

the correct command for MR2020-_2S-S2R_Raid_1 (sdb) 244198552? The server need to be in Maintenance mode?

 

And I will definitely a disk check on sda over the weekend. Thanks a lot.

reiserfsck /dev/sdb1

 

Note the trailing 1.

  • Author

The reiserfsck on the SSD cache drive didn't reported any error but a chkdsk on the flash drive did. I decided to format the flash drive as well as the cache SSD.

 

Server seems to run stable since then. Cross fingers. Thanks a lot.

 

 

Sent from my iPad using Tapatalk

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.