March 2, 201412 yr Hello, I recently upgraded from v5.0 to 5.0.5 and since then, have been getting pretty regular crashes (three times per week maybe). Today, I had some time to investigate a little and tried telnetting to the server. It looks like maybe my flash is corrupted? Can anybody confirm? MediaServer login: root Password: 8632: /lib/libnss_files.so.2: error: symbol lookup error: undefined symbol: _nss_files_initgroups_dyn (fatal) Linux 3.9.11p-unRAID. 8632: 8632: file=libtermcap.so.2 [0]; needed by -bash [0] 8632: find library=libtermcap.so.2 [0]; searching 8632: search cache=/etc/ld.so.cache 8632: trying file=/lib/libtermcap.so.2 8632: 8632: file=libtermcap.so.2 [0]; generating link map 8632: dynamic: 0x40029198 base: 0x40026000 size: 0x00003388 8632: entry: 0x40026a60 phdr: 0x40026034 phnum: 4 8632: 8632: 8632: file=libdl.so.2 [0]; needed by -bash [0] 8632: find library=libdl.so.2 [0]; searching 8632: search cache=/etc/ld.so.cache 8632: trying file=/lib/libdl.so.2 8632: 8632: file=libdl.so.2 [0]; generating link map 8632: dynamic: 0x4002ced0 base: 0x4002a000 size: 0x00003078 8632: entry: 0x4002aa20 phdr: 0x4002a034 phnum: 8 8632: 8632: 8632: file=libc.so.6 [0]; needed by -bash [0] 8632: find library=libc.so.6 [0]; searching 8632: search cache=/etc/ld.so.cache 8632: trying file=/lib/libc.so.6 8632: 8632: file=libc.so.6 [0]; generating link map 8632: dynamic: 0x4018cd7c base: 0x4002e000 size: 0x00162908 8632: entry: 0x40044ce0 phdr: 0x4002e034 phnum: 10 8632: 8632: checking for version `GLIBC_2.1' in file /lib/libdl.so.2 [0] required by file -bash [0] 8632: checking for version `GLIBC_2.0' in file /lib/libdl.so.2 [0] required by file -bash [0] 8632: checking for version `GLIBC_2.4' in file /lib/libc.so.6 [0] required by file -bash [0] 8632: checking for version `GLIBC_2.3' in file /lib/libc.so.6 [0] required by file -bash [0] 8632: checking for version `GLIBC_2.3.4' in file /lib/libc.so.6 [0] required by file -bash [0] 8632: checking for version `GLIBC_2.1' in file /lib/libc.so.6 [0] required by file -bash [0] 8632: checking for version `GLIBC_2.2' in file /lib/libc.so.6 [0] required by file -bash [0] 8632: checking for version `GLIBC_2.0' in file /lib/libc.so.6 [0] required by file -bash [0] 8632: checking for version `GLIBC_2.1.3' in file /lib/libc.so.6 [0] required by file /lib/libtermcap.so.2 [0] 8632: checking for version `GLIBC_2.1' in file /lib/libc.so.6 [0] required by file /lib/libtermcap.so.2 [0] 8632: checking for version `GLIBC_2.0' in file /lib/libc.so.6 [0] required by file /lib/libtermcap.so.2 [0] 8632: checking for version `GLIBC_PRIVATE' in file /lib/ld-linux.so.2 [0] required by file /lib/libdl.so.2 [0] 8632: checking for version `GLIBC_2.1.3' in file /lib/libc.so.6 [0] required by file /lib/libdl.so.2 [0] 8632: checking for version `GLIBC_2.1' in file /lib/libc.so.6 [0] required by file /lib/libdl.so.2 [0] 8632: checking for version `GLIBC_2.0' in file /lib/libc.so.6 [0] required by file /lib/libdl.so.2 [0] 8632: checking for version `GLIBC_PRIVATE' in file /lib/libc.so.6 [0] required by file /lib/libdl.so.2 [0] 8632: checking for version `GLIBC_PRIVATE' in file /lib/ld-linux.so.2 [0] required by file /lib/libc.so.6 [0] 8632: checking for version `GLIBC_2.3' in file /lib/ld-linux.so.2 [0] required by file /lib/libc.so.6 [0] 8632: checking for version `GLIBC_2.1' in file /lib/ld-linux.so.2 [0] required by file /lib/libc.so.6 [0] 8632: 8632: calling init: /lib/libc.so.6 8632: 8632: 8632: calling init: /lib/libdl.so.2 8632: 8632: 8632: calling init: /lib/libtermcap.so.2 8632: 8632: 8632: initialize program: -bash 8632: 8632: 8632: transferring control: -bash 8632: Connection closed by foreign host.
March 2, 201412 yr From what you posted, it could also be a bad plugin...or a conflict among several plugins. If you think its the flash drive: shut down cleanly. Put the flash in your PC. Run Chkdsk on the flash. (Disk Utility on a Mac) and fix all errors. Then try restarting your unRAID in 'SAFE MODE'. If the problem is gone, try restarting normally. If the problem comes back then, post a syslog. http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog
March 4, 201412 yr Author Thanks Dale, I was unable to shut down cleanly, but pulled the flash out anyway and run disk utility on my mac. It was a very short process and I don't think anything was repaired according to the log. The server started like normal though after this, so maybe something was wrong with it. I did a clean shutdown on it and then restarted and checked parity. Then the problem occurred again, now I could not ping it at all, so I dug into the networking side of things and it appears that my Motherboard ethernet interface died on me. Luckily I had a PCI Ethernet card and installed that today and magically, I was abel to reach the server over the network again. I have a feeling that the Ethernet problems caused some corruption.. Will keep ya'll posted. Joe From what you posted, it could also be a bad plugin...or a conflict among several plugins. If you think its the flash drive: shut down cleanly. Put the flash in your PC. Run Chkdsk on the flash. (Disk Utility on a Mac) and fix all errors. Then try restarting your unRAID in 'SAFE MODE'. If the problem is gone, try restarting normally. If the problem comes back then, post a syslog. http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog
March 4, 201412 yr The flash drive uses a really simple file format. Disk Utility runs very quickly and only has 3 steps in the repair process, and doesn't give a lot of feedback...unlike what you see if you run Disk Utility on your normal Mac drive. Sounds like everything is working out. If problems pop up, post a complete syslog. http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog
March 4, 201412 yr The files that it is complaining about are part of the unRAID install. Could you have gotten a bad download of unRAID? See if your download matches the hash from the download page. There are several ways to get the hash, but I use HashTab. It will give you a tab in the property page when you right-click on a file and select properties. Looks like either a corrupt flash or a bad download. Backup your config folder and try starting over with a format and fresh download, then make_bootable and restore your config folder. P.S. you won't see those files in the zip unless you unpack it further. unRAID unpacks those files from bzroot into RAM when it starts.
March 4, 201412 yr Hello, I recently upgraded from v5.0 to 5.0.5 and since then, have been getting pretty regular crashes Run memtest from the startup menu for an extended period, 24 hours or so.
Archived
This topic is now archived and is closed to further replies.