So I put a SSD in my core2 system (p5n32-e sli, e6700, radeon 6770), windows installed properly. Then during slackware installation, it would stop after all the packages were installed with an IO error. Next attempt it finally installed during the boot it gave many of these errors and finally booted.
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0xb [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
07 1b bc 00
sd 0:0:0:0: [sda]
ASC=0x47 ASCQ=0x0
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 07 1b bc 00 00 01 00 00
end_request: I/O error, dev sda, sector 119258112
Xwindows locked after a few minutes and next boot there were more errors and fsck changed the filesystem during its check and rebooted, then I got a kernel panic with VFS root not found. After that it appeared as though massive corruption happened as I couldn't get in with a boot disk, or when I put my HDD back in, booted from that and tried to mount the SSD it gave an IO error.
Here's a thread I started, came to the conclusion the problem is with the motherboard probably the south bridge. Ignore how I thought it was a problem with the fixed disk in the first few posts, apparently that was caused by the southbridge / SSD conflict http://www.linuxquestions.org/questions/linux-hardware-18/io-errors-with-new-hard-disk-4175424822/ the fixed disk worked fine after I took out the SSD. System works fine on HDD's, but the same corruption happens ever time when I use linux. Windows boots fine every time for some odd reason.
So my question is, has anyone encountered corruption with windows or linux and the Nforce 680i south bridge, or the p5n32e-sli? I tried a pci sata controller card with the SSD and got the same errors as when it was plugged into the southbridge connectors.
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0xb [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
07 1b bc 00
sd 0:0:0:0: [sda]
ASC=0x47 ASCQ=0x0
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 07 1b bc 00 00 01 00 00
end_request: I/O error, dev sda, sector 119258112
Xwindows locked after a few minutes and next boot there were more errors and fsck changed the filesystem during its check and rebooted, then I got a kernel panic with VFS root not found. After that it appeared as though massive corruption happened as I couldn't get in with a boot disk, or when I put my HDD back in, booted from that and tried to mount the SSD it gave an IO error.
Here's a thread I started, came to the conclusion the problem is with the motherboard probably the south bridge. Ignore how I thought it was a problem with the fixed disk in the first few posts, apparently that was caused by the southbridge / SSD conflict http://www.linuxquestions.org/questions/linux-hardware-18/io-errors-with-new-hard-disk-4175424822/ the fixed disk worked fine after I took out the SSD. System works fine on HDD's, but the same corruption happens ever time when I use linux. Windows boots fine every time for some odd reason.
So my question is, has anyone encountered corruption with windows or linux and the Nforce 680i south bridge, or the p5n32e-sli? I tried a pci sata controller card with the SSD and got the same errors as when it was plugged into the southbridge connectors.
Facebook
Twitter