similar to: OT: Areca ARC-1220 compatible with SATA III (6Gb/s) drives?

Has anyone experienced any problems with Areca raid cards specifically the 1220 causing kernels to lock up? We are running 2.6.18-92.1.22.el5xen on 64bit. We have "areca_cli rsf info" run once an hour from cron to check for raid raid issues. Having this running seems to cause the box to lock up. Whats weird is I can't seem to make it lock up while running that command by

Has anyone experienced any problems with Areca raid cards specifically the 1220 causing kernels to lock up? We are running 2.6.18-92.1.22.el5xen on 64bit. We have "areca_cli rsf info" run once an hour from cron to check for raid raid issues. Having this running seems to cause the box to lock up. Whats weird is I can't seem to make it lock up while running that command by

I must be doing something horribly wrong and I hope somebody can help. The Areca arc-1224 is not supported by the Areca driver included driver in 7.1 so I have to supply that when starting the install. Documentation provided by Areca and in the Red Hat install guide say the same thing, put the driver on an accessible medium then append inst.dd on the boot command, choose the driver and now the

On 07/05/15, Gordon Messmer wrote: anaconda will try to delete an rpm file if it gets an IOError. Your media may be corrupt. Check that first. ----- Above quoted ----- No such luck. On the system where I'm doing the install, I used dd to read the entire DVD and also copied every .rpm to /dev/null and didn't get any I/O errors. What next?

On 07/06/15 18:06, C Linus Hicks wrote: > On 07/06/15, g wrote: >> you might try verifying that system you are getting error message on >> has a good cd/dvd drive. >> >> burn another dvd at at least 4 speeds slower. >> > if runs ok, bad drive. >> > if still fails, bad drive. >> > another way you can check is to pull iso on system you are

> The disks I am going to use are 6TB Seagate Enterprise ST6000NM0034 > 7200rpm SAS/12Gbit 128 MB Sorry to hear that, my experience is the Seagate brand has the shortest MTBF of any disk I have ever used... > If hardware RAID is preferred, the controller's cache could be updated > to 4GB and I wonder how much performance gain this would give me? Lots, especially with slower

> This is why before configuring and installing everything you may want to > attach drives one at a time, and upon boot take a note which physical > drive number the controller has for that drive, and definitely label it so > y9ou will know which drive to pull when drive failure is reported. Sorry Valeri, that only works if you're the only guy in the org. In reality, you cannot

On 2017-01-20, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > > Hm, not certain what process you describe. Most of my controllers are > 3ware and LSI, I just pull failed drive (and I know phailed physical drive > number), put good in its place and rebuild stars right away. I know for sure that LSI's storcli utility supports an identify operation, which (if the

On Sat, January 21, 2017 12:16 am, Keith Keller wrote: > On 2017-01-20, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: >> >> Hm, not certain what process you describe. Most of my controllers are >> 3ware and LSI, I just pull failed drive (and I know phailed physical >> drive >> number), put good in its place and rebuild stars right away. > > I

On 07/05/15, Gordon Messmer wrote: That's not the same as checking the media for corruption. You may be able to read all of the files, but if the data is corrupt, rpm may throw and IOError. So, the next thing to do is check your media. The DVD should offer to do that first when you boot from it. ------ Above quoted -------- Booted the DVD again, took the default. It got to 76.2% then

On 07/05/2015 09:17 AM, linush at verizon.net wrote: > Someone please tell me what I did to screw this thing up so badly. On 07/05/15, Gordon Messmer<gordon.messmer at gmail.com> wrote: Have you looked at the log files in /mnt/sysimage/root/? ------------- Quoting broken in this mailer ------------ So I looked in /mnt/sysimage/var/log/anaconda and found this in anaconda.packaging.log:

On 07/06/15, g wrote: you might try verifying that system you are getting error message on has a good cd/dvd drive. burn another dvd at at least 4 speeds slower. if runs ok, bad drive. if still fails, bad drive. another way you can check is to pull iso on system you are having problem with and burn dvd. if you get error, get a new drive. -------- Above quoted -------- When I md5sum the DVD

Just as I create a ZFS pool and copy the root partition to it.... the performance seems to be really good then suddenly the system hangs all my sesssions and displays on the console: Oct 10 00:23:28 sunrise arcmsr: WARNING: arcmsr0: dma map got ''no resources'' Oct 10 00:23:28 sunrise arcmsr: WARNING: arcmsr0: dma allocate fail Oct 10 00:23:28 sunrise arcmsr: WARNING: arcmsr0:

Hi, To follow up my CentOS 4.0/Areca SATA RAID driver disk I created a month or two ago, I have now created kernel-module-arcmsr RPMs containing just the kernel module to track the kernel updates. This means: a) No need to patch, rebuild and maintain customised kernels for Areca support b) Keep everything maintained with RPM I've taken the latest 1.20.00.07 kernel driver source as found in

Hello, I have a RAID-6 Partition with the Areca ARC-1231 card on a S5000PAL Intel system with 6 disks as part of the raid volume. The system has been set up as Write-back cache and the raid card has a 2 GIG memory cache on it. It is installed on Freebsd 7.0 STABLE with SCHED_ULE enabled. I have a folder with a lot of small and big files in it that total 3009 files. In the user system we

Hi Valeri, Before you pull a drive you should check to make sure that doing so won't kill the whole array. MegaCli can help you prevent a storage disaster and can let you have more insight into your RAID and the status of the virtual disks and the disks than make up each array. MegaCli will let you see the health and status of each drive. Does it have media errors, is it in predictive

Hi, To satisfy my own requirements, I''ve created a driver disk for the Areca SATA RAID controllers[0]. It currently contains the 1.20.00.06 driver built for the x86_64 SMP and non-SMP kernels, but should be fairly straightforward to add the driver built for 32-bit x86 kernels as well. You can find the driver disk and instructions here: http://www.bodgit-n-scarper.com/code.html#centos

On Fri, January 20, 2017 12:59 pm, Joseph L. Casale wrote: >> The disks I am going to use are 6TB Seagate Enterprise ST6000NM0034 >> 7200rpm SAS/12Gbit 128 MB > > Sorry to hear that, my experience is the Seagate brand has the shortest > MTBF > of any disk I have ever used... > >> If hardware RAID is preferred, the controller's cache could be updated >> to

Updated to latest firmware 1.43-70417 ... same problem.. WARNING: arcmsr0: dma map got ''no resources'' WARNING: arcmsr0: dma allocate fail WARNING: arcmsr0: dma allocate fail free scsi hba pkt WARNING: arcmsr0: dma map got ''no resources'' WARNING: arcmsr0: dma allocate fail WARNING: a The only positive thing is that everytime I try to copy my UFS

Hi, Does anyone have experiences about ARC-1883I SAS controller with CentOS7? I am planning to have RAID1 setup and I am wondering if I should use the controller's RAID functionality which has 2GB cache or should I go with JBOD + Linux software RAID? The disks I am going to use are 6TB Seagate Enterprise ST6000NM0034 7200rpm SAS/12Gbit 128 MB If hardware RAID is preferred, the