SuperW2

Moved to Ebay, need these gone Feel Free to Lock or Delete Thread if Necessary

Moved to Ebay... Need to have these gone! Feel Free to Lock or Delete Thread if Necessary

Posting these up here for a week, and then taking over to eBay...

Posting these up here for a week, and then taking over to eBay...

Ended up using my SuperMicro Card and was unable to use this as well in my server... I'm "maxed" out on my case with 20 drives (4 x 5in3 cages), so selling this card. Original BIOS as far as I know, will include both Reverse Breakout Cables and the goofy USB daugther card that came with it when I ordered it. DOES NOT come with mounting bracket. 100% fully functional - Looking for $50 Shipped (UPS Ground) to Lower 48 US, PayPal Only (500+ Ebay 100% Positive Ratings)

This was an RMA from IcyDock (they replaced the Board), fully tested, 100% functional as new, new Fan and brand new/never used cages (although the screws are MIA). This was last October (still have the RMA Email from IcyDock). Sat in my Closet and cleaning up. Looking for $90 Shipped (UPS Ground) to Lower 48 US, PayPal Only (500+ Ebay 100% Positive Ratings)

Another Lockup/Freeze/Unresponsive GUI/Shares directly after a BLK_EH_NOT_HANDLED again today. I had turned off spin down a few days ago, and it was better, but locked up again today. I think I'm going back to RC3 to see if problem persists. Jun 28 11:25:47 media kernel: sas: command 0xd7104d80, task 0xf2f37180, timed out: BLK_EH_NOT_HANDLED Jun 28 11:25:47 media kernel: sas: Enter sas_scsi_recover_host Jun 28 11:25:47 media kernel: sas: trying to find task 0xf2f37180 Jun 28 11:25:47 media kernel: sas: sas_scsi_find_task: aborting task 0xf2f37180 Jun 28 11:25:47 media kernel: sas: sas_scsi_find_task: querying task 0xf2f37180 Jun 28 11:25:47 media kernel: drivers/scsi/mvsas/mv_sas.c 1747:mvs_query_task:rc= 5 Jun 28 11:25:47 media kernel: sas: sas_scsi_find_task: task 0xf2f37180 failed to abort Jun 28 11:25:47 media kernel: sas: task 0xf2f37180 is not at LU: I_T recover Jun 28 11:25:47 media kernel: sas: I_T nexus reset for dev 0200000000000000 Jun 28 11:25:47 media kernel: sas: sas_form_port: phy2 belongs to port2 already(1)! Jun 28 11:25:50 media kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[2]:rc= 0 Jun 28 11:25:50 media kernel: sas: I_T 0200000000000000 recovered Jun 28 11:25:50 media kernel: sas: sas_ata_task_done: SAS error 8d Jun 28 11:25:50 media kernel: ata13: sas eh calling libata port error handler Jun 28 11:25:50 media kernel: ata14: sas eh calling libata port error handler Jun 28 11:25:50 media kernel: ata15: sas eh calling libata port error handler Jun 28 11:25:50 media kernel: ata15.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 t0 Jun 28 11:25:50 media kernel: ata15.00: failed command: CHECK POWER MODE Jun 28 11:25:50 media kernel: ata15.00: cmd e5/00:00:00:00:00/00:00:00:00:00/40 tag 0 Jun 28 11:25:50 media kernel: res 01/04:ff:00:00:00/00:00:00:00:00/40 Emask 0x3 (HSM violation) Jun 28 11:25:50 media kernel: ata15.00: status: { ERR } Jun 28 11:25:50 media kernel: ata15.00: error: { ABRT } Jun 28 11:25:50 media kernel: ata15: hard resetting link Jun 28 11:25:50 media kernel: sas: sas_form_port: phy2 belongs to port2 already(1)! Jun 28 11:25:52 media kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[2]:rc= 0 Jun 28 11:25:52 media kernel: sas: sas_ata_hard_reset: Found ATA device. Jun 28 11:25:52 media kernel: ata15.00: configured for UDMA/133 Jun 28 11:25:52 media kernel: ata15: EH complete Jun 28 11:25:52 media kernel: ata16: sas eh calling libata port error handler Jun 28 11:25:52 media kernel: ata17: sas eh calling libata port error handler Jun 28 11:25:52 media kernel: ata18: sas eh calling libata port error handler Jun 28 11:25:52 media kernel: ata19: sas eh calling libata port error handler Jun 28 11:25:52 media kernel: ata20: sas eh calling libata port error handler Jun 28 11:25:52 media kernel: sas: --- Exit sas_scsi_recover_host Jun 28 11:26:52 media kernel: sas: sas_ata_task_done: SAS error 2

If RC5 has the new MVAS driver in it, it made it WORSE! I had zero issues on RC3 for weeks. Upgraded to 5 and had 2 of these hard lock/freezes in 3 days.

Any update on this? Spindown disabled since the 24th and no repeat of lockup issue.

I think i'm seeing the same or similar thing... I've had to hard power twice in the last 3 days, the shares become un-accessible, cannot access the GUI. I can Telnet, so I know the Network is good, but cannot Shutdown/Poweroff, etc. Full Syslog attached, but this was the last few lines before I had to restart. Jun 24 22:29:51 media kernel: sas: command 0xed68ccc0, task 0xf2c4a000, timed out: BLK_EH_NOT_HANDLED Jun 24 22:29:51 media kernel: sas: Enter sas_scsi_recover_host Jun 24 22:29:51 media kernel: sas: trying to find task 0xf2c4a000 Jun 24 22:29:51 media kernel: sas: sas_scsi_find_task: aborting task 0xf2c4a000 Jun 24 22:29:51 media kernel: sas: sas_scsi_find_task: querying task 0xf2c4a000 Jun 24 22:29:51 media kernel: drivers/scsi/mvsas/mv_sas.c 1747:mvs_query_task:rc= 5 Jun 24 22:29:51 media kernel: sas: sas_scsi_find_task: task 0xf2c4a000 failed to abort Jun 24 22:29:51 media kernel: sas: task 0xf2c4a000 is not at LU: I_T recover Jun 24 22:29:51 media kernel: sas: I_T nexus reset for dev 0200000000000000 Jun 24 22:29:51 media kernel: sas: sas_form_port: phy2 belongs to port2 already(1)! Jun 24 22:29:53 media kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[2]:rc= 0 Jun 24 22:29:53 media kernel: sas: I_T 0200000000000000 recovered Jun 24 22:29:53 media kernel: sas: sas_ata_task_done: SAS error 8d Jun 24 22:29:53 media kernel: ata13: sas eh calling libata port error handler Jun 24 22:29:53 media kernel: ata14: sas eh calling libata port error handler Jun 24 22:29:53 media kernel: ata15: sas eh calling libata port error handler Jun 24 22:29:53 media kernel: ata15.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 t0 Jun 24 22:29:53 media kernel: ata15.00: failed command: CHECK POWER MODE Jun 24 22:29:53 media kernel: ata15.00: cmd e5/00:00:00:00:00/00:00:00:00:00/40 tag 0 Jun 24 22:29:53 media kernel: res 01/04:ff:00:00:00/00:00:00:00:00/40 Emask 0x3 (HSM violation) Jun 24 22:29:53 media kernel: ata15.00: status: { ERR } Jun 24 22:29:53 media kernel: ata15.00: error: { ABRT } Jun 24 22:29:53 media kernel: ata15: hard resetting link Jun 24 22:29:53 media kernel: sas: sas_form_port: phy2 belongs to port2 already(1)! Jun 24 22:29:56 media kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[2]:rc= 0 Jun 24 22:29:56 media kernel: sas: sas_ata_hard_reset: Found ATA device. Jun 24 22:29:56 media kernel: ata15.00: configured for UDMA/133 Jun 24 22:29:56 media kernel: ata15: EH complete Jun 24 22:29:56 media kernel: ata16: sas eh calling libata port error handler Jun 24 22:29:56 media kernel: ata17: sas eh calling libata port error handler Jun 24 22:29:56 media kernel: ata18: sas eh calling libata port error handler Jun 24 22:29:56 media kernel: ata19: sas eh calling libata port error handler Jun 24 22:29:56 media kernel: ata20: sas eh calling libata port error handler Jun 24 22:29:56 media kernel: sas: --- Exit sas_scsi_recover_host Jun 24 22:30:56 media kernel: sas: sas_ata_task_done: SAS error 2 syslog.txt

One more update before we leave for the family and turkey day dinner... I formatted my USB Stick (first time since Feb 2008 when I bought my Pro License), Put Beta13 back on and rebooted. It's doing a Parity Sync now after reassigning the drives, but I was able to write files to the user share, no windows user/password message, etc. So we will see if it was something wonky with years of up/down grades on the same USB stick or if there is something else going on. Not yet marking this thread solved, but maybe working towards it

Ok, I'll continue talking to myself... After rebooting absolutely everything (and replacing the Switch, even though I don't expect there was any correlation) I can again "read" the shares again (both User, Disk, Flash, etc). (although I still get the Windows login prompt, which once I cancel the folders appeared) This issue is that I can not write any file or folder to either a disk share or a user share... I get the following message when trying to create a "temp" folder anywhere on my array. If I try to play a video file that stored anywhere on the array, it may start, play a few frames and then freezed/locks up. This is the same on 3 different Windows PC's.

Here is one of my user shares...they are all setup about the same for some different names and disk configs.

Syslog attached, I was able to telnet via IP or Server Name successfully I also ran the Utils->New Permissions thing last night before going to bed...no change, still unable to access any of the shares via any Windows box, but i'm able to browse through them via the little explorer icons on the Unraid webconsole. Help please! syslog.txt

OK, I know they are Beta's and I understand everything that goes with that, so we will just move past that first off... I was using B13, I think having some of the LSI issues described in the Beta13 thread (weird errors in syslog, connection issues, stuttering video, etc). I went to go back to B11 (I never really had any luck getting 12 or 12a to boot, would never get past the 12th-13th row of dots when loading). I first tried to just overwrite the BZROOT and BZIMAGE back to the b11... after a reboot, it acted like the array was going up and down (I could connect to user/disk shares one minute and the next Windows would tell me it couldn't connect.) So next (after backing up my Flash USB Stick) I overwrote the entire USB Stick with the contents of the B11 Zip file (overwrote the GO file, etc). The Server Booted, I was able to go intp the Webconsole and change the name of my server from tower to media, enable SMB, it saw all my disks, it see's my shares, the Array is started. The issue is that I can't access any of the user or Disk Shares, or ever the \\media\flash (by IP or DNS name) I get a Windows Security "Enter Network Passsword" Dialog no matter what share I try to connect too (including flash). I'm really pulling my hair out with this thing, trying to go back to what I thought was a "stable" beta (as much as any can be) and now I'm having the SMB share issues. Any help? Thanks Wade

In this case I'm copying new files directly into that "FolderB" location, not new folders (although there are other folders under FolderB location). I changed the Split Level to 4 and retryed the last copy and it seems to be going. Funny that I've never touched the share settings since creating it a couple years ago and have never had a problem, but I guess it has to do with the one drive filling up. hrm. Wade

OK, I changed the Min Free Space to 20971520 which I believe to be the correct KB to GB equivalent for 20GB, and there is no change. This time I'm coping 6 files, all 750-950MB for a total of 5.79GB and I'm getting the same message. ? Wade

Been happening multiple times copying to a specific user share (//backup), but have not seen on other user shares. I get the following Windows Error Message. Share settings are as below I've also tried Split Level 2 and 3 with no change... the folder I'm attempting to copy in to is... \\Backup\FolderA\FolderB Also tried MostFree/Fill-Up and High Water for Allocation Method. I do have 1 Drive (of my 18 data drives) that is pretty much full and 2 at 98% but otherwise, lots of space available.

One last reply and I'll stop spamming... Downgraded to Beta 11 Parity Re-build - Good Parity Check - Good Add re-precleared drives - Good Copy 250GB of Backed up stuff from Removed Drives - Good! Beta 12 did not like my SAS Card per a couple posts above... I'll stay on b11 until it's confirmed that issue is done!

Yes, I see I have that same SAS Card and similar issues... the joys of running Beta Software... BUT, I did remove 1 more of my "new" 1.5TB Drives, which was disk 18 (one that had a few SMART Errors that I didn't copy down). I redid INITCONFIG, removed that drive and let it rebuild Parity over night, AND IT FINISHED... as of right now I have a fully protected Array for the first time in a week (granted it's almost 4 TB smaller than it was previously). So I guess I'll do a through test on these 3 drives, preclear them all if good and try to add 1 at a time and see what happens. Correction, the Parity Rebuild Finished... the subsequent Parity Check Hung after less than an hour and again, no WebGUI, but I can Ping/Telnet fine!

Yes, I see I have that same SAS Card and similar issues... the joys of running Beta Software... BUT, I did remove 1 more of my "new" 1.5TB Drives, which was disk 18 (one that had a few SMART Errors that I didn't copy down). I redid INITCONFIG, removed that drive and let it rebuild Parity over night, AND IT FINISHED... as of right now I have a fully protected Array for the first time in a week (granted it's almost 4 TB smaller than it was previously). So I guess I'll do a through test on these 3 drives, preclear them all if good and try to add 1 at a time and see what happens.

I never was able to get 12A to boot....never got past the rows and rows of Periods on the initial boot...

Well... after attemping a Parity Build for a number of hours today, it appears I'm in the exact same position I was when I started this thread... During Parity Build I lose the ability to connect to the GUI... I can still Ping, I can Telnet, but No GUI... All Lights on all my drives are Green (no Red Activity Blinking) and I'm pretty sure the Parity wasn't scheduled to be done for 2+ more hours... So I still have a server with what I expect is unprotected Parity... one that I will have to Hard Reboot and no idea how to Fix... The Last Activity from Syslog (attached as Zip), was over an hour ago... If this were a horse, I think I'd "put it down" by now... Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[5]:rc= 0 Oct 6 18:26:25 Media kernel: sas: I_T 0600000000000000 recovered Oct 6 18:26:25 Media kernel: sas: sas_ata_task_done: SAS error 8d Oct 6 18:26:25 Media last message repeated 4 times Oct 6 18:26:25 Media kernel: ata13: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata14: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata15: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata16: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata17: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata18: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata18: log page 10h reported inactive tag 26 Oct 6 18:26:25 Media kernel: ata18.00: exception Emask 0x1 SAct 0x1f SErr 0x0 action 0x6 t0 Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/00:00:48:7b:04/02:00:71:00:00/40 tag 0 ncq 262144 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/88:00:c0:79:04/01:00:71:00:00/40 tag 1 ncq 200704 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/00:00:48:7d:04/02:00:71:00:00/40 tag 2 ncq 262144 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x80000 Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x80000 Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/78:00:48:7f:04/01:00:71:00:00/40 tag 3 ncq 192512 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/00:00:c0:80:04/02:00:71:00:00/40 tag 4 ncq 262144 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18: hard resetting link Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x89800. Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x1001 Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy6 Unplug Notice Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x11081 Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[6] Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2278:plugin interrupt but phy6 is gone Oct 6 18:26:26 Media kernel: mvsas 0000:01:00.0: Phy6 : No sig fis Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2139:phy6 Attached Device Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x89800. Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x1001 Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy6 Unplug Notice Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x81 Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x10000 Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[6] Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 1338:port 6 attach dev info is 0 Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 1340:port 6 attach sas addr is 6 Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 379:phy 6 byte dmaded. Oct 6 18:26:27 Media kernel: sas: sas_form_port: phy6 belongs to port5 already(1)! Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[5]:rc= 0 Oct 6 18:26:27 Media kernel: sas: sas_ata_hard_reset: Found ATA device. Oct 6 18:26:27 Media kernel: ata18.00: configured for UDMA/133 Oct 6 18:26:27 Media kernel: ata18: EH complete Oct 6 18:26:27 Media kernel: ata19: sas eh calling libata port error handler Oct 6 18:26:27 Media kernel: sas: --- Exit sas_scsi_recover_host Oct 6 18:26:58 Media kernel: sas: command 0xede30cc0, task 0xedcff180, timed out: BLK_EH_NOT_HANDLED Oct 6 18:26:58 Media kernel: sas: command 0xede30540, task 0xedcff680, timed out: BLK_EH_NOT_HANDLED Oct 6 18:26:58 Media kernel: sas: command 0xede30900, task 0xedcfe8c0, timed out: BLK_EH_NOT_HANDLED Oct 6 18:26:58 Media kernel: sas: command 0xeff1cb40, task 0xedcfe000, timed out: BLK_EH_NOT_HANDLED Oct 6 18:26:58 Media kernel: sas: command 0xede303c0, task 0xedcff900, timed out: BLK_EH_NOT_HANDLED Oct 6 19:45:50 Media in.telnetd[11024]: connect from 192.168.1.120 (192.168.1.120) Oct 6 19:45:54 Media login[11025]: ROOT LOGIN on '/dev/pts/0' from 'Win7Main' syslog.zip

Yes, I think those were actually tied to my Cache Disk, which I just removed/disabled/unplugged, last reboot shows none of these errors in my Syslog! I ran the other two things and nothing seemed out of line... I have removed the drives and am now rebuilding parity after initconfig. I'll preclear those two drives and re-add them as new... hopefully that won't be too difficult. Thanks for ALL your help and patience with me!

I'd be fine reformatting both 9 and 17 actually... I'd be OK removing them both from the Array Completly (later wiping and re-adding as blank new drives) -?If I knew how!