similar to: Sent from CentOS box First install no Sound

Hi Gang. I installed CentOS last night and the sound card detection failled to detect the sound card. I have a Asrock K8NF6G-VSTA mother board, with a nVidia NF6100-405 chip set. I have tried various live distro's and I ran Fedora 7 on it for just over 2 weeks and none of them detected the sound card. I'm a newbie to Red Hat based distributions but have been using Mandriva for

I wrote a bunch of files to a backup DVD about two months ago and now neither of my drives will read it. I get mount errors from "not a directory" to something like "unrecognized file system type" and so on, usually after a really long wait and a notice about how the drive is write-protected (duh). Here's what happened most recently: # mount /dev/hdc /mnt mount: block

Hi, I run hundreds of Redhat 8.0 boxes and Fedora Core 1 boxes, both Operation systems boxes give me some trouble reporting disk errors like the following (collected from /var/log/messages of each linux boxes by my own script). And a "badblocks" command on some of the related hard drive reports that failed sectors found, while others reports no, false-positive. Any one can give me

Hello all. I'm using RedHat 7.2 now and haven't have any problems until today. I can still boot into the system at this time, but cannot load X at all. I'm getting the following error message when I try to run fsck. /contains a file system with errors, check forced. Pass 1: Checking inodes, blocks and sizes Error reading block 1277964 (Attempt to read block from filesystem resulted

Hi, I get the below from dmesg. The server seems to run fine, but it does worry me. What should I do? Other than take a backup.. :-) hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0xd0 { Busy } ide: failed opcode was: unknown hda: DMA disabled ide0: reset: success hda: dma_timer_expiry: dma status == 0x21 hda: dma_intr: status=0x51 { DriveReady

Hi All, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady

Hi, Sorry if this is an old and fixed issue but I can't really seem to find a definitive explanation/fix to this in the mail lists. Ever since I upgraded to FC2 my server randomly decides that it can no longer access the disk and "aborts" the ext3 journal leaving it read-only as expected. I've seen the same errors on other mail list, explained away as disk or disk cable

Hello all, I am new to this list and hope that my mail is not OFF TOPIC. After looking around for 2 months now, to find a solution, I will try it here now. Now the scenario: I bought a new cool dell laptop: INSPIRON 8100, 512MB RAM, NVIDEA GeForce2Go 32MB, 30GB Hitachi hard disk and a DVD. I bought it with WinME preinstalled, because it wasn't possible to get it with linux nor without an

Hello everyone, I''m hoping to find an answer to my problem here. Currently I''m installing xen 2.0.7 on 30 dual opteron machines with 4GB memory. The machines have Tyan K8SR as motherboard with Silicon Image 3114 chip sata controler and 2 x 300 GB Western Digital SATA drives. Each xen server has 5 domUs, where some of them have high traffic and thus require high disk usage.

Hi All, I m a novice developer of Linux applications. Recently I faced a file system corruption. (I guess) I have a Kernel 2.4.7-10 with ext3 file system in compact flash. The system was up for 3 months and was running with average load conditions. One fine day, it just started sending kernel messages on the serial console. The message was like this. EXT3-fs error (device ide0(3,2)):

All, Trying to figure out how to deal with, I assume, a dying disk that's unfortunately on / (ext3). Getting errors similar to: Dec 31 20:44:30 mybox kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 31 20:44:30 mybox kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=163423, high=0, low=163423, sector=163360 Dec 31 20:44:30 mybox kernel: end_request:

I am running RH 7.3 with kernel 2.4.18-27.7.x. Recently I have added a new 60GB Quantum IDE hard drive to the server. I have set it up as a MASTER on a separate IDE channel. Two partitions on the /dev/hdc are /dev/hdc1, /dev/hdc2 - both using ext3. For more detailed HDD parameters, this is 'hdparm -i /dev/hdc': ----------------- /dev/hdc: Model=IC35L060AVV207-0, FwRev=V22OA66A,

Greetings, I am running Xen-3.0.2-3, with host OS kernel version 2.6.16.13-xen0. The system is a AMD Athlon XP running Debian/Etch. I have 3 SATA disks plugged into a Promise TX4 SATA controller. The disks are RAIDed using Linux md with LVM wrapped around the md''s for volume management. I currently am running 3 domUs, each with LVM backed vbd''s. This server has been up for

Wondering if anyone here might better be able to diagnose an issue we're seeing, or point me to some guidelines for this sort of thing. There are two machines with identical hardware, both running Red Hat 7.3's stock SMP kernel (required due to third party software). Both have come down with the same symptoms after having run fine for a number of months. The initial errors were these:

Would the following be symptoms of hardware problems or just a corrupt fs? Will fsck tonight when a new power supply is going into the machine. Kernel: 2.4.17 Drive: Maxtor D740X-6L 80GB connected via HPT366 Feb 25 21:26:33 viper kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error } Feb 25 21:26:33 viper kernel: hde: dma_intr: error=0x40 { UncorrectableError },

Hi, I'm having some serious problems diagnosing a hardware issue in my linux system. The following error occurs intermittently. I have replaced hard drives and it is still occurring. I'm trying to determine if it's a device conflict, a problem with the motherboard or something else. Can anyone help? hda: dma_intr: status=0x51 {DriveReady SeekComplete Error} hda: dma_intr: 0x40

Hi, yesterday my linux machine gave me some smartd errors so i checked the disk in another machine and it had defective sectors, I installed a new hard disk on the original machine. Today this is being reported in logwatch. I have a Maxtor (200gig) as hda, a cdrom as hdc and another hard disk that is used for storage as hdd. All plain IDE (not sata) --------------------- Kernel Begin

Help! I am running FC1, with a maxtor 160GB HD installed. Drive is only about a month old. I had just finished moving data from an older HD that was making some funny sounds and throwing some random errors. All was well. Last night we lost power for several hours and 1 machine's UPS/shutdown system didn't power down the workstation. The other 7 in our office did fine. The power

Hi All, I'm currently running an embedded linux system (arm) with a CF card mounted as EXT3. I'll copy some system details below... Anyway, I'm getting some drive errors and I'm wondering if they're due to bad/old drivers, something with EXT3 and CF latency, or something else entirely. These are the errors: hda: write_intr error1: nr_sectors=1, stat=0x51 hda:

I was creating some directories (mkdir xxxx) while cd'ed to a mounted LV. The first couple of directories were created but subsequent attempts give the following error: #mkdir: cannot create directory `xxxxx': Input/output error The contents of /var/log/messages shows this: Aug 5 10:48:57 inet05 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Aug 5 10:48:57