Swixxy Posted September 21, 2011 Share Posted September 21, 2011 Today i woke up and my unraid servers webui is not responding, neither are any of the shares I can telnet into the machine, but thats about as far as it gets. I forced a reset on my box before i could grab the syslog (Stupid i know!) however i was viewing it at the time through telnet in vi so managed to just ctrl-c the screen at the time and managed to get the important bit Sep 21 20:47:01 jbox logger: ### subsonic_delete_thumbs_ram.sh ### Sep 21 21:26:54 jbox kernel: sas: command 0xf5f219c0, task 0xf74efcc0, timed out Sep 21 21:26:54 jbox kernel: sas: command 0xf5df8d80, task 0xefb3b900, timed out Sep 21 21:26:54 jbox kernel: sas: trying to find task 0xf74efcc0 Sep 21 21:26:54 jbox kernel: sas: sas_scsi_find_task: aborting task 0xf74efcc0 Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 1818:<7>mv_abort_task() Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 1747:mvs_query_task:rc= Sep 21 21:26:54 jbox kernel: sas: I_T nexus reset for dev 010U: I_T recoverd to Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy1 Unplug Notice Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:54 jbox kernel: sas: sas_form_port: phy1 belongs to port1 already(1 Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_rese Sep 21 21:26:57 jbox kernel: sas: sas_ata_task_done: SAS error 8d Sep 21 21:26:57 jbox kernel: sas: trying to find task 0xefb3b900 Sep 21 21:26:57 jbox kernel: sas: sas_scsi_find_task: aborting task 0xefb3b900 Sep 21 21:26:57 jbox kernel: sas: sas_scsi_find_task: task 0xefb3b900 is done Sep 21 21:26:57 jbox kernel: sas: sas_eh_handle_sas_errors: task 0xefb3b900 is d Sep 21 21:26:57 jbox kernel: ata5: sas eh calling libata port error handler [78dSep 21 21:26:57 jbox kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 Sep 21 21:26:57 jbox kernel: ata5.00: res 01/04:ff:00:00:00/00:00:00:00:00/40 Em Sep 21 21:26:57 jbox kernel: ata5.00: error: { ABRT } Sep 21 21:26:57 jbox kernel: ata5: hard resetting link Sep 21 21:26:57 jbox kernel: sas: sas_ata_hard_reset: Found ATA device. Sep 21 21:26:57 jbox kernel: ata5.00: configured for UDMA/133 Sep 21 21:26:57 jbox kernel: ata5: EH complete Sep 21 21:26:57 jbox kernel: ata6: sas eh calling libata port error handler Sep 21 21:26:57 jbox kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 acti Sep 21 21:26:57 jbox kernel: ata6.00: res 01/04:ff:00:00:00/00:00:00:00:00/40 Em Sep 21 21:26:57 jbox kernel: ata6.00: error: { ABRT } Sep 21 21:26:57 jbox kernel: ata6: hard resetting link Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy1 Unplug Notice Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2278:plugin interrupt b Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2139:phy1 Attached Devi Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy1 Unplug Notice Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:59 jbox kernel: sas: sas_form_port: phy1 belongs to port1 already(1 Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_rese Sep 21 21:26:59 jbox kernel: ata6.00: configured for UDMA/133TA device. Sep 21 21:26:59 jbox kernel: ata6: EH complete Sep 21 21:26:59 jbox kernel: ata7: sas eh calling libata port error handler Sep 21 21:26:59 jbox kernel: ata8: sas eh calling libata port error handler Sep 21 21:26:59 jbox kernel: sas: --- Exit sas_scsi_recover_host Sep 21 21:42:49 jbox kernel: sas: command 0xf5f21c00, task 0xf74efcc0, timed out Sep 21 21:42:49 jbox kernel: sas: command 0xf02e6b40, task 0xf75cd900, timed out Sep 21 22:40:58 jbox in.telnetd[4959]: connect from ** (** Sep 21 22:41:12 jbox login[496[31d[35d LOGIN on '/dev/pts/1' from '** Sep 21 22:47:01 jbox logge[36d## subso[40ddelete_thumbs_ram.sh ###ot Sep 21 23:47:02 jbox logger: ### subsonic_delete_thumbs_ram.sh ### [78dSep 22 00:17:08 jbox in.telnetd[5044]: connect from **(** Sep 22 00:17:12 jbox login[5045]: ROOT LOGIN on '/dev/pts/2' from '** Sep 22 00:23:17 jbox in.telnetd[5065]: connect from 194.129.65.79 (** Sep 22 00:23:23 jbox login[5066]: ROOT LOGIN on '/dev/pts/2' from ** Sep 22 00:26:47 jbox e[46dp: unRAID System[50dagement Utility version 5.0-beta12 Sep 22 00:26:47 jb[51dmhttp: Pro key detected,[55dD: 0951-1643-330F-FB70E605229C Sep 22 00:39:28 jbox in.telnetd[5109]: connect from** (** Sep 22 0[65d[A[57dox login[5110]: invalid password for 'root' on '/dev/pts/3' f Sep 22 00:39:43 jbox in.telnetd[5111]: connect fro[** (** Sep 22 00:39:47 jbox login[5112]: invalid password for[67d[b' on '/dev/pts/3' f [76d[72d0:39:52 jbox login[5112]: ROOT LOGIN on '/dev/pts/3[78dom note: telnet was still responsive, however nothing else was (webui etc etc), at the bottom of the log you see me attempt to restart emhttp - which didnt work. Is this a problem with my Supermicro AOC-SASLP-MV8, 8-Port SAS/SATA 300MB/s PCI-e Controller Card I currently have two of these in the system, i had a problem with this card where my drives were unable to spin back up again, but i've disabled drives spinning down Link to comment
Swixxy Posted September 21, 2011 Author Share Posted September 21, 2011 Sorry, just read the post regarding controllers and realised iv'e missed a step when setting up these cards 8 Port Cards Supermicro AOC-SASLP-MV8 Requirements: PCIe x4 or faster slot (PCIe x16 works fine on most motherboards) Cables: -To connect the card directly to a hard drive or SATA drive cage, you need Forward Breakout Cables (4 ports per cable), such as these. -To connect the card directly to a miniSAS backplane such as those used in the Norco 4220 and 4224 cases, you need miniSAS cables (4 ports per cable) such as these. -When searching for these cables, search for the phrase '8087' and you'll find plenty of them. Beware that the Reverse Breakout Cables are only used in Norco cases, they DO NOT work with these SASLP cards. Where to get them: Superbiiz (generally cheaper), Newegg Special Instructions: First off, always disable the INT13 function on these cards. During boot, hold ctrl-m at the appropriate time (the screen that lists all the drive's serial numbers), then go to the second BIOS menu and disable INT13. If you have more than one of these cards, you need to do this for each card (they share the same BIOS menu, so just select the second controller and disable INT13 for that one as well). Newer versions of this card come with a BIOS version ending in .21; this version introduces some RAID functionality to the card that can interfere with the motherboard's ability to boot from unRAID. If you are having trouble booting into unRAID with one or more of the SASLP cards installed, I recommend that you downgrade the card's firmware to the BIOS version ending in .15. Here's how (thanks to joshpond for this tutorial): http://thepcspy.com/read/bootable_usb_flash_drive/ 1) Download the HP USB Flash Drive format tool 2) Extract 3) Run the exe file to install HP tool 4) Insert USB (will delete data) 5) Open HP USB tool 6) Format, select USB drive, FAT (quick is fine) Create DOS start-up disk, select files 7) Select/browse to the extracted folder and there is a DOS files folder Download the .15 firmware from here. 9) Extract firmware .15 to usb USB is now ready to boot off (select HDD on motherboard) Boot off USB, at prompt type: smc-n.bat Set mobo to AHCI and it all works fine. Would this INT13 bios setting be the problem? Link to comment
prostuff1 Posted September 22, 2011 Share Posted September 22, 2011 Sorry, just read the post regarding controllers and realised iv'e missed a step when setting up these cards 8 Port Cards Supermicro AOC-SASLP-MV8 Requirements: PCIe x4 or faster slot (PCIe x16 works fine on most motherboards) Cables: -To connect the card directly to a hard drive or SATA drive cage, you need Forward Breakout Cables (4 ports per cable), such as these. -To connect the card directly to a miniSAS backplane such as those used in the Norco 4220 and 4224 cases, you need miniSAS cables (4 ports per cable) such as these. -When searching for these cables, search for the phrase '8087' and you'll find plenty of them. Beware that the Reverse Breakout Cables are only used in Norco cases, they DO NOT work with these SASLP cards. Where to get them: Superbiiz (generally cheaper), Newegg Special Instructions: First off, always disable the INT13 function on these cards. During boot, hold ctrl-m at the appropriate time (the screen that lists all the drive's serial numbers), then go to the second BIOS menu and disable INT13. If you have more than one of these cards, you need to do this for each card (they share the same BIOS menu, so just select the second controller and disable INT13 for that one as well). Newer versions of this card come with a BIOS version ending in .21; this version introduces some RAID functionality to the card that can interfere with the motherboard's ability to boot from unRAID. If you are having trouble booting into unRAID with one or more of the SASLP cards installed, I recommend that you downgrade the card's firmware to the BIOS version ending in .15. Here's how (thanks to joshpond for this tutorial): http://thepcspy.com/read/bootable_usb_flash_drive/ 1) Download the HP USB Flash Drive format tool 2) Extract 3) Run the exe file to install HP tool 4) Insert USB (will delete data) 5) Open HP USB tool 6) Format, select USB drive, FAT (quick is fine) Create DOS start-up disk, select files 7) Select/browse to the extracted folder and there is a DOS files folder Download the .15 firmware from here. 9) Extract firmware .15 to usb USB is now ready to boot off (select HDD on motherboard) Boot off USB, at prompt type: smc-n.bat Set mobo to AHCI and it all works fine. Would this INT13 bios setting be the problem? Yes, possibly. Link to comment
Swixxy Posted September 23, 2011 Author Share Posted September 23, 2011 I've got the INT13 off and now i can spin down my drives, however this SAS error is still occuring. I've connected to my unraid box from work, however i can't reboot the server (was going to use the file manager to copy/paste it into a txt document) is there any way i can download a file to my local machine via telnet? This problem has made unraid unuseable for me, as it 'crashes' and all shares etc becoem unresponsive within a day! Makes the spouse very unhappy! haha Link to comment
prostuff1 Posted September 23, 2011 Share Posted September 23, 2011 I've got the INT13 off and now i can spin down my drives, however this SAS error is still occuring. I've connected to my unraid box from work, however i can't reboot the server (was going to use the file manager to copy/paste it into a txt document) is there any way i can download a file to my local machine via telnet? This problem has made unraid unuseable for me, as it 'crashes' and all shares etc becoem unresponsive within a day! Makes the spouse very unhappy! haha I am going to assume you are running the latest beta. If you are there are issues with the newest linux kernel, the SASLP driver and everything working correctly. Revert to 4.7 and you should be fine. Link to comment
Swixxy Posted September 23, 2011 Author Share Posted September 23, 2011 I have a 3TB drive hooked up for my parity, is there any other option? e.g patching the drivers? or any tips for what to look for to possibly try and fix the problem myself? or is it literally just a, can't do anything until a fix is supplied Link to comment
prostuff1 Posted September 23, 2011 Share Posted September 23, 2011 or is it literally just a, can't do anything until a fix is supplied Yes Link to comment
Swixxy Posted September 23, 2011 Author Share Posted September 23, 2011 If i were to disconnect the drives from the Supermicro AOC-SASLP-MV8 and connect them to the mobo sata connectors woudl this temporarily fix the issue? I only have 6 drives in total so i have enough ports without the card for the time being Link to comment
prostuff1 Posted September 23, 2011 Share Posted September 23, 2011 If i were to disconnect the drives from the Supermicro AOC-SASLP-MV8 and connect them to the mobo sata connectors woudl this temporarily fix the issue? I only have 6 drives in total so i have enough ports without the card for the time being It might, but if you only have 6 drives then I suggest taking the card out entirely, until you need it. Link to comment
Swixxy Posted September 23, 2011 Author Share Posted September 23, 2011 If i were to disconnect the drives from the Supermicro AOC-SASLP-MV8 and connect them to the mobo sata connectors woudl this temporarily fix the issue? I only have 6 drives in total so i have enough ports without the card for the time being It might, but if you only have 6 drives then I suggest taking the card out entirely, until you need it. It was just in as a breakout cable for a 4 in 3 cage seemed a lot neater than 4 sata cables going across the mobo Thanks, and final question: If i got sata cables and plugged them straight into sata ports would it still recognize the drives in the correct positions (parity etc?) or will i have to unassign all drives prior to disconnect and then reassign them Link to comment
Johnm Posted September 23, 2011 Share Posted September 23, 2011 Thanks, and final question: If i got sata cables and plugged them straight into sata ports would it still recognize the drives in the correct positions (parity etc?) or will i have to unassign all drives prior to disconnect and then reassign them As long as your mobo sata connectors are in achi mode. It should be as simple as re wiring the server and turning it on in 5Bxx. You might have to manually start the array on first boot. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.