similar to: error on 3ware controller

I've got an i386 server running centos 4.2 with 3 3ware controllers in it -- an 8006-2 for the system disks and 2 7500-8s. On the 7500s, I'm running an all software RAID50. This morning I came in to find the system hung. Turns out a disk went overnight on one of the 7500s, and rather than a graceful failover I got this: Jan 6 01:03:58 $SERVER kernel: 3w-xxxx: scsi2: Command

I've been having no end of issues with a 3ware 9650SE-24M8 in a server that's coming on a year old. I've got 24 WDC WD5001ABYS drives (500GB) hooked to it, running as a single RAID6 w/ a hot spare. These issues boil down to the card periodically throwing errors like the following: sd 1:0:0:0: WARNING: (0x06:0x002C): Command (0x8a) timed out, resetting card. Usually when this

Hello all, I have a CentOS 5.7 machine hosting a 16 TB XFS partition used to house backups. The backups are run via rsync/rsnapshot and are large in terms of the number of files: over 10 million each. Now the machine is not particularly powerful: it is 64-bit machine, dual core CPU, 3 GB RAM. So perhaps this is a factor in why I am having the following problem: once in awhile that XFS partition

Dear All Problem with ext3 fs on 3ware 9500S controller: Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #145998372: rec_len is smaller than minim al - offset=0, inode=0, rec_len=0, name_len=0 Dec 7 05:59:50 stams kernel: Aborting journal on device sda1. Dec 7 05:59:50 stams kernel: ext3_abort called. Dec 7 05:59:50 stams kernel: EXT3-fs

Dear all I have a problem with splitting up a data frame called ReVerb: ?? str(ReVerb) `data.frame': 92713 obs. of 16 variables: $ CHILD : Factor w/ 7 levels "ABE","ADA","EVE",..: 1 1 1 1 1 1 1 1 1 1 ... $ AGE : Factor w/ 484 levels "1;06.00","1;06.16",..: 43 43 43 99 99 99 99 99 99 99 ... $ AGE_Q : num 2.0 2.0 2.0 2.4 2.4

Hi, I would like to make a replication of 10 of a linear, first order Autoregressive function, with respect to the replication of its innovation, e. for example: #where e is a random variables of innovation (from GEV distribution-that explains the rgev) #by using the arima.sim model from TSA package, I try to produce Y replicates, with respect to every replicates of e, #means for e[,1], I want

I had a failure over the weekend of my ext3 filesystems. Hardware: Dell 2550 (dual PIII 1 Ghz, 1GB ram, Acenic GigE card) Software: linux-2.4.14 ext3-2.4-0.9.15-2414 Trond's NFS patches (pathconf, tune,read,rpc_blk) The filesystem is RAID0 using LVM (1.0.1-rc4). The disks are connected using fiber channel (qlogic 2200, qlax00-4.27beta). I was generating high load on my nfs

Since I ain't got a better place to report this, I do it here: Kernel 2.4.20-ac1 # uptime 16:31:00 up 2 days, 22:10, 7 users, load average: 1.89, 2.20, 2.99 This is our main mailbox server. We're running ext3: # cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw 0 0 /proc /proc proc rw 0 0 /dev/sdb5 /boot ext3 rw 0 0 /dev/sda6 /home ext3 rw,noatime,nosuid 0 0 /dev/sdb8 /tmp

These came up on dmesg this morning: attempt to access beyond end of device 09:00: rw=0, want=1635237736, limit=976791680 attempt to access beyond end of device 09:00: rw=0, want=1635237736, limit=976791680 EXT3-fs error (device md(9,0)): ext3_free_blocks: Freeing blocks not in datazone - block = 4293394431, count = 1 attempt to access beyond end of device 09:00: rw=0, want=1930439616,

Hello all, Came across my first real "problem" in all the years I've been using Linux today and I'm stumped for an answer. I've recently built a back-up server on top of Centos 5.3 using a 3Ware 9650SE 4 port SATA card and 4 x 1.5TB drives in a RAID 5 array. I went for the 3Ware card as it has driver support already so any kernel updates won't require me to rebuild the

On a 2.4.15-pre5 system with a 3ware-Escalade-68000 IDE RAID (mode 1) we had the follwing "dmesg" output today: EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks in system zones - Block = 16, count = 1 EXT3-fs error (device sd(8,38)): ext3_free_blocks: bit already cleared for block 1052672 EXT3-fs error (device sd(8,38)): ext3_free_blocks: Freeing blocks not in datazone

Hi - We have had 3 rather major occurances of ext3 filesystem corruption lately, i.e. so bad we couldn't event mount, and fsck didn't help. I am looking for pointers, that could help us investigate the root cause. In general... We are running RedHat WS 3 Update 6, 2.4.21-40.2.ELsmp or 2.4.21-37.ELsmp We have a small SAN system that looks like this

Hi, I just noticed that my file server running 2.4.18-pre3 + IDE patches & NTFS patches has this error message in the logs: EXT3-fs error (device md(9,4)): ext3_free_blocks: Freeing blocks not in datazone - block = 33554432, count = 1 This is the only ext3 error I have seen and the uptime is currently over 74 days. The error actually appeared two weeks ago. The timing coincides well with

I have an Adaptec 392320 Ultra320 SCSI adapter. I am running x86_64 SLES9 SP3. When I build x86_64 Xen with just the 2.6-xen kernel + initrd, I am getting the following error on the module load. But if I go back to building separate xenU and xen0 kernels without initrd the device works without any issues. Any idea what is going wrong here? Am I leaving something out of my initrd? Here is the

Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The

I have a question regarding the building of the unified xen kernel (linux-2.6-xen) and the use of initrd. In the past I built both xen0 and xenU kernels; the xen0 default configurations had SCSI and Fusion MPT support compiled into the kernel. Now, they are built as modules. The problem is that I am unable to boot the xen kernel built that way, even though I am building an initrd. I have

Hi I've got serious troubles - I posted a while back about experiencing ext3 errors using 2.4.18, at the time I put the problems down to harddisk failure, but these problems are occurring more and more - not all of our systems are having this problem but 3 systems have now shown this problem. The hardware is essentially the same, the only difference is disk manufacturers but we've now

After a bit of searching through these archives I haven't found quite my problem described yet, so let me bounce this off you guys: Red Hat 7.2, I run up2date whenever patches come out; right now I'm using kernel 2.4.9-21. Things have been quite pleasant for several months, but in the last week I have begun receiving the following error messages: Feb 22 08:06:27 medmeta kernel:

A mysql database file was copied over to a new box running Fedora Core 1. The kernel was updated to the latest Fedora release. However mysqld complains about corrupted tables. The kernel was then updated to 2.6.5 mysqld still complains about corrupted tables. Hardware: Dual PIII 800. 3ware RAID dmesg: ... ... ... EXT3-fs error (device sdb1): ext3_free_blocks: Freeing blocks not in

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.2 Severity: important Tags: patch I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 / linux-image-2.6.26-2-xen-amd64 without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 / linux-image-2.6.32-5-xen-amd64 and now it does