similar to: 7.1 install with Areca arc-1224

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

I have an NEC DVD-RW ND2500A (that's not the label I bought it under, but that's what it really is.) It's supposed to read/write CDs, DVDs, DVD+Rs, and DVD-Rs. I'm basically dual booting between XP and CentOS 4. Following the recipe in "The Linux Cookbook", I tried to copy a DVD using: dd if=/dev/hdd of=/tmp/diskfile.iso then cdrecord dev=/dev/hdd fs=32m

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/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:

Running C6 fileserver. Want to replace 7 year old HDs connected to an Areca ARC-1220 raid sata II (3Gb/s) controller. Has anyone used this controller with newer 2TB SATA III (6Gb/s) WD Re drives like the WD2000FYYZ or the WD2004FBYZ?

Hey guys, Thanks a lot for the CentOS 6 distro. I am having trouble burning the i386 dvds. I tried on a RHEL 6 deskop and also a CentOS 5 laptop. The command I am running on both systems is this: growisofs -dvd-compat -speed=4 -Z /dev/sr0=/home/gsgatlin/CentOS-6.0-i386-bin-DVD/CentOS-6.0-i386-bin-DVD.iso The error I am seeing is: :-( /dev/sr0: 2295104 blocks are free, 2297586 to be written!

> 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

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

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

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

On Fri, January 20, 2017 7:00 pm, Cameron Smith wrote: > Hi Valeri, > > > Before you pull a drive you should check to make sure that doing so > won't kill the whole array. Wow! What did I say to make you treat me as an ultimate idiot!? ;-) All my comments, at least in my own reading, we about things you need to do to make sure when you hot unplug bad drive it is indeed failed

Hi all, sorry for this extensive question, but I think that I'm missing something fundamental. I stepped into a surprising result with the integrate function and I would be glad if someone could put some light onto this. I try to integrate over an s-shaped growth-function. The results from this calculation seem to be correct for small values of t. Just for fun I tried some large values and

*Fluidshopping is a Berlin-based startup working on a customer analytics tool for online retailers. Customer Lifefitime Value (CLV) is the mythical 'magic number', the amount of money a particular customer will ever bring in. Knowing your CLV makes it trivial to: - optimize marketing spend for different inbound channels. - identify your highest value customers, - identify those in danger

On Fri, January 20, 2017 5:16 pm, Joseph L. Casale wrote: >> 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. > >