search for: lba48

...setup in a RAID-5 configuration. All drives are setup for 3.0 GiB SATA link, and the motherboard also supports that. Looking in dmesg when the system comes up, I see that reflected as well: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ATA-7, max UDMA/133, 312581808 sectors: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/133 scsi1 : ahci ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32) ata2.00: configured for UDMA/133 scsi2 : ahci ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata3.00:...

...s, and the case its in has very good airflow. ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD000 irq 193 ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD008 irq 193 scsi0 : sata_nv ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 320173056 sectors: LBA48 ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : sata_nv ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATA-7, max UDMA/133, 320173056 sectors: LBA48 ata2.00: ata2: dev 0 multi count 16 ata2.00: configured for UDMA/133 Vendor: ATA Model: Maxtor 6...

...cted [ 15.107086] usb 1-1: new full speed USB device using ohci_hcd and address 2 [ 15.119952] ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 15.151896] ata17.00: ATA-7: HITACHI HDS7250SASUN500G 0648KPU78F, K2AOAJ0A, max UDMA/133 [ 15.151898] ata17.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 15.151905] ata17.00: max_sectors limited to 256 for NCQ [ 15.153868] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 15.153870] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 15.153872] usb usb3: Product: OHCI Host Controller [ 15....

...ith the ServerWorks chipset in the 2.6.18 kernel. I am running a Dell 1435/CentOS 5.0-x86_64 with dual 250GB Western Digital NCQ supported drives, when I load up the OS I get these messages: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32) ata1.00: ata1: dev 0 multi count 8 ata1.00: configured for UDMA/133 scsi1 : sata_svw ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATA-7, max UDMA/133, 488281250 sectors: LBA48 NCQ (depth 0/32) ata2.00: ata2: dev 0 multi count 8 ata2.00: configured for UDMA...

...e408 irq 10 ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATAPI: PIONEER BD-ROM BDC-202, 1.01, max UDMA/66 ata3.00: configured for UDMA/66 ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata4.00: ATA-7: ST3500630AS, 3.AAC, max UDMA/133 ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) ata4.00: configured for UDMA/133 sda is HD sdb is HD again RAID1 sdc is the HD extra sdd should be hte ATAPI DVD but it ends up being the external USB nothing is at sde Where might my DVD be? Jerry

...E write cache for HVM qemu 0.8.2 has a flush callback to the storage backends, so now it is possible to implement hdparm tunable IDE write cache enable/disable for guest domains, allowing people to pick speed or data consistency on a case by case basis. As an added benefit, really large LBA48 IOs will now no longer be broken up into smaller IOs on the host side. From: Rik van Riel <riel@redhat.com> Signed-off-by: Christian Limpach <Christian.Limpach@xensource.com> However there seems to me to a be a bug in it: it does not take effect for DMA writes, which are handled...

...eeded for boot-time support. After a few more systems, I discovered that XP only wrote it if the boot volume passed the 33.8GB (32GiB) barrier -- at least on my disks that were BIOS LBA32 geometry with Sectors/Heads of 63/255. On newer disk arrays that break the 2.2TB (2TiB) barrier by supporting LBA48 / >255 heads, you _must_ basically use a LDM Disk Label. It appears Microsoft is not interested in any more "hacks" to support legacy BIOS/DOS Disk Labels -- especially given the fact that a lot of PC BIOS' out there are "broken" in their Extended Int13h Services and sup...

...: ata_piix ata1: SATA max UDMA/133 cmd 0x00000000000118c8 ctl 0x00000000000118ae bmdma 0x00000000000118b0 irq 19 ata2: SATA max UDMA/133 cmd 0x00000000000118c0 ctl 0x00000000000118aa bmdma 0x00000000000118b8 irq 19 ata1.00: ATA-6: ST380817AS, 3.42, max UDMA/133 ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32) ata1.01: ATA-8: ST3750330AS, AD14, max UDMA/133 ata1.01: 1465149168 sectors, multi 16: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/133 ata1.01: configured for UDMA/133 usb 1-1: device not accepting address 2, error -71 ata2.00: ATA-8: ST3750330AS, AD14, max UDMA/133 ata2.00...

...the beginning of the disk? > > Also I believe grub does not have this '/boot' location restriction. > Does it mean that their stage1.5 blob contains sata drivers so > stage1.5 uses sata directly instead of BIOS EDD? > I doubt your "old" BIOS doesn't support LBA48 (if I understand correctly, it supports SATA already). I am going to guess that you also performed your tests with an updated mbr.bin. I am also going to guess that, during your tests, you (re)installed Syslinux manually (not with scripts). We should also discard the possibility of some other is...

...atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: <HL-DT-ST, CD-ROM GCR-8522B, 1.00> SCSI0 5/cdrom removable wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 cd0(pciide0:0:1): using PIO mode 0, DMA mode 1 wd1 at pciide0 channel 1 drive 0: <WDC WD1600JB-00EVA0> wd1: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd2 at pciide0 channel 1 drive 1: <WDC WD1600BB-00FTA0> wd2: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 5 "Intel 82801EB/ER SMBus" rev 0x02 at...

Is there a standard way of copying a working system from one machine to another with different partitions? I have two CentOS-5.6 machines, say A and B, and I thought I would copy / on sdb10 on machine A to an unused partition sda7 on machine B with rsync. I made the appropriate changes to /etc/fstab and grub.conf , as well as /etc/sysconfig/network-scripts , but found that there were innumerable

...l /dev/sda". > I haven't looked into the problem yet, > and I don't even know what this old controller is. :) _All_ Escalade 7000/8000 series controllers use the same 64-bit ASIC, FPGA (field programmable) ATA logic and firmware. This includes a 7.5 (was it?) release that added LBA48 (ATA-6) addressing and UDMA Mode 6 (U133) speed support. Again., getting to 7.7.x should be a top priority - the RH3 and, especially, RH4 kernels have drivers that match these much newer 3Ware firmware-driver-3DM releaases. FYI: For reference: 7400/7800 = 33PCI64 full-length, 64-bit ASIC, 1MB S...

...UDMA/133 cmd 0xC480 ctl 0xC402 bmdma 0xBC00 irq 58 ata2: SATA max UDMA/133 cmd 0xC080 ctl 0xC002 bmdma 0xBC08 irq 58 scsi0 : sata_nv input: ImExPS/2 Generic Explorer Mouse as /class/input/input1 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ATA-7, max UDMA/133, 781422768 sectors: LBA48 NCQ (depth 0/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : sata_nv ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATA-7, max UDMA/133, 781422768 sectors: LBA48 NCQ (depth 0/32) ata2.00: ata2: dev 0 multi count 16 ata2.00: configured for UDMA/133...

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

Hello, I originally posted this to xen-users, but someone suggested I post it here. I am having ACPI problems on a PenguinComputing Altus1600 system. It has 2x dual core Opteron 2210 processors. The system boots with a standard Debian or Ubuntu SMP kernel, with ACPI enabled. However the xen live cd, binary xen install, as well as my own custom compile of xen 3.0.4 from source will not boot.

https://bugs.freedesktop.org/show_bug.cgi?id=49397 Aaron Plattner <aplattner at nvidia.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aplattner at nvidia.com |nouveau at lists.freedesktop.o | |rg

...ng ata4: softreset failed (device not ready) ata4: applying SB600 PMP SRST workaround and retrying ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-7: SAMSUNG HD753LJ, 1AA01113, max UDMA7 ata2.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA ata3.00: ATA-7: SAMSUNG HD753LJ, 1AA01113, max UDMA7 ata3.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ATA-7: SAMSUNG HD753LJ, 1AA01113, max U...

root at five-72 ~ # dd if=/dev/zero of=/dev/sdb bs=1M count=1000 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB) copied, 8.67101 s, 121 MB/s root at five-72 ~ # parted /dev/sdb GNU Parted 2.1 Using /dev/sdb Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) mklabel gpt (parted) print Model: ATA ST3000DM001-1CH1 (scsi) -->

...ON SH103S3120G firmware revision 501ABBF0 serial number 50026B7223027059 WWN 50026b7223027059 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 234441648 sectors LBA48 supported 234441648 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM non-rotating Feature Support Enabled Value Vendor read ahead yes yes write cache yes yes flush cac...

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