similar to: Xen stops booting at "SATA Link down (SStatus 0 SControl 300)"

On my machine I have SATA0: HD SATA1: HD these two drives are set as RAID1 SATA2: HD extra SATA3: DVD SATA4: external USB disk Snip from dmesg shows the ATAPI device being detected. ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xe400 irq 10 ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xe408 irq 10 ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATAPI: PIONEER BD-ROM

OK, it seems that the kernel I have (stock CentOS 4.7: 2.6.9-78.0.22.EL i686) seems to gronk the nVideo SATA controller in AHCI mode. It is NOT able to deal with the SATA DVD Burner I have. It is a "Sony Optiarc DVD Burner with LightScribe Black SATA Model AD-7241S-0B LightScribe Support". Is there some special magic I need to do? Here is the relevant bit from the boot up (SATA ports

I've been having an extremely hard time using the on board SATA controller on my nvidia based board. I have two 160gig Maxtor SATA drives attached to the on board controller, setup as software raid0. The problem is the array is extremely unreliable, where I'm getting constant I/O errors like: sd 0:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector

> > > > > [root at darkness ~]# ls -al /dev/sr* > > ls: cannot access /dev/sr*: No such file or directory > > [root at darkness ~]# ls /dev/s* > > /dev/sda /dev/sda3 /dev/sdb1 /dev/sg0 /dev/stderr > > /dev/sda1 /dev/sda4 /dev/sdb2 /dev/sg1 /dev/stdin > > /dev/sda2 /dev/sdb /dev/sdb3 /dev/snapshot /dev/stdout > > [root at

> > [ 2.183682] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 2.183825] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 7.183893] ata3.00: qc timeout (cmd 0xec) > [ 7.183908] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 7.183960] ata4.00: qc timeout (cmd 0xa1) > [ 7.183974] ata4.00: failed to IDENTIFY (I/O error,

hi, we've got a server with 6 sata disk (2 system raid1, 4 data raid5). recently we've got such error is the log and in these case the system is totally hang ie. it seems to crash but after 30-40 sec is start to working. we already 2 times replace the sata cables the problem still arrise what's more with different data disk (so not the same). we assume it can be some kind of sata

I am having problems getting my 64-bit Debian Squeeze (Xen version 4.0, Linux Kernel 2.6.32) dom0 to recognize a harddrive connected to a secondary sata controller. My motherboard is a Gigabyte GA-X79-UP4 and has two sata controllers. The first is controlled by an Intel X79 chipset and the second is controlled by a Marvell 88SE9172 chip. During the initial install of Debian everything is fine and

Hello, We have recently purchased two Supermicro servers, AS-1021M-T2RB (http://www.supermicro.com/Aplus/system/1U/1021/AS-1021M-T2RV.cfm), and have built them both with CentOS 5 operating system. They are identical, apart from the manufacturer of the disk drives. Kernel is: Linux version 2.6.18-8.1.6.el5 (mockbuild at builder6.centos.org) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP

Hi all, I'm sure this eventually will be resolved with a BIOS or kernel update, but in case someone experiences this on this or a similar motherboard, I thought I'd post a problem-and-workaround report. Platform CentOS5, x86_64 kernel-2.6.18-53.1.21.el5 Motherboard Asus M3a78-EMH HDMI SATA-controller configured as AHCI Experienced symptom; Periodic, ~20s lockups/freezes, several a

Hi folks. I'm posting this to both the Fedora as well as the CentOS lists in hopes that somewhere, someone can help me figure out what's going on. I have a dual Xeon 3GHz server that's performing rather slow when it comes to disk activities. The machine is configured with a single 160 GiB OS drive (with CentOS 5.0) and 4x500 GiB drives setup in a RAID-5 configuration.

On Mon, Jun 24, 2019 at 3:35 AM Pete Biggs <pete at biggs.org.uk> wrote: > On Sun, 2019-06-23 at 22:13 -0400, doug schmidt wrote: > > Hi, > > I'm having an issue with my Thinkpad P70 laptop/workstation. This system > is > > a dual boot, > > windows 10 pro and centos 7. I have not needed to use the cdrom until > now, > > however the system does not

Hello, I have a weird problem after adding new PV do LMV volume group. It seems the error comes out only during boot time. Please read the story. I have couple of 1U machines. They all have two, four or more Fujitsu-Siemens SAS 2,5" disks, which are bounded in Raid1 pairs with Linux mdadm. First pair of disks has always two arrays (md0, md1). Small md0 is used for booting and the rest - md1

Ok, got a quickie. I have an eSATA drive, a 750GB Seagate in an eSATA external enclosure, and a Silicon Image sil3132 ExpressCard controller for my laptop. The disk and controller work great in CentOS 5 (or F7, for that matter), if I specifically mount it. This is not how I want to have to use this drive, however. I want to hotplug it; that is, plug the controller into the laptop, and then

I am trying to get a pv_ops dom0 working for testing, but I am running into an elf_init error: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_init: not an ELF binary Full output attached. >From what I have read on the mailing lists, it seems that it is usually a problem with either grub or a corrupt dom0 kernel. Attached is my kernel config (2.6.28-rc6-tip). I followed the instructions on:

Hi, With the pcibackend feature of Xen 3.0.2, I pass a S-ATA card to a domU. This card is recognized with the sata_uli module but not the disk. # lspci 0000:02:09.0 Mass storage controller: ALi Corporation ALi M5281 Serial ATA / RAID Host Controller (rev a1) # modprobe sata_uli sata_uli 0000:02:09.0: version 0.5 ata3: SATA max UDMA/133 cmd 0xC800 ctl 0xC402 bmdma 0xB400 irq 16 ata4: SATA max

Hi, I have a SATA PCIe 6Gbps 4 port controller card made by Startech. The kernel (Linux viz1 2.6.32-220.4.1.el6.x86_64) sees it as Marvell Technology Group Ltd. 88SE9123 I use it to provide extra SATA ports to a raid system. The HD's are all "WD2003FYYS" and so run at 3Gbps on the 6Gbps controller. However I am seeing lots of instances of errors like this

https://bugs.freedesktop.org/show_bug.cgi?id=99482 Bug ID: 99482 Summary: nouveau driver returns -16 trying to hibernate Product: xorg Version: 7.7 (2012.06) Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Driver/nouveau

Hello, I just upgraded from Xen-3.3.1 to Xen-4.0.0. System is Gentoo, Hardware is DualCore AMD Athlon, 8GB RAM. The kernel was upgraded from OpenSUSE 2.6.27.29-0.1.1 to Gentoo-2.6.32-xen- r1. The first boot failed with an OOM error during kernel/initrd load, so I adjusted the dom0_mem option and had to increase it''s avalue from 256M to at least 400M until the dom0 could boot. At all

Hi All, I know Centos 5 is almost EOL and all this is old but.... I'm helping a colleague who has moved a Centos 5 install on an IDE disk to system with a Foxconn M'board. His idea is to use the SATA interface that's on the Foxconn. The thing boots OK and then gets into a loop trying to start the interfaces to the SATA disks. Oceans of stuff like this in /var/log/messages Aug 7

I've tested both 6.3 and 7.0-RC2, amd64 architecture, and have found the occurrence of an interrupt storm using an ASUS A8N-SLI Premium (nForce 4) motherboard with an AMD Opteron 175. Relevant dmesg output: atapci0: <nVidia nForce CK804 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: <ATA channel 0> on atapci0 ata1: <ATA