September 29, 200916 yr I recently got a LimeTech MD-1510/LI (version 4.4.2 of unRAID) and migrated some data over from a Thecus 5200 NAS unit plus some other drives I had available (mostly 1TB WD Green drives). Got everything migrated over about 5 days, mostly using wget between the two devices, so I moved the Thecus' 1.5TB Seagate drives to the unRAID. Everything seemed fine, built the parity drive on one of the 1.5TB drives, but for some reason (and I don't know if this is related), one of the drive LEDs was red on the unit but green in the web interface. Anyways, I was going to run the preclear script on that drive to see what issues it had. About a day later, when I tried to browse the array from an XP machine to move anything off the disk with the red light (it was probably empty but I wanted to make sure), I couldn't connect to the network share. I tried pulling up the web interface, no dice, and also connecting via telnet, also no luck. I could ping the unRAID IP address fine, so it's not a network problem, and the ethernet port light is lit up (orange for GE). Naively, I hit the reset button, which caused the parity to be rebuilt on restart. I waited almost an entire day for that to complete, and now I'm back to my original situation with one of the 1.5TB drives showing a red LED on the unit, everything else is green, and I can't login to the web interface nor via telnet. I did power off the unit (which I understand cleanly shuts down the unit) and turn it back on, but I'm in the same situation. Do I need to open the unit, remove the USB key and try to mount it on a Windows machine to check the syslog? I did purchase the backup key option, so I have a spare as well.
September 29, 200916 yr Can you telnet into the machine? Can you login on the console as root? Login as root either way, see if /boot is mounted with the command df or df /boot See http://lime-technology.com/wiki/index.php/Troubleshooting about troubleshooting and capturing a syslog.
September 29, 200916 yr Author Hi WeeboTech, No, can't telnet in (which I had previously done several times before this issue), and I can't get the web interface to pull up either or browse the network share via CIFS/SMB. I can successfully ping the unit's IP address: C:\Documents and Settings\Administrator>ping 192.168.0.101 Pinging 192.168.0.101 with 32 bytes of data: Reply from 192.168.0.101: bytes=32 time=1ms TTL=64 Reply from 192.168.0.101: bytes=32 time<1ms TTL=64 Reply from 192.168.0.101: bytes=32 time<1ms TTL=64 Reply from 192.168.0.101: bytes=32 time<1ms TTL=64 Unfortunately I don't have a monitor laying around (I guess I could move it and hook it up to my plasma TV's VGA port, but I don't have a keyboard either). Does anyone know if there is a way to access the console either from the network or serial connection with this unit? I'm mostly used to Sun and HP servers, which have integrated lights out management either via a dedicated ethernet port or (if older) a serial console. I only see a single ethernet port and no serial port, so I'm guessing I'm out of luck on that one.
September 29, 200916 yr Author I just tried browsing through My Network Places, and when pulling up the network name I saw the "flash" directory, but no "diskX" directories are showing up.
September 30, 200916 yr It is possible that that drive is spewing errors to the syslog, and the syslog is getting so big, using up too much low memory, that other processes are getting shut down. If you shut down as correctly as possible, a fresh boot should give you a fresh syslog and access to the Web Management page and Telnet, at least for awhile! Try capturing your syslog then to your flash drive, and post it here. The fact that the flash drive was visible but not the data drives means that Samba was still working, but the array was not running, perhaps because of a bad drive.
September 30, 200916 yr Author Thanks for the suggestion RobJ. Would it be a good idea to remove the drive that presumably is problematic (the one that has the red LED on the unit) and then try to boot?
September 30, 200916 yr Unfortunately I don't have a monitor laying around (I guess I could move it and hook it up to my plasma TV's VGA port, but I don't have a keyboard either). Does anyone know if there is a way to access the console either from the network or serial connection with this unit? I'm mostly used to Sun and HP servers, which have integrated lights out management either via a dedicated ethernet port or (if older) a serial console. I only see a single ethernet port and no serial port, so I'm guessing I'm out of luck on that one. I was pretty stumped, but then had a thought. If you can access the flash directory, you can modify the config/go script to save a copy of the syslog upon bootup from a workstation. If that does not work, You could shutdown unRAID, take the flash out, put it on your desktop. Modify the config/go script to save a copy of the syslog upon booting. Then boot... shutdown, and re-examine the flash drive for the syslog file.
October 3, 200916 yr Author Weebo, I must be dense, because I haven't been able to search the forum and find the line to add to the go script to copy the syslog to the flash drive. Care to share it?
October 3, 200916 yr here you go http://lime-technology.com/wiki/index.php?title=Troubleshooting#Capturing_your_syslog
October 3, 200916 yr Weebo, I must be dense, because I haven't been able to search the forum and find the line to add to the go script to copy the syslog to the flash drive. Care to share it? I'd add two lines... sleep 10 cp var/log/syslog /boot/syslog.txt I added a "sleep 10" to allow time for the emhttp process to start the array. Joe L.
October 4, 200916 yr Author Okay, this is the syslog.txt output (I removed the timestamps to get under the character limit)...any ideas? NAS logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 NAS logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo NAS ifplugd(eth0)[1368]: ifplugd 0.28 initializing. NAS kernel: r8169: eth0: link up NAS kernel: r8169: eth0: link up NAS ifplugd(eth0)[1368]: Using interface eth0/00:30:48:B0:87:D5 with driver <r8169> (version: 2.3LK-NAPI) NAS ifplugd(eth0)[1368]: Using detection mode: SIOCETHTOOL NAS ifplugd(eth0)[1368]: Initialization complete, link beat detected. NAS ifplugd(eth0)[1368]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. NAS logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 hw ether 00:30:48:B0:87:D5 NAS logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.0.101 broadcast 192.168.0.255 netmask 255.255.255.0 NAS logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.0.1 metric 1 NAS ifplugd(eth0)[1368]: Program executed successfully. NAS rpc.statd[1414]: Version 1.1.4 Starting NAS ntpd[1433]: ntpd [email protected] Mon May 7 05:15:03 UTC 2007 (1) NAS ntpd[1434]: precision = 1.000 usec NAS ntpd[1434]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 NAS ntpd[1434]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled NAS ntpd[1434]: Listening on interface #1 lo, 127.0.0.1#123 Enabled NAS ntpd[1434]: Listening on interface #2 eth0, 192.168.0.101#123 Enabled NAS ntpd[1434]: kernel time sync status 0040 NAS emhttp: unRAID System Management Utility version 4.4.2 NAS emhttp: Copyright (C) 2005-2008, Lime Technology, LLC NAS emhttp: Pro key detected, registered to: NAS emhttp: Device inventory: NAS emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 (sdj) ata-ST31500341AS_9VS10AZJ NAS emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 (sdk) ata-ST31500341AS_9VS10B69 NAS emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 (sdl) ata-ST31500341AS_9VS0ZBDP NAS emhttp: pci-0000:00:1f.2-scsi-1:0:1:0 (sdm) ata-ST31500341AS_9VS10BJV NAS emhttp: pci-0000:00:1f.5-scsi-0:0:0:0 (sdn) ata-ST31500341AS_9VS0N7Y1 NAS emhttp: pci-0000:00:1f.5-scsi-1:0:0:0 (sdo) ata-WDC_WD10EACS-00D6B0_WD-WCAU40611402 NAS emhttp: pci-0000:01:00.0-scsi-0:0:0:0 (sda) ata-WDC_WD3200JD-60KLB0_WD-WMAMR1586399 NAS emhttp: pci-0000:01:00.0-scsi-1:0:0:0 (sdb) ata-WDC_WD3200JD-60KLB0_WD-WMAMR1649364 NAS emhttp: pci-0000:01:00.0-scsi-2:0:0:0 (sdc) ata-WDC_WD5000YS-01MPB0_WD-WCANU1174952 NAS emhttp: pci-0000:01:00.0-scsi-3:0:0:0 (sdd) ata-ST3750640AS_3QD11EFD NAS emhttp: pci-0000:02:00.0-scsi-0:0:0:0 (sdf) ata-WDC_WD10EACS-00D6B0_WD-WCAU40237231 NAS emhttp: pci-0000:02:00.0-scsi-1:0:0:0 (sdg) ata-WDC_WD10EACS-00D6B0_WD-WCAU40215409 NAS emhttp: pci-0000:02:00.0-scsi-2:0:0:0 (sdh) ata-WDC_WD10EACS-00D6B0_WD-WCAU40215267 NAS emhttp: pci-0000:02:00.0-scsi-3:0:0:0 (sdi) ata-WDC_WD10EACS-00ZJB0_WD-WCASJ0457943 NAS emhttp: restart_md_driver: stat pci-0000:03:00.0-scsi-1:0:0:0: No such file or directory NAS emhttp: shcmd (1): rmmod md-mod >>/var/log/go 2>&1 NAS emhttp: shcmd: shcmd (1): exit status: 1 NAS emhttp: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=8,144,8,176,8,160,8,192,8,208,8,224,8,128,8,112,8,96,8,80,8,48,8,32,8,16,8,0,0,0,0,0 >>/var/log/go 2>&1 NAS kernel: md: unRAID driver 0.95.0 installed NAS kernel: md: xor using function: pIII_sse (10653.600 MB/sec) NAS kernel: md: import disk0: [8,144] (sdj) ST31500341AS 9VS10AZJ offset: 63 size: 1465138552 NAS kernel: md: import disk1: [8,176] (sdl) ST31500341AS 9VS0ZBDP offset: 63 size: 1465138552 NAS kernel: md: import disk2: [8,160] (sdk) ST31500341AS 9VS10B69 offset: 63 size: 1465138552 NAS kernel: md: import disk3: [8,192] (sdm) ST31500341AS 9VS10BJV offset: 63 size: 1465138552 NAS kernel: md: import disk4: [8,208] (sdn) ST31500341AS 9VS0N7Y1 offset: 63 size: 1465138552 NAS kernel: md: import disk5: [8,224] (sdo) WDC WD10EACS-00D6B0 WD-WCAU40611402 offset: 63 size: 976762552 NAS kernel: md: import disk6: [8,128] (sdi) WDC WD10EACS-00ZJB0 WD-WCASJ0457943 offset: 63 size: 976762552 NAS kernel: md: import disk7: [8,112] (sdh) WDC WD10EACS-00D6B0 WD-WCAU40215267 offset: 63 size: 976762552 NAS kernel: md: import disk8: [8,96] (sdg) WDC WD10EACS-00D6B0 WD-WCAU40215409 offset: 63 size: 976762552 NAS kernel: md: import disk9: [8,80] (sdf) WDC WD10EACS-00D6B0 WD-WCAU40237231 offset: 63 size: 976762552 NAS kernel: md: import disk10: [8,48] (sdd) ST3750640AS 3QD11EFD offset: 63 size: 732574552 NAS kernel: md: import disk11: [8,32] (sdc) WDC WD5000YS-01MPB0 WD-WCANU1174952 offset: 63 size: 488386552 NAS kernel: md: import disk12: [8,16] (sdb) WDC WD3200JD-60KLB0 WD-WMAMR1649364 offset: 63 size: 312571192 NAS kernel: md: import disk13: [8,0] (sda) WDC WD3200JD-60KLB0 WD-WMAMR1586399 offset: 63 size: 312571192 NAS emhttp: shcmd (3): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root NAS emhttp: shcmd (4): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root NAS emhttp: shcmd (5): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root NAS emhttp: shcmd (6): crontab /var/spool/cron/crontabs/root NAS kernel: md: import disk0: [8,144] (sdj) ST31500341AS 9VS10AZJ offset: 63 size: 1465138552 NAS kernel: md: import disk1: [8,176] (sdl) ST31500341AS 9VS0ZBDP offset: 63 size: 1465138552 NAS kernel: md: import disk2: [8,160] (sdk) ST31500341AS 9VS10B69 offset: 63 size: 1465138552 NAS kernel: md: import disk3: [8,192] (sdm) ST31500341AS 9VS10BJV offset: 63 size: 1465138552 NAS kernel: md: import disk4: [8,208] (sdn) ST31500341AS 9VS0N7Y1 offset: 63 size: 1465138552 NAS kernel: md: import disk5: [8,224] (sdo) WDC WD10EACS-00D6B0 WD-WCAU40611402 offset: 63 size: 976762552 NAS kernel: md: import disk6: [8,128] (sdi) WDC WD10EACS-00ZJB0 WD-WCASJ0457943 offset: 63 size: 976762552 NAS kernel: md: import disk7: [8,112] (sdh) WDC WD10EACS-00D6B0 WD-WCAU40215267 offset: 63 size: 976762552 NAS kernel: md: import disk8: [8,96] (sdg) WDC WD10EACS-00D6B0 WD-WCAU40215409 offset: 63 size: 976762552 NAS kernel: md: import disk9: [8,80] (sdf) WDC WD10EACS-00D6B0 WD-WCAU40237231 offset: 63 size: 976762552 NAS kernel: md: import disk10: [8,48] (sdd) ST3750640AS 3QD11EFD offset: 63 size: 732574552 NAS kernel: md: import disk11: [8,32] (sdc) WDC WD5000YS-01MPB0 WD-WCANU1174952 offset: 63 size: 488386552 NAS kernel: md: import disk12: [8,16] (sdb) WDC WD3200JD-60KLB0 WD-WMAMR1649364 offset: 63 size: 312571192 NAS kernel: md: import disk13: [8,0] (sda) WDC WD3200JD-60KLB0 WD-WMAMR1586399 offset: 63 size: 312571192 NAS emhttp: shcmd (7): /etc/rc.d/rc.samba stop >/dev/null NAS emhttp: shcmd (: /etc/rc.d/rc.nfsd stop >/dev/null NAS emhttp: shcmd (9): cp /etc/exports- /etc/exports NAS emhttp: shcmd (10): /etc/rc.d/rc.samba start >/dev/null NAS emhttp: shcmd (11): /etc/rc.d/rc.nfsd start >/dev/null NAS kernel: mdcmd (3): start NAS kernel: md: import disk0: [8,144] (sdj) ST31500341AS 9VS10AZJ offset: 63 size: 1465138552 NAS kernel: md: import disk1: [8,176] (sdl) ST31500341AS 9VS0ZBDP offset: 63 size: 1465138552 NAS kernel: md: import disk2: [8,160] (sdk) ST31500341AS 9VS10B69 offset: 63 size: 1465138552 NAS kernel: md: import disk3: [8,192] (sdm) ST31500341AS 9VS10BJV offset: 63 size: 1465138552 NAS kernel: md: import disk4: [8,208] (sdn) ST31500341AS 9VS0N7Y1 offset: 63 size: 1465138552 NAS kernel: md: import disk5: [8,224] (sdo) WDC WD10EACS-00D6B0 WD-WCAU40611402 offset: 63 size: 976762552 NAS kernel: md: import disk6: [8,128] (sdi) WDC WD10EACS-00ZJB0 WD-WCASJ0457943 offset: 63 size: 976762552 NAS kernel: md: import disk7: [8,112] (sdh) WDC WD10EACS-00D6B0 WD-WCAU40215267 offset: 63 size: 976762552 NAS kernel: md: import disk8: [8,96] (sdg) WDC WD10EACS-00D6B0 WD-WCAU40215409 offset: 63 size: 976762552 NAS kernel: md: import disk9: [8,80] (sdf) WDC WD10EACS-00D6B0 WD-WCAU40237231 offset: 63 size: 976762552 NAS kernel: md: import disk10: [8,48] (sdd) ST3750640AS 3QD11EFD offset: 63 size: 732574552 NAS kernel: md: import disk11: [8,32] (sdc) WDC WD5000YS-01MPB0 WD-WCANU1174952 offset: 63 size: 488386552 NAS kernel: md: import disk12: [8,16] (sdb) WDC WD3200JD-60KLB0 WD-WMAMR1649364 offset: 63 size: 312571192 NAS kernel: md: import disk13: [8,0] (sda) WDC WD3200JD-60KLB0 WD-WMAMR1586399 offset: 63 size: 312571192 NAS kernel: unraid: allocated 29624kB NAS kernel: md1: running, size: 1465138552 blocks NAS kernel: md2: running, size: 1465138552 blocks NAS kernel: md3: running, size: 1465138552 blocks NAS kernel: md4: running, size: 1465138552 blocks NAS kernel: md5: running, size: 976762552 blocks NAS kernel: md6: running, size: 976762552 blocks NAS kernel: md7: running, size: 976762552 blocks NAS kernel: md8: running, size: 976762552 blocks NAS kernel: md9: running, size: 976762552 blocks NAS kernel: md10: running, size: 732574552 blocks NAS kernel: md11: running, size: 488386552 blocks NAS kernel: md12: running, size: 312571192 blocks NAS kernel: md13: running, size: 312571192 blocks NAS kernel: mdcmd (5): check NAS kernel: md: recovery thread woken up ... NAS kernel: md: recovery thread checking parity... NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk1 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk2 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 >/dev/null 2>&1 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 >/dev/null 2>&1 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk3 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk4 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3 >/dev/null 2>&1 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 >/dev/null 2>&1 NAS kernel: md: using 1152k window, over a total of 1465138552 blocks. NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk5 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk6 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk7 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk8 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md6 /mnt/disk6 >/dev/null 2>&1 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md7 /mnt/disk7 >/dev/null 2>&1 NAS kernel: ReiserFS: md1: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md1: using ordered data mode NAS kernel: ReiserFS: md3: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md3: using ordered data mode NAS kernel: ReiserFS: md2: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md2: using ordered data mode NAS kernel: ReiserFS: md4: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md4: using ordered data mode NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk9 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md5 /mnt/disk5 >/dev/null 2>&1 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md8 /mnt/disk8 >/dev/null 2>&1 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md9 /mnt/disk9 >/dev/null 2>&1 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk10 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md10 /mnt/disk10 >/dev/null 2>&1 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk11 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md11 /mnt/disk11 >/dev/null 2>&1 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk12 NAS emhttp: shcmd (12): mkdir -m 700 /mnt/disk13 NAS kernel: ReiserFS: md8: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md8: using ordered data mode NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md12 /mnt/disk12 >/dev/null 2>&1 NAS emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md13 /mnt/disk13 >/dev/null 2>&1 NAS kernel: ReiserFS: md12: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md12: using ordered data mode NAS kernel: ReiserFS: md6: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md6: using ordered data mode NAS kernel: ReiserFS: md9: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md9: using ordered data mode NAS kernel: ReiserFS: md13: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md13: using ordered data mode NAS kernel: ReiserFS: md5: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md5: using ordered data mode NAS kernel: ReiserFS: md4: journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md4: checking transaction log (md4) NAS kernel: ReiserFS: md7: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md7: using ordered data mode NAS kernel: ReiserFS: md10: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md10: using ordered data mode NAS kernel: ReiserFS: md9: journal params: device md9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md9: checking transaction log (md9) NAS kernel: ReiserFS: md11: found reiserfs format "3.6" with standard journal NAS kernel: ReiserFS: md11: using ordered data mode NAS kernel: ReiserFS: md12: journal params: device md12, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md12: checking transaction log (md12) NAS kernel: ReiserFS: md13: journal params: device md13, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md13: checking transaction log (md13) NAS kernel: ReiserFS: md8: journal params: device md8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md8: checking transaction log (md8) NAS kernel: ReiserFS: md6: journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md6: checking transaction log (md6) NAS kernel: ReiserFS: md11: journal params: device md11, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md11: checking transaction log (md11) NAS kernel: ReiserFS: md1: journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md1: checking transaction log (md1) NAS kernel: ReiserFS: md5: journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md5: checking transaction log (md5) NAS kernel: ReiserFS: md7: journal params: device md7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md7: checking transaction log (md7) NAS kernel: ReiserFS: md10: journal params: device md10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md10: checking transaction log (md10) NAS kernel: ReiserFS: md3: journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md3: checking transaction log (md3) NAS kernel: ReiserFS: md2: journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 NAS kernel: ReiserFS: md2: checking transaction log (md2) NAS kernel: ReiserFS: md4: Using r5 hash to sort names NAS kernel: ReiserFS: md1: Using r5 hash to sort names NAS kernel: ReiserFS: md10: Using r5 hash to sort names NAS kernel: ReiserFS: md7: Using r5 hash to sort names NAS kernel: ReiserFS: md6: Using r5 hash to sort names NAS kernel: ReiserFS: md2: Using r5 hash to sort names NAS kernel: ReiserFS: md3: Using r5 hash to sort names NAS kernel: ReiserFS: md8: Using r5 hash to sort names NAS kernel: ReiserFS: md12: Using r5 hash to sort names NAS kernel: ReiserFS: md11: Using r5 hash to sort names NAS kernel: ReiserFS: md9: Using r5 hash to sort names NAS kernel: ReiserFS: md13: Using r5 hash to sort names NAS kernel: ReiserFS: md5: Using r5 hash to sort names NAS kernel: can't shrink filesystem on-line NAS last message repeated 12 times NAS emhttp: shcmd (12): cp /etc/exports- /etc/exports NAS emhttp: shcmd (13): mkdir -m 700 /mnt/user NAS emhttp: shcmd (14): /usr/local/sbin/shfs /mnt/user NAS emhttp: get_config_idx: fopen /boot/config/shares/lost+found.cfg: No such file or directory - assigning defaults NAS emhttp: shcmd (15): killall -HUP smbd NAS emhttp: shcmd (16): /etc/rc.d/rc.nfsd restart >/dev/null
October 4, 200916 yr That small piece of the syslog does not show any problems at all, other than an indication that you have had issues in the past. A 'lost+found' folder exists on one or more of your data drives, so you once had Reiser file system problems. You fixed them, because now it does not find anything wrong when it mounts them. The only other piece of info that I can gather from this scrap is that a parity check has begun, which of course will dramatically slow everything else down. We always prefer the entire syslog, attached to the post, zipped if necessary. Because they are text files, and a lot of very repetitive material at that, they compress very tightly. Perhaps in the full syslog, something will show up. Would it be a good idea to remove the drive that presumably is problematic (the one that has the red LED on the unit) and then try to boot? That may be your next step, but we cannot advise until we have a better idea what is wrong, and we need the full syslog. Even if we have identified the drive that appears to be the source of errors, it often is not the drive's fault, but as one example, could be the *cable* to the drive.
October 5, 200916 yr Author Rob, Thanks for the reply. I put the entire syslog file here: http://66.39.67.208/syslog.txt The parity was rebuilt on the last power cycle, as I removed the suspect drive to see if that made a difference (it didn't), so I put the drive back in and it rebuilt the parity. The "lost+found" directory is due to me; I did do an attempt to recover some files I thought I had deleted using some instructions I found on this forum. I initially used wget to transfer the files from my old Thecus NAS to the unRAID since you can't do recursive transfer using command line FTP, but realized that wget was ignoring files containing certain characters in the filenames due to URL encoding. So I used another program I have on Windows called GoodSync to try to sync those over, and I thought I had accidentally misconfigured it and it was removing files on one side of sync (turns out it was just saving those to another directory). Anyways, I did try the file recovery on a disk I thought I had deleted files on, but that was several days before this issue manifested itself.
October 5, 200916 yr Syslog looks great. For this boot on October 3rd at 9:20am, all drives were found, identified and setup without any problems, and then mounted without any issues. A parity check has begun, but there are no issues apparent to require it, so it can be aborted, if desired. What ever happened earlier seems to be resolved. You may want to Obtain a SMART report for that suspect drive. Otherwise, all you can do is wait for it to act up again, then capture the associated syslog. One very small item, you apparently still have the SATA150 jumper on the Seagate 750GB drive, see Improving unRAID Performance, Remove SATA150 Jumper section.
October 6, 200916 yr Author I'm starting to think this is something else rather than an issue with the array--as you said, the array appears to be fine (and after the last parity rebuild, the one drive that was showing a red LED on the front panel is now green). But I'm having the same issues. I tried connecting via the web interface and via telnet, no luck. I browsed the network share via Windows Explorer and it showed all the disk, flash, lost+found and user share directories. Once I tried accessing any of those, I get an error about the network path not being found. After that happened, I can't even get back to that listing again--if I try to browse the network share, I get the error again instead of the folder listing. I've rebooted my router and swapped out the ethernet cable to the LimeTech server--same result. I've turned my firewall off. Any other ideas? Looks like I need to grab a keyboard and hook up a monitor to see what I can find out from the console.
October 7, 200916 yr Author I brought a keyboard and monitor home from the office; the system and array appears to be working fine, but I can't get any outbound traffic from the unRAID unit. I can't ping the gateway (get 100% packet loss), though I can ping the unRAID unit from the gateway and other machines on the network. I ran "ifconfig -a" and the interface seems to be configured properly, but obviously something else is going on. Any ideas?
October 7, 200916 yr I brought a keyboard and monitor home from the office; the system and array appears to be working fine, but I can't get any outbound traffic from the unRAID unit. I can't ping the gateway (get 100% packet loss), though I can ping the unRAID unit from the gateway and other machines on the network. I ran "ifconfig -a" and the interface seems to be configured properly, but obviously something else is going on. Any ideas? Bad cable... bad port... bad router.... you did not define a nameserver on the unRAID server? Try typing: cat /etc/resolv.conf You should get something like this... pointing to your gateway, # Generated entries: nameserver 192.168.2.1
October 7, 200916 yr Author Joe, /etc/resolv.conf is fine; it has the gateway's IP: nameserver 192.168.0.1 It's not the port or cable...I swapped all of those out. I turned on the ability to ping in the router config (for some reason, I can ping the gateway from my Windows machines but not unRAID unless this is turned on, I guess there's a difference in the MTU values or something like that). Anyways, I can ping to outside sites just fine from the command line of the unRAID server. I also have some other devices on the network that have an embedded web server, and I can telnet to those on port 80 from the unRAID. I just can't access anything on the unRAID server from my laptop, and I wasn't having this problem before. And this was sort of weird--I tried hitting up the unRAID web interface after playing around with some things, and it very briefly showed the "waiting" screen before I got an error about it being unavailable. And as I said, I can see all the disks and directories under the unRAID network share, I just can't access any of them. I have a music server on my network that runs Linux and Samba, and I can access it fine from this same laptop, so I know CIFS/SMB isn't totally being blocked or having issues on that laptop.
October 10, 200916 yr Author Okay, so I'm still struggling to figure out how to connect to the array over the network and what went wrong. Have tried just about everything I can think of, and I still can't access the server via telnet or the web interface. The network share mount shows up in Windows Explorer, but as soon as I try to connect to any of the disks or user shares, I get an error that it's not accessible. And this was unusual--the only other device I have at home right now with a web browser is a Wii, so I used the included Opera browser to hit the unRAID's web interface. It partially loads the page (and it loads very slowly), showing the parity and disk1 info (when it should be up to disk 13), and is missing the images and the CSS file(s). When I click on any of the links (users, shares, settings, devices, or the parity/disk link), I get a "connection closed by remote server" error. If I hit "refresh" on the homepage, I sometimes get that same error or it hangs on the "Wait" white screen. I have a few other devices on the network that have web interfaces (a print server, a music server, and my original Thecus NAS, which also has SSH/telnet) and I'm not having any issues connecting to those at all, so I have to assume it's an issue with the unRAID unit. I checked top from the command line and it's almost 100% idle with just under 4G of RAM free, so it's not a resource issue. I can ping the other devices on the network without any latency. Is it possible something is corrupted with the OS? I have a backup USB key--should I look at using that?
October 10, 200916 yr Author Nevermind, this seems to be a network issue. I noticed the ping results, while low in the latency number, were always skipping the same number of sequences--it would do 7 successful sequences, then kinda hang, then output a result 33 sequences higher than the previous result. So I plugged my laptop directly into the unRAID unit, and everything worked fine (web interface, network share, telnet). There must be something with my Dlink wireless router--I'm having the same issues whether I'm using a wired or wireless connection. One other question--the front panel LED for this same drive I suspect may have issues is always red, but it's showing green in the web interface. Is that something to be concerned about?
Archived
This topic is now archived and is closed to further replies.