January 8, 201412 yr Author @garycase: There was no box to check to say it's ok to format them. Access thru IP address didn't work. Restart the server and bring online in maintenance mode resulted in a parity check start, after which I again couldn't reach the server.
January 8, 201412 yr Looking through the forum, there are several posts on setting up systems using the AOC-SASLP-MV8. Did you disable the RAID mode on the controller (in the controller's BIOS)? ... and what firmware level is on your AOC-SASLP-MV8 ?
January 8, 201412 yr Have you changed the "tuneable" parameters under disk settings? Too high settings (allocations) may result in your system becoming unresponsive while a parity check is running.
January 8, 201412 yr Author I didn't change anything in unRaid, no tuneable parameters or anything. I didn't disable RAID mode on the controller. When I'm home later this day I will try to access the cards Bios and disable RAID mode (I assume that is what must be turned off garycase?) and read some posts about setting up the AOC-SASLP-MV8. (I can only acces my PC at home from here (my work), but can't push any fysical powerbuttons on the server..)
January 8, 201412 yr Author Ok, So now I tried to enter the cards Bios. I had to enter it by setting the harddrives in my servers Bios to IDE according to some posts on this forum, and then hold ctrl-m during the screen that lists all the drive's serial numbers. I never got in the bios.. What I can see is that I'm using Bios Version 3.1.0.21. Some post say that "IF you are having trouble booting into unRAID with one or more of the SASLP cards installed, you have two options: 1) Modify the firmware using a built-in utility to disable the RAID functionality. or 2) Downgrade the card's firmware to the BIOS version ending in .15. The problem is not that I can't boot into unRaid, because that works fine. Every time I start the array, I can't use the array, and can't use or get in the GUI with explorer. "Waiting on Tower"... it says, and nothing happens further. The only thing that does work, is that I can see and assign all disks, and all balls are green. The only thing left then, is is shut down the power..
January 8, 201412 yr The problem is not that I can't boot into unRaid, because that works fine. Every time I start the array, I can't use the array, and can't use or get in the GUI with explorer. "Waiting on Tower"... it says, and nothing happens further. The only thing that does work, is that I can see and assign all disks, and all balls are green. The only thing left then, is is shut down the power.. That sounds like a plugin not letting the array start but I though you had already ruled that out? Have you booted up with a stock unRAID no plugins standard GUI no simple features no new WebGUI, no DYNAMIX etc...?
January 8, 201412 yr Author @BobPhoenix I don't have any plugins. Everything as standard as possible.
January 8, 201412 yr Author When powering up the server, I got a message that there is something wrong with the AOC-SASLP-MV8. Maybe that is more serious then I thought before: When I started the array, I quickly pressed the LOG button when it was still working with this as a result: Jan 9 00:22:40 Tower emhttp: shcmd (103): crontab -c /etc/cron.d - <<< "# Generated mover schedule: /usr/local/sbin/mover |& logger" Jan 9 00:22:40 Tower emhttp: shcmd (104): /usr/local/sbin/emhttp_event disks_mounted Jan 9 00:22:40 Tower emhttp_event: disks_mounted Jan 9 00:22:40 Tower emhttp: shcmd (105): :>/etc/samba/smb-shares.conf Jan 9 00:22:41 Tower emhttp: Restart SMB... Jan 9 00:22:41 Tower emhttp: shcmd (106): killall -HUP smbd Jan 9 00:22:41 Tower emhttp: shcmd (107): ps axc | grep -q rpc.mountd Jan 9 00:22:41 Tower emhttp: _shcmd: shcmd (107): exit status: 1 Jan 9 00:22:41 Tower emhttp: shcmd (108): /usr/local/sbin/emhttp_event svcs_restarted Jan 9 00:22:41 Tower emhttp_event: svcs_restarted Jan 9 00:23:01 Tower crond[1235]: failed parsing crontab for user root: /usr/local/sbin/mover |& logger Jan 9 00:23:14 Tower kernel: sas: command 0xeff7e240, task 0xeff452c0, timed out: BLK_EH_NOT_HANDLED Jan 9 00:23:14 Tower kernel: sas: Enter sas_scsi_recover_host Jan 9 00:23:14 Tower kernel: sas: trying to find task 0xeff452c0 Jan 9 00:23:14 Tower kernel: sas: sas_scsi_find_task: aborting task 0xeff452c0 Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1818:<7>mv_abort_task() mvi=f74e0000 task=eff452c0 slot=f74f15d8 slot_idx=x0 Jan 9 00:23:14 Tower kernel: sas: sas_scsi_find_task: querying task 0xeff452c0 Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1747:mvs_query_task:rc= 5 Jan 9 00:23:14 Tower kernel: sas: sas_scsi_find_task: task 0xeff452c0 failed to abort Jan 9 00:23:14 Tower kernel: sas: task 0xeff452c0 is not at LU: I_T recover Jan 9 00:23:14 Tower kernel: sas: I_T nexus reset for dev 0500000000000000 Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 5 ctrl sts=0x89800. Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 5 irq sts = 0x1001001 Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy5 Unplug Notice Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 5 ctrl sts=0x199800. Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 5 irq sts = 0x1001081 Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 5 ctrl sts=0x199800. Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 5 irq sts = 0x10000 Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[5] Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1338:port 5 attach dev info is 40400 Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1340:port 5 attach sas addr is 5 Jan 9 00:23:14 Tower kernel: drivers/scsi/mvsas/mv_sas.c 379:phy 5 byte dmaded. Jan 9 00:23:14 Tower kernel: sas: sas_form_port: phy5 belongs to port7 already(1)! Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[7]:rc= 0 Jan 9 00:23:16 Tower kernel: sas: I_T 0500000000000000 recovered Jan 9 00:23:16 Tower kernel: sas: sas_ata_task_done: SAS error 8d Jan 9 00:23:16 Tower kernel: ata7: sas eh calling libata port error handler Jan 9 00:23:16 Tower kernel: ata8: sas eh calling libata port error handler Jan 9 00:23:16 Tower kernel: ata9: sas eh calling libata port error handler Jan 9 00:23:16 Tower kernel: ata10: sas eh calling libata port error handler Jan 9 00:23:16 Tower kernel: ata11: sas eh calling libata port error handler Jan 9 00:23:16 Tower kernel: ata12: sas eh calling libata port error handler Jan 9 00:23:16 Tower kernel: ata13: sas eh calling libata port error handler Jan 9 00:23:16 Tower kernel: ata14: sas eh calling libata port error handler Jan 9 00:23:16 Tower kernel: sas: sas_ata_task_done: SAS error 2 Jan 9 00:23:16 Tower kernel: ata14: failed to read log page 10h (errno=-5) Jan 9 00:23:16 Tower kernel: ata14.00: exception Emask 0x1 SAct 0x1 SErr 0x0 action 0x6 t0 Jan 9 00:23:16 Tower kernel: ata14.00: failed command: READ FPDMA QUEUED Jan 9 00:23:16 Tower kernel: ata14.00: cmd 60/00:00:58:04:04/02:00:00:00:00/40 tag 0 ncq 262144 in Jan 9 00:23:16 Tower kernel: res 01/04:00:58:02:04/00:00:00:00:00/40 Emask 0x3 (HSM violation) Jan 9 00:23:16 Tower kernel: ata14.00: status: { ERR } Jan 9 00:23:16 Tower kernel: ata14.00: error: { ABRT } Jan 9 00:23:16 Tower kernel: ata14: hard resetting link Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 5 ctrl sts=0x89800. Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 5 irq sts = 0x1001001 Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy5 Unplug Notice Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 5 ctrl sts=0x199800. Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 5 irq sts = 0x1001081 Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 5 ctrl sts=0x199800. Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 5 irq sts = 0x10000 Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[5] Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1338:port 5 attach dev info is 40400 Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1340:port 5 attach sas addr is 5 Jan 9 00:23:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 379:phy 5 byte dmaded. Jan 9 00:23:16 Tower kernel: sas: sas_form_port: phy5 belongs to port7 already(1)! Jan 9 00:23:18 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[7]:rc= 0 Jan 9 00:23:18 Tower kernel: sas: sas_ata_hard_reset: Found ATA device. Jan 9 00:23:18 Tower kernel: ata14.00: configured for UDMA/133 Jan 9 00:23:18 Tower kernel: ata14: EH complete Jan 9 00:23:18 Tower kernel: sas: --- Exit sas_scsi_recover_host Jan 9 00:23:48 Tower kernel: sas: command 0xeff7e240, task 0xf7406dc0, timed out: BLK_EH_NOT_HANDLED
January 9, 201412 yr The problem is not that I can't boot into unRaid, because that works fine. Every time I start the array, I can't use the array, and can't use or get in the GUI with explorer. "Waiting on Tower"... it says, and nothing happens further. The only thing that does work, is that I can see and assign all disks, and all balls are green. If I understand what you're saying, your system DOES boot into UnRAID okay, but you can't access the Web GUI after the boot. Is this correct? How do you know it's booted okay if you can't see the GUI? And how do you know the balls are all green if you can't see the display after you've started the array? When it says "Waiting for Tower", what happens if you close Internet Explorer; then open it again and to go //Tower ?? As for your card ... are you seeing any messages about RAID from the SASLP-MV8's BIOS during initialization. If so, you need to disable that ... which is a bit tricky, but fairly well outlined here: http://lime-technology.com/forum/index.php?topic=27129.0
January 9, 201412 yr Author @garycase Excuse my for not explaining the problem properly, my native language is Dutch. What I mean is that I can power up my system, after which unRaid starts. I can see all my disks in the GUI in explorer, and I can push the button to start the array. After that, nothing happens and I can not reach my server thru my Windows PC in any way. When I try to close Internet Explorer and open it again, the same thing happens when I try to acces it with typing //Tower. When I'm home from work, I will try to acces the SASLP-MV8's Bios with help from the post you mentioned, thanx! I uploaded a video with the power-on process on it: Maybe somebody knows when I'm supposed to push the ctrl-m command to enter the cards Bios?
January 9, 201412 yr What's the 'ADAPTER ERROR' that shows up very early in the video...Before UnRAID? At 00:08 on the clip? It prompts you to hit a key to continue, which you do, and then unRAID begins to load. Which Adapter is the message about? (I can't see it well enough on my screen) Prior to that point, on the screen it looks like there aren't enough SATA ports for what you're describing as your setup. Am I seeing this right?
January 9, 201412 yr I would try to flash the firmware on the card. As to when to press CNTL-M: I didn't see a prompt at the bottom like with mine but that is probably suppressed by the error message. You should be able to press CNTL-M any time you see the display for the card. I quite often just continue to press the appropriate button throughout the cards display until the bios screen shows up. Over kill but doesn't appear to harm anything.
January 15, 201412 yr Author Ok, I had a busy week, but was finally able to test a few things: I am able to access the cards bios, but only when connecting less than 12 disks in total. for example: 6 on MoBo and 5 on SASLP-MV8. Or 8 on SASLP-MV8 and 3 on MoBo. I think my old problem is back here to stay now, it all begun with my MoBo that can't seem to handle more than 11 disks. It looks like that hasn't changed with the SASLP-MV8. So now I want to buy a new MoBo that definitely can handle at least 14 disks (6 on MoBo and 8 on the SASLP-MV8), that is enough for this year. The problem is off course that the MoBo's that are for sale now, are not tested or approved or anything..
January 15, 201412 yr Ok, I had a busy week, but was finally able to test a few things: I am able to access the cards bios, but only when connecting less than 12 disks in total. for example: 6 on MoBo and 5 on SASLP-MV8. Or 8 on SASLP-MV8 and 3 on MoBo. I think my old problem is back here to stay now, it all begun with my MoBo that can't seem to handle more than 11 disks. It looks like that hasn't changed with the SASLP-MV8. So now I want to buy a new MoBo that definitely can handle at least 14 disks (6 on MoBo and 8 on the SASLP-MV8), that is enough for this year. The problem is off course that the MoBo's that are for sale now, are not tested or approved or anything.. I don't remember the setting name but there is a setting (an interrupt setting) that if you turn it off you can no longer boot from drives attached to it. Since unRAID boots from USB stick this isn't a problem and usually allows MBs with your problem to boot when you have too many drives.
January 15, 201412 yr Author @BobPhoenix The problem is not that the board won't boot up: It boots up, unRaid is started but shows few disks than attached. (that was with my old Promise PCI cards attached) And with the MV8 it boots up, shows all disks like it should, but when I start the array the server freezes..
January 15, 201412 yr Author I'm thinking of buying a Supermicro MBD-X8SSIL-F, so I can use my old processor and memory
January 16, 201412 yr Author In a last try to get my system going before buying a new MoBo, I managed to disable the raid functionality while keeping the .21 firmware as described here: http://lime-technology.com/forum/index.php?topic=27129.0 What I got in return was a nice line of harddisks in my bios, just like it should but which I had never had before with 14 attached drives! So now I'm kind of convinced that the problem IS fixable after all.. The problem is still the same, after booting up I saw all the disks as you can see in picture "GUI". The three disks that I added (at once) are all visible as unformatted, and disk 12 has a red ball (because I tried to remove it some days ago to see if the system would start up with one disk less. It didn't, but the result was a red ball when installing the disk again). When I start the array, nothing further happens. Except for the screen on my server as you can see in picture "Problem" (next post). Some problem with device md11, i/o failures??? Everything stops after that, there is no further activity. Anyone know how to act now? Maybe is was not so smart to ad three disks at once? In that case I think I have to try to get an array of my original nine datadisks online (but how do I do that?), an then later ad one disk at a time?
January 16, 201412 yr The error showing from your screen shot makes me think you have file system corruption on md11 and you need to run the tools to fix them. However I'm not the person to advise you on this as I've only had to use them once so am not familiar with them. Maybe someone else can take over now I've reached my knowledge limit.
January 17, 201412 yr Author Thanx dgaschk!! I will try and give this a try tonight and post the result.
January 17, 201412 yr Author Ok, I started the array in maintenance mode. I quickly stopped the data rebuild that it started by itself because of the red ball on disk12. After typing reiserfsck --check /dev/md11 on the server, I got the screen you see on the picture. It does that with all disks. ??
Archived
This topic is now archived and is closed to further replies.