Lightscribe - System 7 - SATA drive

Why doesn't Lightscribe support System 7 with a SATA DVD?
The few people who have been able to make it work had to modify their registry.

System 7?
Do you mean Mac OS7 or the British band called System 7?
If you mean Windows 7, you might want to check the LightScrribe website for the update to LightScribe .
Best regards,
erico
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Similar Messages

My system won't boot past POST after I plugged in my new SATA drive. (SATA noob

I have a MSI K8n Neo 2 Platinum mobo with a Athlon64 +3500 and 1gig dual channel DDR 400. I currently have 2 drives set up a IDE primary (MAxtor 6Y120) and a IDE slave (Maxtor 6L080).
I recently purchased a Maxtor DiamondMax 10 6L300S0 300GB Serial ATA 7200RPM Hard Drive w/16MB Buffer.
It is my first SATA drive ever so non the less I am a newb. I want to use it as a non Raid media storage device while my primary IDE remains my boot OS drive.
I plugged the SATA in to the sata one port and powered it. I enabled the SATA in the bios with RAID disabled. When the system boots up it does the memory chech and lists all the IDE devices. Then it says "Detecting IDE drives..." and just hangs there. The new drive spins so it definatly has power but occasionaly it make occasional clicking sounds.
Once it actually booted up and windows detected it. I decided to reboot it just to play it safe but it never would get past post screen again. I can boot up the system normally when I unplug the SATA cable.
Please help I need to know if I am doing something wrong or I should RMA the drive. THANK YOU!

Got the same problem:
pata Maxtor Diamond Max =9 200 (40/160) Boot drive
AMD 64 x2 3800
Bios 1.2 090905 using MSi online auto update utility
2x 512 DDR double sided
X850 pro 128mb
PSU Sweetex 650w
Switched power supply
110/220 V switchable (220 V: 5 Amp/ 110V:10 Amp)
+ 3.3 V 28 Amp
+ 5 V 45 Amp
+ 12 V 25 Amp
-5 V 0.5 Amp
-12 V 0.8 Amp
- 5 Vsb 2 Amp PEAK 2.5
Max. 650 Watt
CE, FC
Boots perfectly with 1 pata, adda sata to sata 1 or 2 or 3 or 4
Boot stalls in bios at Raid setup. Tried enable raid with no drives enable , system booted twice, turned off overnight, then failed to start the next day. Will only restart with a cold reboot. Hot reboot produces a long BEEEEEP & power is on but nothing happens no post nothing.
SATA drive was taked from a working system (ECS 755a - AMD 64 3000 - PATA 200 / SATA 200), configured 40/160 40=OS Winxp 64 / 160 = data. System will not boot if this is the sole drive connected.

SATA DRIVES NOT SHOWING IN SYSTEM PROFILER

Hi.
Thanks for reading this.
I found out that my SATA drives do not appear in my System Profiler.
I am running OS 10.4.7 on a PowerMAC G4 Dual Gig 2002 Quicksilver with
3 hard drives:
- TWO 250 GB SATA Drives (Both partitioned into 3 sections: 132 GB which is my MAIN drive, 90 GB which is used to back up music, and 53 GB which is used to hold finished work. The other drive is partitioned into 3 sections: 60 GB which is a back up of my MAIN drive, 126 GB which I record music to, and 58 GB which I use for Photoshop/Video finished work.) The SATA drives are connected via PCI card (described below)
- ONE 80 GB ATA Drive (Partitioned into 2 sections: 20 GB which has back up OS and 60 GB which holds my iTunes library.)
Here is what System Profile shows me:
Hardware Overview:
Machine Name: Power Mac G4
Machine Model: PowerMac3,5
CPU Type: PowerPC G4 (2.1)
Number Of CPUs: 2
CPU Speed: 1 GHz
L2 Cache (per CPU): 256 KB
L3 Cache (per CPU): 2 MB
Memory: 1.5 GB
Bus Speed: 133 MHz
Boot ROM Version: 4.3.3f2
Serial Number: XB2081EAM8H
Sales Order Number: M8667LL/A
ATA:
ST380021A:
Capacity: 74.53 GB
Model: ST380021A
Revision: 5.05
Serial Number: 3HV0XMWA
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Protocol: ATA
Unit Number: 0
Socket Type: Internal
OS9 Drivers: Yes
S.M.A.R.T. status: Not Supported
Volumes:
ATA Drive:
Capacity: 15 GB
Available: 5.51 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s11
Mount Point: /Volumes/ATA Drive
iTunes:
Capacity: 59.4 GB
Available: 682.29 MB
Writable: Yes
File System: HFS+
BSD Name: disk0s12
Mount Point: /Volumes/iTunes
PCI Cards:
SeriTek/1V2E2 v.5.1.1,03/14/05, 23:42:20:
Name: Seri-Tek1V2E2
Type: ata
Bus: PCI
Slot: SLOT-3
Vendor ID: 0x8086
Device ID: 0x3200
Subsystem Vendor ID: 0x8086
Subsystem ID: 0x3200
ROM Revision: 5.1.1.1V2E2
Revision ID: 0x0000
Is this normal?
Is there a way to fix it?
I have noticed some strangeness while using Safari lately, could there be a connection?
PLEASE respond as if you are explaining this all to a COMPLETE idiot.
(Meaning technical jargon with abbreviated terms can cause confusion, just please give a descriptive response?)
Thanks!
And when I click on Serial-ATA I get:
No information found.
PowerMAC G4(2002 Quicksilver) Mac OS X (10.4.7) 2 Seagate SATA 250GB drives, 80 GB Seagate ATA drive, Digital Performer 4.6

Hi Tommy,
you could try reseting your PRAM to see if that makes any difference, as this holds your systems parameters. You shouldn't hurt your Mac by resetting them.
To reset PRAM hold down AppleAlt+PR on startup until it chimes 3 to 5 times then release.
Also...
Let the Mac boot after a PRAM reset then restart to reset your Open Firmware which may also help. At Startup hold AppleAlt+OF then type at the light grey screen (all without speech marks) "reset-nvram" then press return key. Then type "rest-all" then press return key again. Then type "mac-boot" press return to exit.
These command may help you they may not, but they shouldn't hinder you in any way. But if you are in any doubt about these commands by all means research them further on the Apple website or just ask for a second opinion.
Regards.
Rory

SATA driver flooding System.log, filling up startup disk

My system.log seems to be filling up with SATA error messages, about 10 per second. The log is now so large that I can't even get the Console app to open it (only in Open Quick, which seems to show little snippets of the log only).
This seems to have started when I installed an Initio 1623 SATA controller as part of a GraniteDigital drive upgrade. The controller worked, the drives worked. I've since pulled the controller card, but it seems the driver continues to flood the log file!
The drivers for the controller are apparently built in to OSX (at least in 10.4.7...) so there is no way to update the driver separately.
Restarting the machine hasn't helped. For now, I have to keep moving files to other disks to keep this G5 functioning.
How can I A) delete the log file to gain some time?
B) make this error stop?
Thanks.

Well - maybe it isn't a SATA driver system.log. I can't read the system.log because it keeps refreshing so the data in on the screen for less than a second before it refreshes. AND there is so much disk thashing that the system is barely responsive.
The only visible log entries are:
Jul 19 04:28:10 Platinum kernel[0]: Inic1622: SATA - Int no command active (repeated about ten times)
Jul 19 04:28:10 Platinum kernel[0]: and active
and repeat....
The log file is showing a size of 4.5 GB

SATA drive no longer boots

The PC was running fine for about two weeks with a single 160GB SATA drive.
One morning, with no hardware changes, the PC refused to boot. A blue screen of death flashed very quickly past as the PC rebooted. Windows suggested safe mode, and when I booted into safe mode the PC stopped loading drivers immediately after mup.sys. I've had this problem before with mup.sys on other PCs (I believe the real problem is the ACPI driver loaded immediately after mup.sys). In any case the solution is usually to remove any hardware or, in the worst case, re-install XP.
Running windows XP setup from CD it will no longer re-install onto the SATA hard drive. Even the recovery console will not work, claiming there is a problem with the drive. I know that the drive is not dead, because it gets as far as trying to install the ACPI driver.
Install a ATA HDD, installing XP on to it. Ran SP1 and all the updates. The ATA HDD worked OK until I plugged in the SATA HDD, which caused the new version of XP to hang at the mup.sys driver again. Disabled the SATA controller, and then everything works again. Ran all the updates for the motherboard and BIOS but that did not help. Switched SATA cables but did not help. Tried the SATA RAID controller but that did not make any difference. Variously tried disabling everything I could in the BIOS setup but that made no difference.
Now, I know that my no-name RAM might be a bit dodgy, and the PSU a little wimpy, but the PC works fine as long as the SATA HDD is either disabled or not plugged in. It actually ran perfectly for two weeks, and I was surprised how cool the CPU runs.
I looks like the next step is to try another SATA HDD, then PSU, then motherboard, but is there anything else which might help my situation before I go out and buy those items?

Well, it turns out it was the SATA HDD, and it seems to be repaired.
The method was to boot Windows XP from another HDD into safe mode and repair the drive. Windows would not boot from the SATA HDD at all, nor run in safe mode. When booted from the other HDD Windows would not access the SATA HDD normally, but would for some reason in safe mode. There must be a difference between the SATA drivers used in safe mode vs regular mode.
CheckDisk found many cross linked files and fixed them (took about an hour) and now the SATA HDD looks like it is working.
How did the file system get damaged? Good question, since I have never seen NTFS get messed up like this. In any case I'm probably going to replace the HDD in case it was the controller.

[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.

Which 1TB (or bigger) SATA drive is the coolest/quietest/least power-hungry

I have a Power Mac G4 Dual 1.25 GHz MDD (it's this model here) which (as it's unmodified) runs very hot & noisy much of the time.
What doesn't help is that I have 3 hard drives installed. 2 of these (including the boot drive) are IDE (80 GB & 120 GB), and are attached to the cables at the front of the machine (am I right in thinking that this is the ATA-66 bus?). The third is a SATA drive (250 GB) connected to one of the sets of cables at the back of the machine (the ATA-100 bus?) via an IDE -> SATA adapter (not a PCI card).
This adapter took me many weeks of research to track down (& order online from the USA) as there didn't appear to be (at the time - a few years ago) anyone here in the UK that made or sold these adapters. (The opposite adapter - IDE drive to SATA cable - was freely available ironically, even in my local electronics shop). The physical size of the adapter means that I can't sit one of the other drives in the empty drive bay at the back of the machine.
A few months ago, as I was almost out of hard drive space, I decided to get a new (SATA) drive to replace the existing 3 drives. As well as giving me lots of capacity, one drive is going to use less power than 3, give off much less heat than 3, and hopefully reduce the fan noise.
Incidentally, I've found many good articles on reducing heat/power consumption/noise in MDD Macs - see here, here, here, here & here.
At the time, 1TB was the largest size available. After much research, along with some forum postings - see here & here - I decided to go for the Samsung Spinpoint F1 drive, which is currently quite cheap - see here.
However, I recently discovered that Seagate now makes a 1.5 TB drive, which would obviously be preferable - see here & here although it is much more expensive - see here.
However, there are many reports of problems with the Seagate drive - see here, here & here.
What I'm wondering is if there are any drives that are bigger than 1TB apart from the Seagate?
If not, would people recommend that I chance going for the Seagate, and hope that I don't have the problems, or that I'll be able to flash the firmware at some future point to sort the problem if it occurs (I have Virtual PC 7.0.2 installed, running Windows 2000 Service Pack 4 - would this enable internal hard drives to have their firmware updated?) or should I just play safe and go for the Samsung, even though it's "only" 1TB?
The largest capacity money can buy is my primary concern, followed by low power usage, low heat output & low noise.
Many thanks.

Thanks for the info.
I don't really see the point in the expense of a PCI card when the IDE -> SATA adaptor works fine, and if I bought a PCI card, I'd then feel obliged to go through the hassle of selling the adaptor on eBay to try to recoup part of the cost of the PCI card.
I should have mentioned before that I want to format my new drive as a single partition, in Mac OS Extended (Journaled) format, and to boot from it. I only want the new drive in the Mac - I don't want any other drives in there. Apart from increased capacity & performance, and reduced power consumption, heat & noise - the main point of getting the new drive is so that there is only one drive in my Mac. Having more than one is a complete pain for me.
At the moment, despite having "Put the hard disk(s) to sleep when possible" unchecked in the Energy Saver pane of System Preferences, all 3 drives spin down very soon after they stop being accessed, which means an infuriating delay (& spinning beach ball) when they spin up again. One or more of them spinning up even interrupts music playing sometimes, and when I go to shut down the computer, if they are spun down but mounted on the desktop, they spin up again before they spin down as part of the shutdown procedure! Also, with more than one drive, I can't tell which drive a file/folder is on just by looking at it, if it's on the desktop.
As far as Other World Computing goes, they may ship to the UK, but by the time the international shipping charges are added, I very much doubt if the total cost of a new drive would work out cheaper than ordering from a UK supplier & getting free shipping.
Another potential problem I've discovered with the Seagate drive is actually a quote from the Other World Computing website that's reproduced in comment number 66 (on page 3) of the MacRumors Forums thread that I gave the link to in my initial post. Basically it says that if you format the Seagate drive as a single partition on a Mac, the performance isn't acceptable. It's apparently fine though if it's partitioned in 2 equal size volumes, or if you format it as an NTFS or FAT32 drive. Neither of these work-arounds are any use to me though.
Everything so far suggests that I should just go for the Samsung 1 TB drive, but I'm hesitant to do so until it's confirmed to me that there aren't any other drives out there that are bigger than 1 TB apart from the Seagate, and also, knowing my luck, the day after I buy the Samsung, Western Digital or Hitachi or someone will bring out a flawless 1.5 TB drive for not a lot more money, and I'll be kicking myself for ending up with only 2 thirds of the capacity than I could have had...

How to connect a SATA Drive in a G4 MDD Desktop Mac?

Due to much more needed harddisk space for music production on my G4 1.25 GHz Dual PC, I ordered and just received a SATA 500 GB internal Harddiskdrive.
Under "About This Mac" in the System Profiler I get a list of all my internally already connected ATA Drives. But there is also a (empty) category available, named "Serial-ATA" which I strongly assume stands for SATA. I further think once such a category is existing I should be able to connect a SATA drive.
Now:
1. Can I connect the new SATA HD internally in my Dual G4 or must I use the Drive as an external Firewire Drive (of course in a special housing)?
2. If it is possible to built in a SATA drive, must I buy an adapter in any form, because the interface on the SATA drive is different from the cable endings in my Mac?
3. If so, what is such an Adapter be called (from Inerface A name to Interface B name) and do I get it at an electronic store?
4. Is there anything crucial I do need to know regarding this matter (maybe voltage compatibility, adjustments on SATA drive or in my Macintosh G4, etc.)?
5. And if it should not be possible to use the HD internally (as in question 1.), are there housings with Firewire 800 connectors available for SATA drives which I can use?
I would be very glad for your specialist help! Thank you!
Steve
G4 1.25 GHz Dual PowerPC 1 MB L3 cache processor · 1.25 GB DDR SDRAM · Mac OS X (10.4.8) · 19" CRT ƒAQTOR 19+ Monitior · AD/DA Converter MOTU Traveler

Thank you all (Malcolm Rayfield · The hatter · Rodney Culling) so very much. I thought I would be lost and stuck - on contrary I got your huge help.
Unfortunately I bought already the SATA 7200.10 and it had been delivered. But I am very happy to hear that there are PCI SATA cards available and I preferably would like this solution to have the Drive as an internal drive. It is for me easier to tame the noise not having an additional drive in my Mini recording studio.
I will investigate into the prices of those cards and only do hope that the price for such PCI SATA cards are not to expensive otherwise my bread deliverer (boss) will refuse. He was already not excited to hear I ordered a SATA drive but there was no ATA anymore available at my usual source and if I later upgrade to a G5 I can take the drive with me. I only will have then the reverse situation using some of my older ATA drives in a new G5.
Thanks a million again for your kind and unexpected fast help. Thanks!
Steve
G4 1.25 GHz Dual PowerPC 1 MB L3 cache processor · 1.25 GB DDR SDRAM Mac OS X (10.4.8) · 19" CRT ƒAQTOR 19+ Monitior · AD/DA Converter MOTU Traveler

Do i need to do "something" for my mac mini to see my sata drive?

Hi guys
Problem: After replacing a failing HDD, I have connected a sata cable from inside my mini to an external sata drive and my mini does not recognise my new drive as an internal drive or in disk utility.
Modification: I have removed my failing internal 320 gb HDD and am presently booting up via an external USB drive. I have modified a sata to esata cable so that it fits the internal sata connection of the mini. ( i have carefully cut excess plastic off the sides of one end, so that it fits into the connection. ) I have a 1.5tb sata drive inside an external sata/firewire/usb enclosure. The drive has been mac formatted on another machine, with 3 partitions (boot, back up & media)
Tests: In disk utility, i can not view my sata connected drive. However, when i connect the drive via firewire or usb, the drive is recognised and all 3 partitions show up. Disk Utlity shows that this connection is made via USB/Firewire.
System Info: 2008 Mac Mini 2ghz with 2gig Ram. Did have a 320gb internal Drive, but it crashed. Replacing it with a western digital 1.5tb sata hard drive. The enclosure is a standard non branded silver enclosure. There is no physical switch on the enclosure that controls the connection type. The cable is a regular sata to esata cable.
Do i need to do anything for my mini to recognise this new drive?
Thanks for reading

After re-watching the Youtube clip that i followed, i think i have modified the wrong cable.
The cable that i modified is this sata to esata cable
The cable on the YouTube clip looks like the metal connectors are like a series of long rectangles. As does the connector on the broken hard drive that i have. The cable i am using, the metal connector points are a series of small dots/balls at the ends.
The Youtube clip makes his own sata enclosure, where as i am using an enclosure that already has the connections.
Can anybody advise what connectors then, i should use, if i am using the wrong one.
Thanks alot

Upgrade SATA drive for macbook late 2008

Hello!!
I am here to ask for help. Let me tell you a bit more about my Mac:
Late 2008 silver 13" MacBook 250GB 2GB RAM 2.4GHz IntelCore2Duo DDR3 MB467LL/A, currently at 10.5.8 OSx system (yes I know I need to update the software as well!)
I currently bought 4GB kit (2x2GB) RAM to upgrade on my silver MacBook (late 2008), and would also like to update my hard drive.
I have looked around on online shops for 2.5" 9mm SATA drive, and came across to 1TB for not too bad a price (between £85 to £100).
Anyone know whether if this is ok for my laptop?
Samsung, WD Scorpio Blue and Toshiba, all are at 5400rpm for 1TB. (However there is 750GB Seagate 7200rpm 16MB - recommended???)
Large memory/drive are usually much needed with me as I do use a lot of design work e.g. Adobe InDesign/Illustrator/Photoshop...you get the drift .
Any advice would be much appreciated!
Looking forward to hear from you soon!
Thanks again,
ejburton.

If all the technical specs (like SATA, physical dimensions, power usage etc) all match then you can use any drive of any available size in your MBP. Right now it appears that the largest available is the Western Digital 250GB 5400rpm drive where as the fastest is the Hitachi 200GB 7200rpm drive. Fujitsu and Toshiba have annonce 300GB drives though I've not heard that either are yet shipping.
I have to say that I'm very pleased with the Hitachi 200GB 7200rpm drive.

Mac Pro Compatibility With Older SATA Drives And DVI Connectors

I soon plan to replace my 5 year old G5 with a new Mac Pro and need two questions answered so that I will know what options i have for the transfer of older data and apps. The Apple web site for the Mac Pro includes the following paragraph which gives me reason for concern:
Your Mac Pro includes four drive bays, allowing you to configure it with
up to 8 terabytes of storage using 7200-rpm Serial ATA 3Gb/s drives, up
to 2 terabytes of storage using high-performance solid-state drives, or
any combination of each type of drive. Configure each drive bay
separately.
Does the phrase "using 7200-rpm Serial ATA 3Gb/s drives" mean that the Mac Pro will ONLY work with 3Gb/s drives or that it performs best with 3Gb/s drives?
I currently have two internal SATA 250/300 GB Maxtors (Maxtor 7Y250M0 and Maxtor 6B300S0... both are 7200 RPM but I don't know the data transfer speed). Ideally I would get a Mac Pro with a single 1 TB drive, move one or both of these older SATA drives to the new computer, one temporarily and the other permanently in order to transfer data and Apps to the new machine. If this is not possible then the new machine will need to wait until after I get a new larger FW external drive to use as a data transfer medium (I had planned to do that anyhow). I need to do some advance planning for this so I need to know what to expect in advance. I noticed this possible wording ambiguity on Apple's description of the Mac Pro long ago, but now I need to find out the answer for sure. Apple, you need to be more specific with your words.
Can anybody answer this question for me?
My second question regards display connectors. Does the standard (no bucks added) display card include a standard DVI connector or only the newer Mini-DVI connectors. I think I see a standard DVI connector in the low res picture of the back of the Mac Pro but am unsure. My 5 year old Apple display bit the dust a year ago and I had to replace it with an HP 2009m display (mumble grumble) which does use a standard DVI connector. A new Apple display is too rich for my blood so I plan to continue using the HP display for now and need to find out if I will need a display adapter to go with it.
Many thanks to anyone who can answer these questions authoritatively.
For anyone who asks why I still run 10.3.9 on my G5, I can only answer response speed. New OS versions always act like a lead anchor on a machine with their added overhead and Tiger really does feel like a ball and chain tied to me... it just does not reaspond as fast as I do. I look forward to the speed of a new machine.
Phil Rogers
--

Does the phrase "using 7200-rpm Serial ATA 3Gb/s drives" mean that the Mac Pro will ONLY work with 3Gb/s drives or that it performs best with 3Gb/s drives?
Any commercial sATA drive will do just fine. 7200 RPM is not a requirement.
WD "Green" drives have caused user complaints about "long delay until ready" when installed inside a Mac Pro, but are fine for backups.
You are making the leap from PowerPC to Intel Mac. Eventually, you should re-initialize your old drives to GUID partition table for best responsiveness.
Migrating your System will not be possible. Use the pre-installed System or Install a new System on a GUID-partitioned drive with the release DVD in the box.
Migrating your Applications is a Bad Idea. You should plan on re-installing all your third-party Applications from their release discs.

[865PE/G Neo2 Series] Just got my first SATA drive.. need help booting up.. :(

Hey guys
I just got my very first SATA drive. it's a Hitachi 160GB 7k250!
anyway, I wanted to set this new drive (partion 1 to be exact) as my PRIMARY or what I like to call SYSTEM drive.. this is where i store only my windows core files and program files..
My previous setup is that I have 2 PATA drives (Primary master and Secondary Master) and 2 DVD drives (Primary Slave and Secondary Slave)..
Now with the introduction of this new SATA drive, well, i didnt know what to do..
I got as far as setting my BIOS to: (forgive me if the following isnt exact terms as in the bios)
ATA = PATA Channel only
keep SATA = YES
(and some settings i can't remember)
I was able to boot my computer up with the SATA HD partitions set at the next available drive letters.
Now here's the problem.. I currently have an Image of my C: (system) created with Acronis TrueImage 8, and i restored that to my SATA drive's FIRST partition...
The first partition is also formatted with the same file system NTFS and is set to primary..
From here, i honestly dont know what to do..
ofcourse I will have to set bios to boot the SATA drive first...
Also, since the System image (windows XP) is that of DRIVE C: I have to somehow set the SATA drive to be HD0 (first channel)... playing around in my bios I have accomplised to have set my SATA drive as IDE channel 1 = Primary.. funny thing is the rest of the drives moved down starting at IDE Channel 3 and 4..
Still i went on to boot up.. but i was unsuccessfull. I get a very quick blue screen (about 50 miliseconds) and then my computer shuts off and reboots..
I played around witht he settings and tried many things.. still get the quick BSOD and then reboot problem
GUys? What am i missing here?
I didnt know this SATA drive was gona get complicated.. i thought i'd be up and running by now.. :( ..
Please lend me some of your knowledge peoplez.. :D
tea

Hi Danny,
Thanks for your reply.
I have followed your instructions to the dot.. now im getting as far as the WindowsXP Boot Screen... after an unusually long loading time, i get that BSOD flash which i really cant make out since the darn thing reboots right away.. :(
I also tried
Native Mode
ATA Configuration - SATA only
(changing this to SATA, thinking you were mistaken since am booting sata up.. but what do i know ei?)
SATA Keep enabled - yes
PATA Keep enabled - yes
PATA channel selection - both
same results... a long boot screen loading time.. then a quick BSOD..
I alsto tried booting up in safemode.. the loading stops at agp440.sys and reboots after a long pause at that part.
So now I switched back to your recommended settings, but this time setting my old hard drive to boot (PATA).
To my surprise im back to where i started (despite maintaining your suggested settings) thus i am replying to this post again..
also, i noticed that with your suggested settings, my SATA drive is on IDE channel 1.. and the rest on IDE channel 3 and 4.. but here in windows my old hard drive is still drive C:.. I was expecting my SATA drive to be Drive C this time.. could this be the problem here?
I mean the windows Image I restored is setup to work on drive C (first drive), although I removed all the drive, could it be that my SATA drive is still not on drive C?
Please help. My brain's bleeding
Tea

Need Sata Driver to connect my external hard drive?

Hi
I have an hp eliteworkbook 8540w with windows 7 on it. I made a backup of my computer witht he windows 7 backup software and put it on an external drive. When I try to restore the entire computer with that backup I must use the system repair disk to get to the option to restore my computer.
However it will not recongize my external drive and thus I cannot get to the image. My drive does connect through a usb cable but I am wondering if I need some sata driver as well.

ehm, i have like the same problem, and trying diffrent USB locations does'nt solve anything, instead the external hard drive will not run under the drivers of the other USB locations then windows gave it. but everyone can solve their problems by watching a trial on youtube or follow one one some blog/forum. only...i don't ever get the blue disk thingy in device maneger, what really sucks, i need to format this drive, but how? anyone got to tell me a diffrent way, diskpart does'nt work, diffrent letter theory does'nt work, diffrent USB location does'nt work, i cannot find drivers that can run this device, even thought i don't know anymore then ''sata portable HDD device''

Memory errors after Array is created SATA drive

Hello,
I am trying to setup a 655 Max board with a SATA drive. Once I define an array, I get Memory errors. I am testing this using the Microsoft memory dest boot CD. As soon as I delete the array from the drive, the memory test is able to work sucessfully. I am using FASTtrack with a promise 376 driver.
Brian

I have been searching the forum for links between raid array's and memory issues. I noticed some people that have random stop errors when loading xp (which is what I was also seeing).
Why would the promise (raid controller) have an effect on the system (ram) like that? I noticed as I ran the Microsoft memory test, it would start to get all garbled on the screen and every once in a while information would show up from the fast track screen. Hmmmm....

MS-7008 SATA drives not visible

Hi,
My MS-7008 ATX Mainboard has:
Supports Intel® P4 Northwood/Prescott (Socket 478) processor.
VIA® PT880 chipset
VIA® VT8237 chipset
- High Bandwidth V-link Client controller
- Integrated Faster Ethernet LPC
- Integrated Hardware Sound Blaster/Direct Sound AC97 audio
- Ultra DMA 66/100/133 master mode PCI EIDE controller
- ACPI
- Supports Serial ATA
- Supports USB2.0
Have been funning this motherboard for many years without problems. Until now, when I decided to use SATA drives in addition. Bought Samsung 1 TB (HD103UJ model) drive, connected to MB and fired up my W2K3 system.
To my large dissapointment drives did not show up in the list of available disks. I am looking under Computer Management - Disk Management. Device Manager shows some error under SCSI and RAID Controllers - VIA RAID Conntroller 3149 ... It has this yellow sign with "!" in it. Understand that driver for SATA migh be missing. Since that point I have been to tones of pages on web reading and searching, but after two days still no luck... Tried MSI page, VIA (producer of southbridge chipset) page, tried out many drivers I could find there, but still same message. On the other hand, those are not listed in computer start up post messages either. I checked all settings in BIOS, found only one regarding SATA and there it says enabled.
The only thing I did not check out yet is to play with HDD jumpers. Somewhere I read that by limiting speed of HDD one can make them appear. But I do not have jumper avalable and HDD manual is very unclear, not sure if I can do that even if I had jumper. Have only 4 pins ( two sets times two pins) so it is only 4 possible combinations, will try as soon as I get some pins.
Anybody else have any other idea??? Really painfull to search for something that should just work in "plug & play" mode

Unfortunatelly Disk Management does not show that disk. I am quite sure this has to do with finding right drivers. Furthermore, I hope that these drivers can be installed now, after system has been installed. I believe SATA drivers need to be installed during system installation only if SATA drive is the one where you install the system. In my case, this drive will only be used as data drive, so hopefully I can find the right driver and install it now. Pleaes note, that BIOS identifies SATA 1 driver (I temporarely connected another SATA drive that I had). The only problem is, I can not find the driver.... One possible reason could be that my system "windows Server 2003 X86 is not supported"... That would be dissapointing :( I have looked through MSI page as well as VIA support and tried many possible drives (I go into device manager and select SATA driver that is currently with yellow warning sign, right click it and do update, then select the new downloaded driver, but system does not accept it).
I also tried to uninstall existing drive completely, and then do "search for hardware changes". This finds new device and places it not under unidentified devices without driver. It places into SCSI and RAID controllers group and call device something that ends 3149 ... VIA chip used on my board is 8237, so again, kind of weired number that Windows automatically assigns to new device. But again, it does not allow me to change the driver to any of the downloaded ones, saying that it is not newer driver than the one currently installed....

Lightscribe - System 7 - SATA drive

Similar Messages

Maybe you are looking for