January 4, 201016 yr I trying to setup an UnRAID server to replace my Openfiler server. So, first some info. regarding my setup: I am using an old machine (MOBO: Biostar P4M890-M7) with an Rosewill RSV-S8 storage enclosure system that's include a PCIe x1 slot card (Sil3132R5) for the eSATA connections between the enclosure and the my server (I already backup all my data in another RSV-S8 connected into an HTPC running Win7) RSV-S8 as the one mentioned here http://lime-technology.com/forum/index.php?topic=3609.0 | I updated the SiI3132 card BIOS to the latest one without RAID (BASE only - JBOD). I have 10 disks. 3- 750GB's and 7- 1.5TBs, all from Seagate) and a UnRAID pro key license. 8 disks are connected into the RSV-S8 and 2 into MOBO controller - SATA I UnRAID was installed with latest 4.5 stable version + UnMENU 1.2 and a few packages (nano, screen, etc.) - memtest shows no errors after a 12 hours run. UnRAID booted OK and all my 10 disks are showing up inside the web interface. Nice! I am so excited! Now I want to pre-clear all my data disks to be able to start transfer my data into my new UnRAID server (without parity, of course, I will add parity once I transfer all my data back) So I started with pre-clearing the 2 disks connected into MOBO controller, so far so good... But when I started a 3rd pre-clear script for one of the disks connected into the SiI3132 card the system start showing messages on system (+ a speaker beep), the message says: Jan 4 02:15:15 Tower preclear_disk-start[3090]: Jan 4 02:15:15 Tower kernel: do_IRQ: 0.99 No irq handler for vector (irq -1) Jan 4 02:15:16 Tower last message repeated 5 times Jan 4 02:15:19 Tower kernel: __ratelimit: 167 callbacks suppressed Jan 4 02:15:19 Tower kernel: do_IRQ: 0.99 No irq handler for vector (irq -1) Jan 4 02:15:20 Tower last message repeated 9 times Jan 4 02:15:25 Tower kernel: __ratelimit: 269 callbacks suppressed Jan 4 02:15:25 Tower kernel: do_IRQ: 0.99 No irq handler for vector (irq -1) Jan 4 02:15:25 Tower last message repeated 9 times Jan 4 02:15:30 Tower kernel: __ratelimit: 217 callbacks suppressed Jan 4 02:15:30 Tower kernel: do_IRQ: 0.99 No irq handler for vector (irq -1) Jan 4 02:15:31 Tower last message repeated 9 times Jan 4 02:15:35 Tower kernel: __ratelimit: 248 callbacks suppressed Jan 4 02:15:35 Tower kernel: do_IRQ: 0.99 No irq handler for vector (irq -1) Jan 4 02:15:35 Tower last message repeated 9 times The pre-clear scripts are still running for more than 1 hour now (3 instances for 3 different disks, one of them in the SiI3132 card). Every 60 secs. I got the same msg on syslog + a system beep. Jan 4 04:16:31 Tower kernel: __ratelimit: 35 callbacks suppressed Jan 4 04:16:31 Tower kernel: do_IRQ: 0.99 No irq handler for vector (irq -1) Any idea of what could be this msg.? Is this something bad? There are anything I can do to avoid this? full syslog is attached just in case I really want to use UnRAID since the new version is out with the big performance improvement. I also brought this RSV-8 because the PCIe card uses SiI3132 chipset was supposed to be supported by UnRAID Any help will be really appreciated. Regards, chopeta
January 5, 201016 yr Author Well, according to this it's an issue with some VIA chipsets I was able to get rid of that messages including this param. into the boot code: pci=nomsi,noaer Now, my syslinux.cfg file looks like this: root@Tower:/boot# cat syslinux.cfg default menu.c32 menu title Lime Technology LLC prompt 0 timeout 50 label unRAID OS menu default kernel bzimage append initrd=bzroot pci=nomsi,noaer label Memtest86+ kernel memtest root@Tower:/boot# Let's pre-clear all the disks and to start copying data Regards, chopeta
January 13, 201016 yr Always great to see someone solve their own problems! Nice job too. I noted one other item of concern: Jan 4 03:02:39 Tower kernel: ata1.03: ATA-8: ST31500341AS, SD17, max UDMA/133 Jan 4 03:02:39 Tower kernel: ata1.03: 2930277168 sectors, multi 0: LBA48 NCQ (not used) Jan 4 03:02:39 Tower kernel: ata1.03: WARNING: device requires firmware update to be fully functional. Jan 4 03:02:39 Tower kernel: ata1.03: contact the vendor or visit http://ata.wiki.kernel.org. SD17 is known to be one of the unsafe firmware versions for that drive. Seagate has a firmware upgrade for it, directly from them. Users have not had very good success with VIA chipsets here. And lines like the following are not particularly reassuring... Jan 4 03:02:39 Tower kernel: via-rhine: Broken BIOS detected, avoid_D3 enabled.
January 13, 201016 yr Author Thanks RobJ. Really appreciate your time. Regarding the SD17 firmware, this is the info. for that disk: smartctl -a -d ata /dev/sde (disk4) smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS09PDH Firmware Version: SD17 User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Wed Jan 13 02:19:17 2010 GMT+5 SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. I checked that disk serial [9VS09PDH] on Seagate website and it shows up as a good firmware (no need for FW upgrade). So I don't know how to upgrade it anyway (do I need to it?) Regarding the VIA chipset, actually I was not really comfortable with that Biostar mainboard so I swap it with my Proxmox VE server mainboard which is a Foxconn G31MXP-K with 4GBs of RAM. Now I am more comfortable since this mainboard is listed in the HW compat. list and some users have reported good results. I have removed the boot params. that I prev. added. So far so good. I was still pre-clearing my disks (it took a long time)... now I am about to start copying my files (without parity)... I am not sure about how to proceed here, so I will post a new thread with my question. I will also post my results in the Forum (including full syslog) once I finish the copy and the parity creation + check. Thanks again. Regards, chopeta
January 18, 201016 yr Author I will try to upgrade this firmware following this post http://lime-technology.com/forum/index.php?topic=2773.msg22889#msg22889
Archived
This topic is now archived and is closed to further replies.