Problem with JMicron 2x 3.5" SATA HD enclosure - JBOD

I bought the IcyBox 2x 3.5" SATA to USB enclosure and Arch does not detect 2nd drive. This enclosure supports SATA II hard disks with only JBOD.
dmesg gives this:
usb 2-2: USB disconnect, address 34
usb 2-2: new high speed USB device using ehci_hcd and address 35
usb 2-2: device descriptor read/64, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 8
usb 5-2: device descriptor read/64, error -110
usb 5-2: device descriptor read/64, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 9
usb 5-2: device descriptor read/64, error -110
usb 5-2: device descriptor read/64, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 10
usb 5-2: device descriptor read/8, error -110
usb 5-2: device descriptor read/8, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 11
usb 5-2: device descriptor read/8, error -110
usb 5-2: device descriptor read/8, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 36
usb 2-2: device descriptor read/64, error -110
usb 2-2: device descriptor read/64, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 37
usb 2-2: new high speed USB device using ehci_hcd and address 38
usb 2-2: device descriptor read/64, error -110
usb 2-2: device descriptor read/64, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 39
usb 2-2: device descriptor read/64, error -110
usb 2-2: device descriptor read/64, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 40
usb 2-2: device descriptor read/8, error -110
usb 2-2: device descriptor read/8, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 41
usb 2-2: device descriptor read/8, error -110
usb 2-2: device descriptor read/8, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 12
usb 5-2: device descriptor read/64, error -110
usb 5-2: device descriptor read/64, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 13
usb 5-2: device descriptor read/64, error -110
usb 5-2: device descriptor read/64, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 14
usb 5-2: device descriptor read/8, error -110
usb 5-2: device descriptor read/8, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 15
usb 5-2: device descriptor read/8, error -110
usb 5-2: device descriptor read/8, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 42
usb 2-2: device descriptor read/64, error -110
usb 2-2: device descriptor read/64, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 43
usb 2-2: device descriptor read/64, error -110
usb 2-2: device descriptor read/64, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 44
usb 2-2: device descriptor read/8, error -110
usb 2-2: device descriptor read/8, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 45
usb 2-2: device descriptor read/8, error -110
usb 2-2: device descriptor read/8, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 16
usb 5-2: device descriptor read/64, error -110
usb 5-2: device descriptor read/64, error -110
usb 5-2: new full speed USB device using uhci_hcd and address 17
usb 2-2: new high speed USB device using ehci_hcd and address 46
usb 2-2: device descriptor read/64, error -110
usb 2-2: new high speed USB device using ehci_hcd and address 47
usb 2-2: device descriptor read/64, error -110
usb 1-3: new high speed USB device using ehci_hcd and address 9
usb 1-3: configuration #1 chosen from 1 choice
usblp0: USB Bidirectional printer dev 9 if 0 alt 0 proto 2 vid 0x04A9 pid 0x10CA
usblp0: removed
usb 1-3: USB disconnect, address 9
usb 1-3: new high speed USB device using ehci_hcd and address 10
usb 1-3: configuration #1 chosen from 1 choice
usblp0: USB Bidirectional printer dev 10 if 0 alt 0 proto 2 vid 0x04A9 pid 0x10CA
usblp0: removed
usb 1-3: USB disconnect, address 10
usb 1-3: new high speed USB device using ehci_hcd and address 11
usb 1-3: configuration #1 chosen from 1 choice
usblp0: USB Bidirectional printer dev 11 if 0 alt 0 proto 2 vid 0x04A9 pid 0x10CA
usblp0: removed
usb 1-3: USB disconnect, address 11
usb 2-1: USB disconnect, address 17
usb 2-1: new high speed USB device using ehci_hcd and address 48
usb 2-1: configuration #1 chosen from 1 choice
usb-storage: device found at 48
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 2-2: new high speed USB device using ehci_hcd and address 49
usb 2-2: configuration #1 chosen from 1 choice
usb-storage: device found at 49
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 2-2: USB disconnect, address 49
usb 2-2: new high speed USB device using ehci_hcd and address 50
usb 2-2: configuration #1 chosen from 1 choice
usb-storage: device found at 50
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 2-2: USB disconnect, address 50
usb 2-2: new high speed USB device using ehci_hcd and address 51
usb 2-2: configuration #1 chosen from 1 choice
usb-storage: device found at 51
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 1-3: new high speed USB device using ehci_hcd and address 12
usb 1-3: configuration #1 chosen from 1 choice
usb-storage: device found at 12
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 1-3: USB disconnect, address 12
usb 1-3: new high speed USB device using ehci_hcd and address 13
usb 1-3: configuration #1 chosen from 1 choice
usb-storage: device found at 13
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 1-3: USB disconnect, address 13
usb 1-3: new high speed USB device using ehci_hcd and address 14
usb 1-3: configuration #1 chosen from 1 choice
usb-storage: device found at 14
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
usb 1-3: USB disconnect, address 14
usb 2-2: USB disconnect, address 51
usb 2-2: new high speed USB device using ehci_hcd and address 52
usb 2-2: configuration #1 chosen from 1 choice
usb-storage: device found at 52
usb-storage: waiting for device to settle before scanning
usb 2-2: USB disconnect, address 52
usb 2-2: new high speed USB device using ehci_hcd and address 53
usb 2-2: configuration #1 chosen from 1 choice
usb-storage: device found at 53
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 003: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 053: ID 152d:2336 JMicron Technology Corp. / JMicron USA Technology Corp. Hard Disk Drive
Bus 002 Device 048: ID 1058:1100 Western Digital Technologies, Inc.
Bus 002 Device 002: ID 064e:a101 Suyin Corp. Acer CrystalEye Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I don't know how to get access to the second drive. It's on and works if swaped with the 1st one.
As I know JMicron was or still is troublesome for Linux users.
Last edited by Kardell (2010-02-15 01:24:31)

I suspect a problem with SATA II incompatibility between these two hard drives.
The manual said that in the rare circumstances there is a requirement to downgrade SATA II hard drives to operate in SATA (150) mode. In both cases I have to use DOS applications to achieve this, but I cannot get access to these hard drives when they are inside enclosure connected via USB.
Can someone share some experience about enclosures? Is it the true reaction of the confused SATA controller to disable the second hard drive by default when such incompatibility occurs?
As you can see lsusb displays this usb connection named by its controller not by the mounted hard drive itself in this case Samsung or Hitachi one.

Similar Messages

Problems with JMicron-PATA-controller

Hi..
Two weeks ago I purchased new PC-components.
My new mainboard is an ASUS P5K Deluxe
It has a JMicron PATA-Controller onbaoard..
My two IDE-drives (DVD-rom and DVD-writer) are connected to this controller
[XazZ@darklight ~]$ lspci | grep IDE
03:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03)
Now this message spams my dmesg:
hda: cdrom_pc_intr: The drive appears confused (ireason = 0xd0). Trying to recover by ending request.
hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
hdb: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hdb: drive not ready for command
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hdb: drive not ready for command
I already searched for a solution - and someone suggested to add pci=routeirq to the kernel command-line (in my menu.lst)
I did that but it had no effect
In my kernel-config I activated the following options:
Device Drivers ---> <M> Serial ATA (prod) and Parallel ATA (experimental) drivers ---> <M> AHCI SATA support
<M> Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
<M> JMicron PATA support
If you need more information - just tell me
Thanks in advance
XazZ

Thanks for the reply
I think you are right
But I solved my problem a bit different:
After I've read your post I wanted to disable the old jmicron module in my kernel-config but I couldn't find it...
Then I opened
linux-2.6.22/drivers/ide/pci/Makefile
with an editor
There I've removed the following line:
obj-$(CONFIG_BLK_DEV_JMICRON) += jmicron.o
After that I've saved the Makefile and build my kernel
-> Works nice until now (tested it for ~30 - 45 minutes) - no dmesg spam anymore
After patching the Makefile:
[XazZ@darklight pci]$ lsmod | grep jmicron
pata_jmicron 4608 0
libata 108084 3 ata_generic,pata_jmicron,ahci
Before I patched it, only the module jmicron was loaded (pata_jmicron *wasn't* loaded)
Thanks for your hint/solution
XazZ

Big Problems with Samsung Series 830 SSD SATA III (256GB) and W520

Hi,
i get my W520 last week with an normal SATA 500 GB Drive, at home i changed it to a Samsung Series 830 SSD SATA III (256GB) and install windows 7 64bit pro via recovery media.
I was wondering, startup was taking very long .... from starting windows to the logon screen 1.45 minutes ... Now i tried a new recovery, same issue, tested the harddisk which is in good state.
I changed back to the 500GB Drive, startup take only 30 seconds around....
Are there any known issues?
Best Wishes
Markus
Solved!
Go to Solution.

Hi,
hope to catch all questions and some additional Information
1. RST is installed
2. BIOS 1.34
3. latest Lenovo Updates are all installed
4. latest Windows Updates are all installed
5. Clean Install i have tried, but first startup has shown the same issue
6. Tried the SSD via main bay and via multibay
7. checked BIOS for AHCI Mode
8. switched to Diagnostic mode (where can i view the report, machine goes driectly further in Booting windows)?
Machine Type is 42844MG
Core i7-2860QM (2.50GHz), 16GB RAM, 500GB 7200rpm HD, 15.6in FullHD LED BL 1920x1080 + Colorimeter, 2GB nVidia Quadro 2000M, CDRW/DVDRW, Intel 6300AGN Wireless, Modem, Bluetooth, UMTS, 1GB Ethernet, UltraNav, Secure chip, Fingerprint reader, Kamera, 9c Li-Ion, Windows 7 Professional (64-Bit)
What speaks again Samsung SSD's, at the moment it is the fastest SDD on the market and so far i've seen no bad rewiews.
I can't find any thread with same (SSD and problem) ... i have seen some SSD issues in another community thread, but not with same symtoms. I don't know where to locate, at the SSD, at W520, whereeever.
Best Wishes
Markus

Working on dv-7 6166nr with a problem with hp BD E DS6E2LH SATA CdRom Device

hp BD E DS6E2LH SATA CdRom Device will not load or play Blu rays. It plays Dvd and Cd.

Hi KingOfDeals,
Welcome to the HP Forums!
For you to have the best experience in the HP forum, I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I understand that your optical drive will not load or play Blue Ray disks but will DVDs and CDs.
Theres is a bios update for your system. VersionF.21, 5.85M. If that has not been previously update,d I would do that first. Updating the Bios. Have you done all your Windows updates?
You can run the HP Support Assistant to aid with updates and resolving issues. If you are still running Windows 7, you can use MS Fix It to help also.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Problems with 17" 2011 MBP optibay sata speeds for SSD.

I have a 17" early 2011 MBP. I noticed that the optibay SATA is only 3GB/S. Since I need to set up an internal RAID with SSD (SATA III 6Gb/S), and newer versions are now supporting this (I was under the impression that my earlier one would too), what are my options to get the optibay to work at the proper speed? Do I need to replace the MBP? Are there fixes that can be done by Apple repair?
I need this for a number of on site video editing jobs that I need to complete over the next four months. without the RAID set up, i don't see how I can do this. I am also in process of getting the new thunderbolt RAID for in the office.
Can anyone give me advice on how to address this issue? I can swap the system as long as I can pull the current disk drive (and replace with the one that was delivered with the system), if that is what I need to do.
Many thanks in advance.

Hi David,
What little I know about this for sure is that there are at least 2 different optical drive interfaces for the 2011 17" MBP.
I bet you can guess the difference; iirc correctly, the ones that shipped early on have the SATA II interface, while later/current ones have the SATA III. You can check yours in System Profiler, but again, I bet you know already. Again, iirc, the early ones cannot be updated to run at SATA III/6Gbps.
I don't know any of the above with 100% certainty, so I would continue looking/asking, but if it is correct, that means you'd need a new MBP (and need to make sure it's newer stock; what the cutoff is, I have no idea). fwiw

Raid problem with 845 PE and 2 SATA drive

have a big problem, I have bought an mainboard MSI 845PE MAX 3 SR, and I have installed 2 Hard drive Maxtor SATA 80GB in Combination Raid 0. When I install the operating system, Windows XP professional, after I have pushed F6 and insert the floppy, the installation continues but after 3 minute when the system install the FAST TRAK driver, I have a message " The driver is not certified for windows XP " if I click on OK or NO, the system stopped ...
please help me fast
ths
sorry for my bad english

Solved, it turned out to be a setting in BIOS that I overlooked, drive is now in use.

Problem with NEO2 and sata controller card

1.Product Type: MSI K8N Neo2 Platinum (MS-7025)
and the controller card is a InnoVision DM-8301 and the hard drive is a Seagate ST3320620AS
2.BIOS version: The newest one, 1C0 or something.
3.External VGA Type: Geforce 6800 GT
4.CPU Type: AMD 64 3500+
5.Memory Type: G Skill ZX 2048mb.
6.Power Supply Type:
7.Operating System: Xp Pro
8.Problem Description:
Hello. I have a strange problem with my controllercard. I wrote this text to InnoVision suport and they send me files and bios updates for a whole week and it was still the same problem. And then i tried the card in an older computer and everything worked fine.
I wrote
"Hello. I got some problems with my new controller card. I can find my new harddrive ,that's conected to the controller card, when iam inside windows and it's seems to be no problem. I can look on every seting on it and everywhere i look i can read "No problem". I Also did some test with the seatools programe and everything was fine. But when i schould copy files to it the coumputer start lagging after a few seconds and i cant do anything. After a while i can move the mouse around but the it laggs again. My computer is overclocked at the time but i have tried to use the harddrive when it's not clocked also. Also when im goin in to teh controlpanel and starts the setings for Sillicon Images sata controll and have music on my computer, the music laggs for a very very short moment. Something must be wrong and i can not find it."
It's still the same problem in my computer. The older computer had a MSI moderboard with a VIA chip and i have a nForce 3. InnoVison said i should talk to you about this problem. I have 3 harddrives but i use this controllercard because i want to have my computer overclocked and then i can't use 2 of the sata ports as i think you know.
I would be very thankful if you could help me with this problem.
//Martin

I've used a noname SATA pci card (non raid) with SIL3112 on my neo2 without problems with 1C bios.
Think you may try with a disk lower than 48bitLBA need (137GB barrier), eg a 120GB disk
Quote:
have the InnoVision EIO DM-8301 and had alot of problems using it with WD 160MB SATA drive.
I am using Intel 865 based MB with 2 original SATA channels. The original SATA channels are bootable.
I could not used the EIO card with 160G HDD. The whole setup is working only after I connected oine of my 120G Segate SATA HDD to the EIO Sata card.
I think this card do not properly support HDD above 120G.
Please respond to: [email protected]
http://www.devhardware.com/forums/storage-devices-80/sata-as-boot-20080-2.html
Btw: you have xp sp2 ?
48bitLBA is not enabled in the first version.
http://www.48bitlba.com/winxp.htm
Edit:
Here's another with complete different setup and same problems
http://forum.tweakxp.com/forum/Topic212148-4-1.aspx
I doubt it has anything to do with your motherboard and/or bios.
Btw: I looked at innovision and their drivers in download area are very old.
Get the latest SIL3112 drivers for XP here:
http://www.siliconimage.com/support/supportsearchresults.aspx?pid=63&cid=3&ctid=2&osid=4&
And remember 3112 is sata150 only , so it's not sure it will work with your drive at all .
Anyway it should be set to fixed sata1.5G with jumper - not certain the controller can autonegotiate
without trouble. You cannot have command queing enabled either , disk support only NCQ and controller TCQ
so having command queing set ON will cause major conflicts in data transfers.

[SOLVED] Problem with second SATA drive

My laptop has two hard drive bays, and just recently I added a second SATA drive (moved it from my old laptop) to the extra bay.
Now, anytime the second hard drive /dev/sdb has any heavy disk activity, it appears to cause a shutdown of the SATA port for the first drive (/dev/sda)! Though the second drive is still fine, and I can still write to it until the system crashes from the root drive (on /dev/sda) being shutdown.
If I don't mount and use the second drive, the first drive works just fine, and I can pound it with traffic without issue.
I can reproduce this problem by copying large amounts of data to drive 2.
This is when I get in my dmesg when the first SATA drive shuts down:
[ 3013.249525] ata1.00: exception Emask 0x0 SAct 0x7ff SErr 0x0 action 0x6 frozen
[ 3013.249532] ata1.00: failed command: READ FPDMA QUEUED
[ 3013.249539] ata1.00: cmd 60/08:00:78:b8:ba/00:00:24:00:00/40 tag 0 ncq 4096 in
[ 3013.249539] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 3013.249543] ata1.00: status: { DRDY }
[ 3013.249545] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249559] ata1.00: cmd 61/08:08:b8:60:7b/00:00:29:00:00/40 tag 1 ncq 4096 out
[ 3013.249559] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249562] ata1.00: status: { DRDY }
[ 3013.249564] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249568] ata1.00: cmd 61/08:10:c0:60:7b/00:00:29:00:00/40 tag 2 ncq 4096 out
[ 3013.249568] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249570] ata1.00: status: { DRDY }
[ 3013.249572] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249576] ata1.00: cmd 61/08:18:c8:60:7b/00:00:29:00:00/40 tag 3 ncq 4096 out
[ 3013.249576] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249578] ata1.00: status: { DRDY }
[ 3013.249580] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249585] ata1.00: cmd 61/08:20:48:12:d7/00:00:18:00:00/40 tag 4 ncq 4096 out
[ 3013.249585] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249587] ata1.00: status: { DRDY }
[ 3013.249589] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249593] ata1.00: cmd 61/08:28:28:63:38/00:00:19:00:00/40 tag 5 ncq 4096 out
[ 3013.249593] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249595] ata1.00: status: { DRDY }
[ 3013.249597] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249601] ata1.00: cmd 61/08:30:28:6f:38/00:00:19:00:00/40 tag 6 ncq 4096 out
[ 3013.249601] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249603] ata1.00: status: { DRDY }
[ 3013.249605] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249609] ata1.00: cmd 61/08:38:28:98:ae/00:00:25:00:00/40 tag 7 ncq 4096 out
[ 3013.249609] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249611] ata1.00: status: { DRDY }
[ 3013.249613] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249617] ata1.00: cmd 61/08:40:d8:79:3b/00:00:25:00:00/40 tag 8 ncq 4096 out
[ 3013.249617] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249619] ata1.00: status: { DRDY }
[ 3013.249621] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249625] ata1.00: cmd 61/08:48:08:98:b6/00:00:18:00:00/40 tag 9 ncq 4096 out
[ 3013.249625] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249627] ata1.00: status: { DRDY }
[ 3013.249629] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249633] ata1.00: cmd 61/08:50:10:98:36/00:00:19:00:00/40 tag 10 ncq 4096 out
[ 3013.249633] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249636] ata1.00: status: { DRDY }
[ 3013.249640] ata1: hard resetting link
[ 3013.575549] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3013.576784] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 3013.578334] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 3013.578588] ata1.00: configured for UDMA/133
[ 3013.592223] ata1.00: device reported invalid CHS sector 0
[ 3013.592233] ata1.00: device reported invalid CHS sector 0
[ 3013.592238] ata1.00: device reported invalid CHS sector 0
[ 3013.592242] ata1.00: device reported invalid CHS sector 0
[ 3013.592246] ata1.00: device reported invalid CHS sector 0
[ 3013.592250] ata1.00: device reported invalid CHS sector 0
[ 3013.592254] ata1.00: device reported invalid CHS sector 0
[ 3013.592258] ata1.00: device reported invalid CHS sector 0
[ 3013.592263] ata1.00: device reported invalid CHS sector 0
[ 3013.592267] ata1.00: device reported invalid CHS sector 0
[ 3013.592271] ata1.00: device reported invalid CHS sector 0
[ 3013.592302] sd 0:0:0:0: [sda]
[ 3013.592306] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592310] sd 0:0:0:0: [sda]
[ 3013.592313] Sense Key : 0xb [current] [descriptor]
[ 3013.592320] Descriptor sense data with sense descriptors (in hex):
[ 3013.592323] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592342] 00 00 00 00
[ 3013.592351] sd 0:0:0:0: [sda]
[ 3013.592353] ASC=0x0 ASCQ=0x0
[ 3013.592358] sd 0:0:0:0: [sda] CDB:
[ 3013.592361] cdb[0]=0x28: 28 00 24 ba b8 78 00 00 08 00
[ 3013.592376] end_request: I/O error, dev sda, sector 616216696
[ 3013.592414] sd 0:0:0:0: [sda]
[ 3013.592417] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592421] sd 0:0:0:0: [sda]
[ 3013.592423] Sense Key : 0xb [current] [descriptor]
[ 3013.592428] Descriptor sense data with sense descriptors (in hex):
[ 3013.592431] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592449] 00 00 00 00
[ 3013.592458] sd 0:0:0:0: [sda]
[ 3013.592460] ASC=0x0 ASCQ=0x0
[ 3013.592465] sd 0:0:0:0: [sda] CDB:
[ 3013.592467] cdb[0]=0x2a: 2a 00 29 7b 60 b8 00 00 08 00
[ 3013.592482] end_request: I/O error, dev sda, sector 695951544
[ 3013.592505] sd 0:0:0:0: [sda]
[ 3013.592508] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592512] sd 0:0:0:0: [sda]
[ 3013.592514] Sense Key : 0xb [current] [descriptor]
[ 3013.592519] Descriptor sense data with sense descriptors (in hex):
[ 3013.592522] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592540] 00 00 00 00
[ 3013.592549] sd 0:0:0:0: [sda]
[ 3013.592551] ASC=0x0 ASCQ=0x0
[ 3013.592556] sd 0:0:0:0: [sda] CDB:
[ 3013.592558] cdb[0]=0x2a: 2a 00 29 7b 60 c0 00 00 08 00
[ 3013.592572] end_request: I/O error, dev sda, sector 695951552
[ 3013.592583] sd 0:0:0:0: [sda]
[ 3013.592586] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592589] sd 0:0:0:0: [sda]
[ 3013.592592] Sense Key : 0xb [current] [descriptor]
[ 3013.592597] Descriptor sense data with sense descriptors (in hex):
[ 3013.592599] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592618] 00 00 00 00
[ 3013.592626] sd 0:0:0:0: [sda]
[ 3013.592628] ASC=0x0 ASCQ=0x0
[ 3013.592632] sd 0:0:0:0: [sda] CDB:
[ 3013.592635] cdb[0]=0x2a: 2a 00 29 7b 60 c8 00 00 08 00
[ 3013.592649] end_request: I/O error, dev sda, sector 695951560
[ 3013.592665] sd 0:0:0:0: [sda]
[ 3013.592668] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592671] sd 0:0:0:0: [sda]
[ 3013.592673] Sense Key : 0xb [current] [descriptor]
[ 3013.592678] Descriptor sense data with sense descriptors (in hex):
[ 3013.592684] Aborting journal on device dm-0-8.
[ 3013.592701] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:4476: Journal has aborted
[ 3013.592687] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592723] 00 00 00 00
[ 3013.592729] sd 0:0:0:0: [sda]
[ 3013.592730] ASC=0x0 ASCQ=0x0
[ 3013.592733] sd 0:0:0:0: [sda] CDB:
[ 3013.592735] cdb[0]=0x2a: 2a 00 18 d7 12 48 00 00 08 00
[ 3013.592744] end_request: I/O error, dev sda, sector 416748104
[ 3013.592752] Buffer I/O error on device dm-0, logical block 266057
[ 3013.592760] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5902184 (offset 258048 size 4096 starting block 266057)
[ 3013.592766] sd 0:0:0:0: [sda]
[ 3013.592768] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592771] sd 0:0:0:0: [sda]
[ 3013.592772] Sense Key : 0xb [current] [descriptor]
[ 3013.592776] Descriptor sense data with sense descriptors (in hex):
[ 3013.592778] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592790] 00 00 00 00
[ 3013.592795] sd 0:0:0:0: [sda]
[ 3013.592797] ASC=0x0 ASCQ=0x0
[ 3013.592800] sd 0:0:0:0: [sda] CDB:
[ 3013.592801] cdb[0]=0x2a: 2a 00 19 38 63 28 00 00 08 00
[ 3013.592811] end_request: I/O error, dev sda, sector 423125800
[ 3013.592817] Buffer I/O error on device dm-0, logical block 1063269
[ 3013.592822] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5898577 (offset 970752 size 4096 starting block 1063269)
[ 3013.592842] sd 0:0:0:0: [sda]
[ 3013.592845] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592849] sd 0:0:0:0: [sda]
[ 3013.592851] Sense Key : 0xb [current] [descriptor]
[ 3013.592856] Descriptor sense data with sense descriptors (in hex):
[ 3013.592859] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592877] 00 00 00 00
[ 3013.592885] sd 0:0:0:0: [sda]
[ 3013.592887] ASC=0x0 ASCQ=0x0
[ 3013.592892] sd 0:0:0:0: [sda] CDB:
[ 3013.592894] cdb[0]=0x2a: 2a 00 19 38 6f 28 00 00 08 00
[ 3013.592908] end_request: I/O error, dev sda, sector 423128872
[ 3013.592915] Buffer I/O error on device dm-0, logical block 1063653
[ 3013.592922] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5902187 (offset 1171456 size 4096 starting block 1063653)
[ 3013.592931] sd 0:0:0:0: [sda]
[ 3013.592934] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592937] sd 0:0:0:0: [sda]
[ 3013.592940] Sense Key : 0xb [current] [descriptor]
[ 3013.592945] Descriptor sense data with sense descriptors (in hex):
[ 3013.592947] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592966] 00 00 00 00
[ 3013.592974] sd 0:0:0:0: [sda]
[ 3013.592976] ASC=0x0 ASCQ=0x0
[ 3013.592980] sd 0:0:0:0: [sda] CDB:
[ 3013.592983] cdb[0]=0x2a: 2a 00 25 ae 98 28 00 00 08 00
[ 3013.592997] end_request: I/O error, dev sda, sector 632199208
[ 3013.593006] Buffer I/O error on device dm-0, logical block 27197445
[ 3013.593018] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 6425165 (offset 151552 size 4096 starting block 27197445)
[ 3013.593028] sd 0:0:0:0: [sda]
[ 3013.593031] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.593034] sd 0:0:0:0: [sda]
[ 3013.593037] Sense Key : 0xb [current] [descriptor]
[ 3013.593042] Descriptor sense data with sense descriptors (in hex):
[ 3013.593045] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.593063] 00 00 00 00
[ 3013.593071] sd 0:0:0:0: [sda]
[ 3013.593073] ASC=0x0 ASCQ=0x0
[ 3013.593078] sd 0:0:0:0: [sda] CDB:
[ 3013.593085] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:4476: Journal has aborted
[ 3013.593089] cdb[0]=0x2a: 2a 00 25 3b 79 d8 00 00 08 00
[ 3013.593104] end_request: I/O error, dev sda, sector 624654808
[ 3013.593111] Buffer I/O error on device dm-0, logical block 26254395
[ 3013.593115] lost page write due to I/O error on dm-0
[ 3013.593126] sd 0:0:0:0: [sda]
[ 3013.593129] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.593132] sd 0:0:0:0: [sda]
[ 3013.593135] Sense Key : 0xb [current] [descriptor]
[ 3013.593140] Descriptor sense data with sense descriptors (in hex):
[ 3013.593142] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.593161] 00 00 00 00
[ 3013.593169] sd 0:0:0:0: [sda]
[ 3013.593171] ASC=0x0 ASCQ=0x0
[ 3013.593175] sd 0:0:0:0: [sda] CDB:
[ 3013.593178] cdb[0]=0x2a: 2a 00 18 b6 98 08 00 00 08 00
[ 3013.593192] end_request: I/O error, dev sda, sector 414619656
[ 3013.593198] Buffer I/O error on device dm-0, logical block 1
[ 3013.593201] lost page write due to I/O error on dm-0
[ 3013.593211] sd 0:0:0:0: [sda]
[ 3013.593213] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.593217] sd 0:0:0:0: [sda]
[ 3013.593219] Sense Key : 0xb [current] [descriptor]
[ 3013.593224] Descriptor sense data with sense descriptors (in hex):
[ 3013.593227] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.593245] 00 00 00 00
[ 3013.593253] sd 0:0:0:0: [sda]
[ 3013.593256] ASC=0x0 ASCQ=0x0
[ 3013.593260] sd 0:0:0:0: [sda] CDB:
[ 3013.593262] cdb[0]=0x2a: 2a 00 19 36 98 10 00 00 08 00
[ 3013.593277] end_request: I/O error, dev sda, sector 423008272
[ 3013.593283] Buffer I/O error on device dm-0, logical block 1048578
[ 3013.593286] lost page write due to I/O error on dm-0
[ 3013.593298] ata1: EH complete
[ 3013.595707] EXT4-fs error (device dm-0) in ext4_dirty_inode:4603: Journal has aborted
[ 3013.596581] EXT4-fs error (device dm-0): ext4_journal_start_sb:370: Detected aborted journal
[ 3013.596591] EXT4-fs (dm-0): Remounting filesystem read-only
[ 3020.421558] journal commit I/O error
[ 3020.421570] journal commit I/O error
[ 3020.421574] journal commit I/O error
[ 3020.421578] journal commit I/O error
[ 3020.421581] journal commit I/O error
[ 3147.052191] ata1.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x6 frozen
[ 3147.052197] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052209] ata1.00: cmd 60/50:00:d0:48:99/00:00:1c:00:00/40 tag 0 ncq 40960 in
[ 3147.052209] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 3147.052212] ata1.00: status: { DRDY }
[ 3147.052213] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052218] ata1.00: cmd 60/18:08:28:49:99/00:00:1c:00:00/40 tag 1 ncq 12288 in
[ 3147.052218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3147.052220] ata1.00: status: { DRDY }
[ 3147.052221] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052226] ata1.00: cmd 60/88:10:48:49:99/00:00:1c:00:00/40 tag 2 ncq 69632 in
[ 3147.052226] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3147.052228] ata1.00: status: { DRDY }
[ 3147.052229] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052234] ata1.00: cmd 60/20:18:00:a4:ba/00:00:24:00:00/40 tag 3 ncq 16384 in
[ 3147.052234] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3147.052236] ata1.00: status: { DRDY }
[ 3147.052239] ata1: hard resetting link
[ 3147.378368] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3148.066853] ata1.00: ACPI cmd ef/5a:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3148.069139] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 3148.069393] ata1.00: configured for UDMA/133
[ 3148.080059] ata1.00: device reported invalid CHS sector 0
[ 3148.080066] ata1.00: device reported invalid CHS sector 0
[ 3148.080071] ata1.00: device reported invalid CHS sector 0
[ 3148.080075] ata1.00: device reported invalid CHS sector 0
[ 3148.080112] sd 0:0:0:0: [sda]
[ 3148.080114] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080117] sd 0:0:0:0: [sda]
[ 3148.080118] Sense Key : 0xb [current] [descriptor]
[ 3148.080123] Descriptor sense data with sense descriptors (in hex):
[ 3148.080125] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080136] 00 00 00 00
[ 3148.080140] sd 0:0:0:0: [sda]
[ 3148.080142] ASC=0x0 ASCQ=0x0
[ 3148.080145] sd 0:0:0:0: [sda] CDB:
[ 3148.080146] cdb[0]=0x28: 28 00 1c 99 48 d0 00 00 50 00
[ 3148.080156] end_request: I/O error, dev sda, sector 479807696
[ 3148.080170] sd 0:0:0:0: [sda]
[ 3148.080171] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080173] sd 0:0:0:0: [sda]
[ 3148.080175] Sense Key : 0xb [current] [descriptor]
[ 3148.080178] Descriptor sense data with sense descriptors (in hex):
[ 3148.080180] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080190] 00 00 00 00
[ 3148.080195] sd 0:0:0:0: [sda]
[ 3148.080196] ASC=0x0 ASCQ=0x0
[ 3148.080199] sd 0:0:0:0: [sda] CDB:
[ 3148.080200] cdb[0]=0x28: 28 00 1c 99 49 28 00 00 18 00
[ 3148.080209] end_request: I/O error, dev sda, sector 479807784
[ 3148.080216] sd 0:0:0:0: [sda]
[ 3148.080218] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080220] sd 0:0:0:0: [sda]
[ 3148.080221] Sense Key : 0xb [current] [descriptor]
[ 3148.080224] Descriptor sense data with sense descriptors (in hex):
[ 3148.080225] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080236] 00 00 00 00
[ 3148.080241] sd 0:0:0:0: [sda]
[ 3148.080242] ASC=0x0 ASCQ=0x0
[ 3148.080245] sd 0:0:0:0: [sda] CDB:
[ 3148.080246] cdb[0]=0x28: 28 00 1c 99 49 48 00 00 88 00
[ 3148.080254] end_request: I/O error, dev sda, sector 479807816
[ 3148.080267] sd 0:0:0:0: [sda]
[ 3148.080268] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080270] sd 0:0:0:0: [sda]
[ 3148.080272] Sense Key : 0xb [current] [descriptor]
[ 3148.080274] Descriptor sense data with sense descriptors (in hex):
[ 3148.080276] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080287] 00 00 00 00
[ 3148.080291] sd 0:0:0:0: [sda]
[ 3148.080293] ASC=0x0 ASCQ=0x0
[ 3148.080295] sd 0:0:0:0: [sda] CDB:
[ 3148.080296] cdb[0]=0x28: 28 00 24 ba a4 00 00 00 20 00
[ 3148.080305] end_request: I/O error, dev sda, sector 616211456
[ 3148.080315] ata1: EH complete
I have experimented, and found that if I turn off NCQ on the kernel command line in my bootloader (libata.force=noncq), that it takes longer before the problem occurs. Though, if I write enough to the second drive, it does still happen after a while, just greatly reduced its chances of happening.
Is it possible that the old drive (sdb) is causing the problem? I noticed that it is much noisier than I remember when the drive head moves around.
Another curiosity while I was trying to duplicate the problem:
- I start a large file copy from sda -> sdb
- At the same time in another terminal, I do "find / -print"
- When I hear the drive 2 head moving, it pauses the output of the "find" command.
Every time I hear the head move, I see the find output pause. Its almost like the drive seek on drive 2 causes the whole Sata controller to pause while the head moves. Very odd!
Anyone have any ideas? I think the next thing I will try is borrow a drive from another machine, and do the big write to it to see if I get the same results.
If it is of any help, here is some more info on the laptop:
lspci:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1251 (rev a1)
01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1)
07:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)
0d:00.0 Network controller: Intel Corporation Centrino Advanced-N + WiMAX 6250 (rev 5e)
13:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
13:00.1 SD Host controller: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
19:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
cat /proc/interrupts:
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
0: 50 0 0 0 0 0 0 0 IO-APIC-edge timer
1: 958 0 0 0 0 0 0 0 IO-APIC-edge i8042
8: 1 0 0 0 0 0 0 0 IO-APIC-edge rtc0
9: 1675 0 0 0 0 0 0 0 IO-APIC-fasteoi acpi
12: 12257 0 0 0 0 0 0 0 IO-APIC-edge i8042
16: 24769 0 0 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb1, mmc0, nvidia
17: 142 0 0 0 0 0 0 0 IO-APIC-fasteoi snd_hda_intel
19: 0 0 0 0 0 0 0 0 IO-APIC-fasteoi rts_pstor
23: 1937 0 0 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb4
41: 1 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
42: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
43: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
44: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
45: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
46: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
47: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
48: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
49: 19406 0 0 0 0 0 0 0 PCI-MSI-edge iwlwifi
50: 36099 0 0 0 0 0 0 0 PCI-MSI-edge ahci
51: 14 0 0 0 0 0 0 0 PCI-MSI-edge mei
52: 386378 0 0 0 0 0 0 0 PCI-MSI-edge snd_hda_intel
53: 56803 0 0 0 0 0 0 0 PCI-MSI-edge eth0
NMI: 34 5 19 5 18 4 13 4 Non-maskable interrupts
LOC: 77964 17705 161241 14302 187823 16150 56845 12750 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 34 5 19 5 18 4 13 4 Performance monitoring interrupts
IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts
RTR: 7 0 0 0 0 0 0 0 APIC ICR read retries
RES: 13721 7023 304 110 175 110 213 123 Rescheduling interrupts
CAL: 6941 7677 2774 7670 5804 7568 7655 7673 Function call interrupts
TLB: 366 545 268 179 310 272 212 166 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 29 29 29 29 29 29 29 29 Machine check polls
ERR: 0
MIS: 0
smartctl --all /dev/sda
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.3-1-ARCH] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: ST9500423AS
Serial Number: 5WS354LM
LU WWN Device Id: 5 000c50 044bb741b
Firmware Version: 0005DEM1
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Thu Sep 13 15:26:14 2012 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 105) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x303f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 113 099 006 Pre-fail Always - 54715920
3 Spin_Up_Time 0x0003 098 098 085 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1114
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 069 060 030 Pre-fail Always - 10214892
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2030
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 559
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 098 000 Old_age Always - 8590065667
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 053 049 045 Old_age Always - 47 (Min/Max 47/51)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 17
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 871
193 Load_Cycle_Count 0x0032 039 039 000 Old_age Always - 122293
194 Temperature_Celsius 0x0022 047 051 000 Old_age Always - 47 (0 17 0 0 0)
195 Hardware_ECC_Recovered 0x001a 113 099 000 Old_age Always - 54715920
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 67229123085518
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1947733828
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2798982459
254 Free_Fall_Sensor 0x0032 001 001 000 Old_age Always - 899
SMART Error Log Version: 1
ATA Error Count: 8 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 8 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:21:04.124 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
Error 7 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:21:04.124 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
Error 6 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
Error 5 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 05:20:58.724 READ LOG EXT
Error 4 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 05:20:58.724 READ LOG EXT
61 00 08 ff ff ff 4f 00 05:20:58.724 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 05:20:58.724 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 6 -
# 2 Short offline Aborted by host 90% 1 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
smartctl --all /dev/sdb
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.3-1-ARCH] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint M6
Device Model: SAMSUNG HM320JI
Serial Number: S16LJF0QB02815
LU WWN Device Id: 5 0f0000 001202815
Firmware Version: 2SS00_01
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Thu Sep 13 15:27:10 2012 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 110) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 110) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0007 252 252 025 Pre-fail Always - 2562
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 810
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000e 252 252 051 Old_age Always - 0
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 4842
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 440
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 154
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 71
194 Temperature_Celsius 0x0022 073 073 000 Old_age Always - 55 (Min/Max 17/55)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 1
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 252 252 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x0032 252 252 000 Old_age Always - 0
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 534
225 Load_Cycle_Count 0x0032 077 077 000 Old_age Always - 236803
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Last edited by johni (2012-09-16 00:46:54)

It appears my drive one really is failing. It was the first drive and not the second making the loud head seek sound. I borrowed another drive from a friend, and copied my drive one to it. No problems with the new drive in place.

Right, MacBook Pro 17" early 2011(Built March) and my new OCZ sata III 6G not working, when is Apple going to admit there is a problem with the Intel's 6 Series Chipset. In System Information it says "Link Speed: 6 Gigabit" which is sata III.

My MacBook Pro 17" early 2011(built March) and my new OCZ sata III 6G are not working together, when is Apple going to admit there is a problem with the Intel's 6 Series Chipset. In System Information it says "Link Speed: 6 Gigabit" which is sata III and in my MacBook Pro it does not work.
Now MacBook Pro 17" early 2011 built May onward do not have this problem it was fixed in the Intel's 6 Series Chipset. (So there is a problem). Cam I have my MacBook Pro fixed please.

After biting the bullet and ordering more RAM, my computer now is working a ton better. So that must have been the main issue. With 8 GB RAM, I can now even run Parallels fluidly (better than my work PC!) where before simple things like logging in to my MBP after reboot could take forever.
The place I went to had several other people getting RAM upgrades at the same time as me, so between this and other comments I've seen in discussions here and elsewhere on the Internets, I take it to mean that either Apple should bump up the base RAM on its new machines, and/or stop charging so much for additional RAM.
I refused to believe a Pro machine bought with Lion installed would come with too little RAM for light to medium usage, but it was apparently the case. I'll mark this as a correct answer and hope some other poor soul will come across this thread and be helped by it.

MOVED: Problem with SATA DVD/RW

This topic has been moved to AMD64 nVidia Based board.
Problem with SATA DVD/RW

I use the Plextor PX-712SA's with no issues. However...I do not believe the SATA versions require jumpers. Try plugging them in on SATA port 1 or 2, making sure those are enabled in BIOS of course. Make sure all connections are secure. There have been some issues with these particular drives not operating properly, but it has not been an issue with seasoned system builders, so the problems may be with the builder himself. Usually, Plextors are so good, they'll almost burn a paper plate! Try a different medium, maybe another brand of blank CD or DVD.
You may also want to check Device Manager in Windows, to see if it is listed "This device is working properly"!

Boot problems with IDE HD and SATA HD on K7N2-Delta L

I'll get right to the point.
I have an PCI SATA Controller Card in my system (using a K7N2 Delta-L motherboard, BIOS v5.7 with an Athlon XP 2800+ and Corsair ValueSelect 512MB DDR400 RAM on a single stick). My system works fine in it's original configuration of drives (CD-RW drive only drive on IDE bus, and SATA drive only hard drive). However, upon installing my IDE hard drive from my old computer, the system will no longer boot right. I am connecting the other IDE HD as Slave on the CD-RW's bus, as I'm reserving the second bus for bigger and better things such as a DVD burner, and speed isn't too important for this hard drive as it's just my MP3/data I don't need in a hurry drive.
In the current configuration, all three drives are detected properly (CD-RW and HD detected on the IDE detection screen, and the SATA drive detected on the SATA card's detection screen). However, after the SATA detection screen, the system just stops. The cursor is still blinking, but nothing comes up.
Both hard drives are Western Digitals (IDE is a ATA100 Western Digital 60GB at 5400 RPM, and the SATA is a Western Digital 36.7GB at 10,000 RPM), and the CD-RW is a HP CD-Writer 9100. I have Windows XP installed on both hard drives (first partition of the IDE, which is divided into two), but considering the system doesn't even attempt to boot I don't think that's an issue. I've gone through and tried enabling and disabling "Boot Other Device", but still no love. My boot order is set to Floppy, CD-ROM, and SCSI, which works fine when the SATA drive is in there.
Any idea what's up? I can provide more information upon request, as I'm sure there's something I forgot to mention that's important.
Thanks.

Take a look at this link, https://forum-en.msi.com/index.php?threadid=71384, I think you both have the same problem. It seems that a sata drive doesn't like having an ide drive in the system that has an active partition.
Do like Wonkanoby suggest, reformat the ide hard drive and make sure that it's not set to be the active partition in the system. Boot with a 98 boot floppy if you have to so you can format the ide drive to fat32, once you can boot up using the sata drive you can use xp disk manager to convert the ide drive to ntfs.

Problems with itunes videos playing on NVidia Graphics/SATA controllers FIX

Hi folks just wanted to let you know there is a hotfix for all you folks that have a Vista Computer that has Nvidia Graphics cards GEFORCE series, and Nvidia SATA Drive Controllers.... Go to this website and do al the hoit fixes listed there... http://www.nvidia.com/object/windowsvistahotfixes.html
This will update the firmware for your graphics card and some vista incompatibility issues. Not all of the hotfixes may apply to your system however try downloading all four and it will tell you if it applies to your system or not after you try to install them. After that go to your Control panel and go to device manager and go to your storage card section.. Click on the Nvidia SATA controller device click on the driver section and click on update driver... this will bring up a screen that asks you to have the computer search for the correct driver "click it". It will search the internet for you and download the NEW SATA driver you will have to restart after downloading. THEN go back into the control panel again and make sure the driver is updated to 7/2007 if not reapeat the update driver part. It will then pull the information from your hard drive and the driver will be installed. It takes like 4 seconds to do this... then restart your system and all the problems have been fixed... this works with quicktime in itunes video problems as well as the kodak camera video problems.. I hope this helps it worked great for me..... Good Luck...

I've experienced a similar problem with my mid-2010 MBP freezing when on battery power. I've traced the problem to gfxCardStatus switching the GPU to the Intel HD when there are still dependencies for the NVIDIA 330. I stopped using the application and seems to have solved the problem.
I agree that the problem is prevelant on Lion and didn't occur in Snow Leopard. Your advice to turn off the AGS feature in Energy Saver is a smart one, at least until engineering at Apple resolves this problem, since both gfxCardStatus and AGS are doing the same graphics card switching without reference to actual need of the running apps.

Problem with Sat Nav

Hi there, I am experiencing some problems when trying to use my Sat Nav on my Curve. When I start up the application, it opens for a few seconds then pops up with a message saying 'A network error has occured, please try again later. If this problem persists, please check your network settings or contact customer support.' What should my network settings be, and how do I change them? I don't think I touched the settings for that, since getting the phone.
Any help greatly appreciated!
Thanks
Tom

@MaryP
Welcome to the forum!
As well as OVI Maps application needing to be set "Offline" within application > Spanner icon > Internet > Connection, you would need to go to Menu > Settings > Application settings > Positioning > Positioning methods - only enable Integrated GPS positioning method for no data cost although implication for satellite lock on if not utilising Assisted GPS feature with network access.
You may find that you need to go outdoors away from tall buildings for 20 - 30 minutes to establish first positional fix.
If you are not running OVI Maps v3.06 11wk10 check "?" icon within application > About Maps > Versions you may need to upgrade either via SW Update or OVI Store on device, via OVI Suite > Tools > Software updates on PC or directly from here:http://europe.nokia.com/support/product-support/maps-support/compatibility-and-download#/nokia-n8-00...
If your N8 is not already updated to PR1.2 check by keying in *#0000# on dialler you could find that device still running OVI Maps v3.04, in which case you would be told that existing map data on mass memory has to be deleted and replaced when OVI Maps application updated.
Happy to have helped forum with a Support Ratio = 42.5

Sometimes cannot start PC: problem with Hitachi SATA Hard drive and K7N2G-ILSR

I have major problem with my 160Gb SATA Hitachi hard drive and my MSI K7N2G-ILSR motherboard. Sometimes the PC can be started, sometimes it cannot.
After I installed a clean build of Windows XP Pro SP1 onto my new hard drive (as the only hard drive in my PC) and install all the necessary drivers, the system runs smoothly. However, after about 2 to 3 weeks, sometimes when I start the PC, it cannot detect the hard drive and hence it claimes that it cannot find any VMI Pool Data (i.e. no OS detected). What makes it really horrible is that, it is like the lottery everytime when I start the PC. Sometimes it works, sometimes it doesn't. The highest record was 8 consecutive failures (by resetting or by turning the power off and on again) before I can start the machine properly. Also, the system sometimes just crashes in the middle of operating.
I have already sent the hard drive back to Hitachi. Got the same model of hard drive back as replacement, but the replacement has the same problem, except with the replacement drive the PC can be started eventually after many tries, while with the previous drive it is possible that the PC cannot be started until after a few days later.
Also, it seems that my drive can detect either SATA hard drive or PATA hard drive, but not both. (If I leave my old PATA drive connect in the primary IDE channel, Windows cannot detect the new SATA drive.)
Is my motherboard faulty? Can it only use PATA drive?
My PC's spec is as follows:
AMD Athlon XP 2500+
512Mb PC3200 SDRAM (set to run at 166MHz)
Hitachi 160Gb SATA Hard drive on 1st SATA channel (Model #HDS722516VLSA80)
Sony DVD+-RW drive and Panasonic DVD-ROM drive on secondary IDE channel
Use onboard video (GeForce MX)
US Robotech V92 internal PCI modem
SoundBlaster Audigy 2 Player soundcard
Onboard audio disabled
300W PSU
OS is Windows XP Pro SP1 (with all latest security patches up to date)

Quote
Originally posted by Raven_
Quote
Originally posted by boucher91
Along the same lines the sata drives use more power than the pata drives...
sata usually faster spin rate, pata is slower spin rate...
that is not entirly correct.
many harddrives just come with different ways to connect them.
the only sata drives i now that spins faster is western digital raptors 10k rpm.
all other is running at 7200rpm.
older drives run at 5400rpm
Yes to get the full benefit of RAID, the Raptors are the way to go.Anything else, no significant difference.

Pm8pm-v with awardbios 3.3 and SATA 400gb hdd problems

Hi, I have a problem with my pm8pm-v mother board.
When I plug the SATA hdd, in the bios setup only recognize 150GB, the hdd have 400gb. I updated the bios, I have windows XP sp2, I use the western digital data tools and nothing works.
In fact the western digital made a registry change to enable the "large hdd compatibility" but didn't work.
The mother board isn't compatible with larger hdd? or there is a solution that doesn't imply changing the mother board? thanks.
Motherboard: pm8pm-v
CPU: Pentium 4HT 3.0
Memory Size: 1.5gb
Video Card: Nvidia 7600gs 512mb
Hdd1: Maxtor IDE 120gb
Hdd2: Western Digital 400gb SATA I
EXCUSE MY ENGLISH! I HOPE YOU CAN UNDERSTANDME

oh sorry, I forgot that, its a western digital: WD4000YR
Product Specification:
Data transfer rate - buffer to host (SD and YR) 1.5 Gb/s
Data transfer rate - buffer to host (YS, AYYS, ABYS) 3.0 Gb/s
Data transfer rate - buffer to disk (SD and YR) 65 MB/s sustained
Data transfer rate - buffer to disk (YS, AYYS, ABYS) 85 MB/s sustained
Average read seek (SD and YR) 8.7 ms (average)
Average read seek (YS, AYYS, ABYS) 8.9 ms (average)
Track-to-track seek 2.0 ms (average)
Full stroke read seek (on reads and writes) 21 ms (average)
Average latency 4.2 ms nominal
Rotational speed 7200 RPM
Read cache Adaptive
Write cache Yes
Buffer 8 MB (SD) and 16MB (YR and YS, AYYS, ABYS)
Drive ready time 17 sec. (average)
Master/slave support Yes
IORDY support Yes
LBA support Yes
Error rate (non-recoverable) <1 in 1014 bits read
Warranty 5-year
Thats from western digital web page. Thanks

Problem with JMicron 2x 3.5" SATA HD enclosure - JBOD

Similar Messages

Maybe you are looking for