January 19, 201313 yr After a couple of years of no problems (except for a couple of bad drives), I suddenly can't access my UnRAID v4.7 box via both the web management screen and Unmenu. I can, however, still access files and shares via Windows. Via Telnet, I've tried: killall emhttp nohup /usr/local/sbin/emhttp & and cd /boot/unmenu uu But, I get nothing. A portion of my syslog reads: Jan 18 05:02:59 UR1 kernel: mdcmd (494): spindown 8 Jan 18 05:03:00 UR1 kernel: mdcmd (495): spindown 9 Jan 18 05:03:00 UR1 kernel: mdcmd (496): spindown 10 Jan 18 05:03:01 UR1 kernel: mdcmd (497): spindown 11 Jan 18 05:03:01 UR1 kernel: mdcmd (498): spindown 12 Jan 18 06:06:17 UR1 ntpd[1862]: no servers reachable Jan 18 06:23:23 UR1 ntpd[1862]: synchronized to 205.196.146.72, stratum 2 Jan 18 06:58:12 UR1 dhcpcd[1854]: sending DHCP_REQUEST for 192.168.1.5 to 192.168.1.1 Jan 18 06:58:12 UR1 dhcpcd[1854]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 18 06:58:12 UR1 dhcpcd[1854]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 18 06:58:12 UR1 dhcpcd[1854]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 18 06:58:12 UR1 dhcpcd[1854]: DHCP_ACK received from (192.168.1.1) Jan 18 18:17:20 UR1 kernel: mdcmd (499): spindown 5 Jan 18 18:17:20 UR1 kernel: mdcmd (500): spindown 6 Jan 18 18:17:41 UR1 kernel: sas: command 0xc35f5b40, task 0xf6f23b80, timed out: BLK_EH_NOT_HANDLED Jan 18 18:17:41 UR1 kernel: sas: Enter sas_scsi_recover_host Jan 18 18:17:41 UR1 kernel: sas: trying to find task 0xf6f23b80 Jan 18 18:17:41 UR1 kernel: sas: sas_scsi_find_task: aborting task 0xf6f23b80 Jan 18 18:17:41 UR1 kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abort_task:rc= 5 Jan 18 18:17:41 UR1 kernel: sas: sas_scsi_find_task: querying task 0xf6f23b80 Jan 18 18:17:41 UR1 kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_query_task:rc= 5 Jan 18 18:17:41 UR1 kernel: sas: sas_scsi_find_task: task 0xf6f23b80 failed to abort Jan 18 18:17:41 UR1 kernel: sas: task 0xf6f23b80 is not at LU: I_T recover Jan 18 18:17:41 UR1 kernel: sas: I_T nexus reset for dev 0300000000000000 Jan 18 18:17:41 UR1 kernel: sas: I_T 0300000000000000 recovered Jan 18 18:17:41 UR1 kernel: sas: --- Exit sas_scsi_recover_host Jan 18 18:17:50 UR1 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 1 does not match to the expected one 3 Jan 18 18:17:50 UR1 kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 206734. Fsck? Jan 18 18:17:50 UR1 kernel: REISERFS (device md8): Remounting filesystem read-only Jan 18 18:17:55 UR1 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 1 does not match to the expected one 3 Jan 18 18:17:55 UR1 kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 206734. Fsck? Jan 18 18:17:59 UR1 kernel: mdcmd (501): spindown 9 Jan 18 18:18:00 UR1 kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 0 ctrl sts=0x199800. Jan 18 18:18:00 UR1 kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 0 irq sts = 0x80000 Jan 18 18:18:00 UR1 kernel: mdcmd (502): spindown 10 Jan 18 18:18:00 UR1 kernel: mdcmd (503): spindown 11 Jan 18 18:18:01 UR1 kernel: mdcmd (504): spindown 12 Jan 18 18:18:21 UR1 kernel: sas: command 0xd81720c0, task 0xf6f7bb80, timed out: BLK_EH_NOT_HANDLED Jan 18 18:18:21 UR1 kernel: sas: Enter sas_scsi_recover_host Jan 18 18:18:21 UR1 kernel: sas: trying to find task 0xf6f7bb80 Jan 18 18:18:21 UR1 kernel: sas: sas_scsi_find_task: aborting task 0xf6f7bb80 Jan 18 18:18:21 UR1 kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abort_task:rc= 5 Jan 18 18:18:21 UR1 kernel: sas: sas_scsi_find_task: querying task 0xf6f7bb80 Jan 18 18:18:21 UR1 kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_query_task:rc= 5 Jan 18 18:18:21 UR1 kernel: sas: sas_scsi_find_task: task 0xf6f7bb80 failed to abort Jan 18 18:18:21 UR1 kernel: sas: task 0xf6f7bb80 is not at LU: I_T recover Jan 18 18:18:21 UR1 kernel: sas: I_T nexus reset for dev 0000000000000000 Jan 18 18:18:21 UR1 kernel: sas: I_T 0000000000000000 recovered Jan 18 18:18:21 UR1 kernel: sas: --- Exit sas_scsi_recover_host Jan 18 18:25:17 UR1 kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 3 ctrl sts=0x199800. Jan 18 18:25:17 UR1 kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 3 irq sts = 0x80000 Jan 18 18:25:24 UR1 kernel: ata7: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Jan 18 18:25:24 UR1 kernel: ata7: status=0x51 { DriveReady SeekComplete Error } Jan 18 18:25:24 UR1 kernel: ata7: error=0x04 { DriveStatusError } Jan 18 18:25:24 UR1 kernel: ata7: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Jan 18 18:25:24 UR1 kernel: ata7: status=0x51 { DriveReady SeekComplete Error } Jan 18 18:25:24 UR1 kernel: ata7: error=0x04 { DriveStatusError } Jan 18 18:25:24 UR1 kernel: ata7: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Jan 18 18:25:24 UR1 kernel: ata7: status=0x51 { DriveReady SeekComplete Error } Jan 18 18:25:24 UR1 kernel: ata7: error=0x04 { DriveStatusError } Jan 18 18:25:24 UR1 kernel: ata7: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Jan 18 18:25:24 UR1 kernel: ata7: status=0x51 { DriveReady SeekComplete Error } Jan 18 18:25:24 UR1 kernel: ata7: error=0x04 { DriveStatusError } Jan 18 18:25:24 UR1 kernel: ata7: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Jan 18 18:25:24 UR1 kernel: ata7: status=0x51 { DriveReady SeekComplete Error } Jan 18 18:25:24 UR1 kernel: ata7: error=0x04 { DriveStatusError } I attached my syslog (which I had to edit because it contained too many errors that I don't understand). Any assistance will be greatly appreciated. syslog3.txt
January 19, 201313 yr Author Thanks, I'll try that. As I was typing this message, I attempted to access the Web Management Screen and was successful - for a very brief period. I noticed that it has a flashing red-ball on one of my drives. Unfortunately, I can't access it any longer and therefore, can't take the array offline via the WMS. I just poked around trying to find out how to do it via Telnet, however, I'm not sure that I'm looking at the most accurate post of how to do it. Do you have a link to the safest way to use Telnet to shut it down so that I can swap in a new drive? Thanks much.
January 19, 201313 yr Author Thanks. Couple more questions - before I mess something up: -Is it correct to assume that I should use the term "md1", "md2", etc instead of the "sd1", "sd2", etc., designators that UnRAID originally assigned the drives? -How do I know which one of the drives is the parity drive? Or does it matter? Thanks again.
January 19, 201313 yr The parity disk does not have a mounted file system. Follow the guide carefully.
January 19, 201313 yr Author In the end, the bad drive was what seemed to be causing my entire problem. I replaced it, restarted UnRaid, and re-built the new drive successfully. I've had several red-balls before, but never did they cause me to not be able to gain access via the web management screen and Unmenu. Another UnRaid lesson learned by young grasshopper ... The timely assistance is greatly appreciated.
Archived
This topic is now archived and is closed to further replies.