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.

Server Crash every night... Please help.

Featured Replies

I have unraid 5.0b14 running for a few years now. Recently I have had major issues with unmenu interfering with simpleFeatures (ended up removing both last night). I also deleted all the packages in the /boot/packages folder and the contents of the /boot/unmenu folder. Since then, each night, my server crashes. I didn't touch any of the core files of the unraid OS. I'm a bit of a newbie so I'm left scratching my head. I have however, narrowed the problem down to the mover (this is exactly when the system crashes). Posted below is the syslog.

 

Was there something in unMENU that was needed for the mover to function? If so, how do I recover it? Any help would save my life. I'm so frustrated and worried that I may lost a ton of precious data over this.

 

./movies/To the Arctic 3D (2012)/To the Arctic 3D (2012).nfo
*** glibc detected *** rsync: free(): invalid next size (normal): 0x080d2438 ***
======= Backtrace: =========
/lib/libc.so.6(+0x705aa)[0xb76405aa]
/lib/libc.so.6(+0x73503)[0xb7643503]
/lib/libc.so.6(cfree+0x70)[0xb76466b0]
rsync[0x807cd74]
rsync[0x807de60]
rsync[0x804f3aa]
rsync[0x8050b5f]
rsync[0x8051e56]
rsync[0x8065825]
rsync[0x80666ac]
/lib/libc.so.6(__libc_start_main+0xe6)[0xb75e6b86]
rsync[0x804aad1]
= Memory map: =
08048000-0809d000 r-xp 00000000 00:01 1083       /usr/bin/rsync
0809d000-080a1000 rwxp 00054000 00:01 1083       /usr/bin/rsync
080a1000-080f2000 rwxp 00000000 00:00 0          [heap]
b7400000-b7421000 rwxp 00000000 00:00 0
b7421000-b7500000 ---p 00000000 00:00 0
b7503000-b751f000 r-xp 00000000 00:01 1548       /usr/lib/libgcc_s.so.1
b751f000-b7520000 rwxp 0001b000 00:01 1548       /usr/lib/libgcc_s.so.1
b7528000-b758a000 rwxp 00000000 00:00 0
b758a000-b75c9000 r-xp 00000000 00:01 1609       /usr/lib/locale/en_US.utf8/LC_CTYPE
b75c9000-b75cb000 rwxp 00000000 00:00 0
b75cb000-b75cf000 r-xp 00000000 00:01 555        /lib/libattr.so.1.1.0
b75cf000-b75d0000 rwxp 00003000 00:01 555        /lib/libattr.so.1.1.0
b75d0000-b772c000 r-xp 00000000 00:01 831        /lib/libc-2.11.1.so
b772c000-b772d000 ---p 0015c000 00:01 831        /lib/libc-2.11.1.so
b772d000-b772f000 r-xp 0015c000 00:01 831        /lib/libc-2.11.1.so
b772f000-b7730000 rwxp 0015e000 00:01 831        /lib/libc-2.11.1.so
b7730000-b7733000 rwxp 00000000 00:00 0
b7733000-b7739000 r-xp 00000000 00:01 781        /lib/libpopt.so.0.0.0
b7739000-b773a000 rwxp 00006000 00:01 781        /lib/libpopt.so.0.0.0
b773a000-b7740000 r-xp 00000000 00:01 834        /lib/libacl.so.1.1.0
b7740000-b7741000 rwxp 00005000 00:01 834        /lib/libacl.so.1.1.0
b7749000-b774a000 rwxp 00000000 00:00 0
b774a000-b774b000 r-xp 00000000 00:00 0          [vdso]
b774b000-b7768000 r-xp 00000000 00:01 563        /lib/ld-2.11.1.so
b7768000-b7769000 r-xp 0001d000 00:01 563        /lib/ld-2.11.1.so
b7769000-b776a000 rwxp 0001e000 00:01 563        /lib/ld-2.11.1.so
bf8a9000-bf8ca000 rw-p 00000000 00:00 0          [stack]
find: `rsync' terminated by signal 6
rsync: writefd_unbuffered failed to write 79 bytes to socket [Receiver]: Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(1530) [Receiver=3.0.7]

Was there something in unMENU that was needed for the mover to function? If so, how do I recover it? Any help would save my life. I'm so frustrated and worried that I may lost a ton of precious data over this.

I don't know of anything in unMENU that is used by the mover.

 

After you removed SimpleFeatures and /boot/unmenu, did you reboot?  (That IS necessary to actually un-unstall whatever you had previously installed)

 

The rsync error might be an indication that you are running out of memory.  (or memory corruption)  Another less likely possibility is memory that is causing errors.  I would perform a memory test to rule that out.

 

The error you are seeing is not one that indicates any kind of data loss.  Nor does it indicate a system crash.. (although "rsync" is obviously crashing.)

 

To remove everything SimpleFeatures installs you need to rename /boot/extra (or delete its contents) and remove the contents of /boot/plugins and /boot/config/plugins and then reboot.

Joe L.

  • Author

Thanks, Joe.

 

I tried several things -- pretty drastic. Nothing seemed to work.

 

1) I removed all the /boot/config and /boot/packages folders and rebooted. Still get the rsync error when I invoke the mover.

 

2) I tried running Memtest86+ 4.1 during bootup, but it just hangs. So I figured, maybe it's bad RAM. I replaced it with sticks that I know work -- and still the same issue.

 

3). I formatted the USB thumb drive off of which unraid runs, and installed version 5.0rc12 (I had 5.0b14) on it. Now everything boots very smoothly, but as soon as I enable the array and ask the mover to run, I get the same rsync error.

 

I can't imagine anything more drastic than that, short of assuming this is a problem with my motherboard. Funny thing is, once I upgraded to unraid OS v5.0rc12 and started memtest, it ran beautifully and registered that my memory was error free.

 

Any other ideas? I am really out of ideas right now.

Does memtest run overnight correctly with the new RAM?

 

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.