Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[solved: bad SATA cable] freezing system - mainboard broken?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
as.gentoo
Guru
Guru


Joined: 07 Aug 2004
Posts: 319

PostPosted: Mon Aug 10, 2015 7:06 pm    Post subject: [solved: bad SATA cable] freezing system - mainboard broken? Reply with quote

Hello,

I hope this is the right forum to post to.

I had freezing PC once or twice in the past month. I couldn't fine anything in the log file since it - probably - froze on disk access. It actually happened when I tried to access a (local) virtual machine.
In the past weekend I could first login to KDE. Then there was some messages that the system couldn't write to the disk and eventually that the HDD wasn't recognised anymore. It looked like the disk broke. I quickly shut down the system to prevent further damage. :?

I tested RAM with memtest for five rounds but there was no error. I tested the HDD using 'smartctl -t long /dev/sdX' and a few times with ViVard, no error.
I cloned the disk with dd then. When I tried to boot it didn't even get so far to present the login screen anymore.
Next was connecting the disk to a differen controller. Since that everything is ok - probably just yet...

When I'm right, the big problem is, that the faulty controller is the mainboard chipset. Probably more won't work soon. But I want to be sure because a new mainboard means new RAM and a new CPU. I won't buy the newest hardware - even so I have to count with a sum of at least 800€.

So the disk is ok, RAM is ok, CPU seems ok as well. Can't be the kernel since I'm using it right now. In case it's not the board, what else remains?

Your help would be appreciated.






I found something in the log from August 3 and 4. Maybe you can read something out of that.

Aug 03 11:49:34 [kernel] [121817.910534] xhci_hcd 0000:09:00.0: Finished xhci_init
Aug 03 11:49:34 [kernel] [121817.910535] xhci_hcd 0000:09:00.0: Start the primary HCD
Aug 03 11:49:34 [kernel] [121817.910536] xhci_hcd 0000:09:00.0: xhci_run
Aug 03 11:49:34 [kernel] [121817.910538] xhci_hcd 0000:09:00.0: Failed to enable MSI-X
Aug 03 11:49:34 [kernel] [121817.910585] xhci_hcd 0000:09:00.0: irq 61 for MSI/MSI-X
Aug 03 11:49:34 [kernel] [121817.910624] xhci_hcd 0000:09:00.0: Command ring memory map follows:

Aug 04 03:17:21 [kernel] [167111.251607] sr 15:0:0:0: [sr0] CDB:
Aug 04 03:17:21 [kernel] [167111.251609] Read(10): 28 00 00 00 03 32 00 00 01 00
Aug 04 03:17:21 [kernel] [167111.251615] ata16.00: cmd a0/00:00:00:00:08/00:00:00:00:00/a0 tag 0 pio 2048 in
Aug 04 03:17:21 [kernel] [167111.251615] res 40/00:03:00:14:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Aug 04 03:17:21 [kernel] [167111.251617] ata16.00: status: { DRDY }
Aug 04 03:17:21 [kernel] [167111.251620] ata16: hard resetting link
Aug 04 03:17:21 [kernel] [167111.712032] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug 04 03:17:21 [kernel] [167111.718931] ata16.00: configured for PIO0
Aug 04 03:17:21 [kernel] [167111.721950] ata16: EH complete
Aug 04 03:17:29 [kernel] [167119.259076] ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Aug 04 03:17:29 [kernel] [167119.259082] sr 15:0:0:0: [sr0] CDB:
Aug 04 03:17:29 [kernel] [167119.259084] Read(10): 28 00 00 00 03 32 00 00 01 00
Aug 04 03:17:29 [kernel] [167119.259093] ata16.00: cmd a0/00:00:00:00:08/00:00:00:00:00/a0 tag 0 pio 2048 in
Aug 04 03:17:29 [kernel] [167119.259093] res 40/00:03:00:14:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Aug 04 03:17:29 [kernel] [167119.259095] ata16.00: status: { DRDY }
Aug 04 03:17:29 [kernel] [167119.259099] ata16: hard resetting link
Aug 04 03:17:29 [kernel] [167119.719516] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug 04 03:17:29 [kernel] [167119.726179] ata16.00: configured for PIO0
Aug 04 03:17:29 [kernel] [167119.729196] ata16: EH complete
Aug 04 03:17:37 [kernel] [167127.266562] ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Aug 04 03:17:37 [kernel] [167127.266569] sr 15:0:0:0: [sr0] CDB:
Aug 04 03:17:37 [kernel] [167127.266570] Read(10): 28 00 00 00 03 32 00 00 01 00
Aug 04 03:17:37 [kernel] [167127.266579] ata16.00: cmd a0/00:00:00:00:08/00:00:00:00:00/a0 tag 0 pio 2048 in
Aug 04 03:17:37 [kernel] [167127.266579] res 40/00:03:00:14:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Aug 04 03:17:37 [kernel] [167127.266582] ata16.00: status: { DRDY }
Aug 04 03:17:37 [kernel] [167127.266585] ata16: hard resetting link
Aug 04 03:17:37 [kernel] [167127.727003] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug 04 03:17:37 [kernel] [167127.733910] ata16.00: configured for PIO0
Aug 04 03:17:37 [kernel] [167127.736928] ata16: EH complete
Aug 04 03:17:45 [kernel] [167135.274048] ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Aug 04 13:06:00 [kernel] [176941.593468] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Aug 04 13:06:00 [kernel] [176941.605501] ata4.00: configured for UDMA/133
Aug 04 13:06:00 [kernel] [176941.616515] sd 3:0:0:0: [sda] Starting disk
Aug 04 13:06:00 [kernel] [176945.518088] ata14.00: qc timeout (cmd 0xa1)
Aug 04 13:06:00 [kernel] [176945.518103] ata8.00: qc timeout (cmd 0xec)
Aug 04 13:06:00 [kernel] [176945.520092] ata7.00: qc timeout (cmd 0xec)
Aug 04 13:06:00 [kernel] [176945.520098] ata14.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aug 04 13:06:00 [kernel] [176945.520098] ata14.00: revalidation failed (errno=-5)
Aug 04 13:06:00 [kernel] [176945.520104] ata8.00: revalidation failed (errno=-5)
Aug 04 13:06:00 [kernel] [176945.522096] ata7.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aug 04 13:06:00 [kernel] [176945.522097] ata7.00: revalidation failed (errno=-5)
Aug 04 13:06:00 [kernel] [176945.827545] ata14: SATA link up <unknown> (SStatus FFFFFF93 SControl 300)
Aug 04 13:06:00 [kernel] [176945.827559] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug 04 13:06:00 [kernel] [176945.827747] ata14.00: configured for UDMA/66
Aug 04 13:06:00 [kernel] [176945.829546] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug 04 13:06:00 [kernel] [176945.830010] ata8.00: configured for UDMA/133
Aug 04 13:06:00 [kernel] [176945.830174] sd 7:0:0:0: [sdd] Starting disk

Aug 04 13:06:00 [kernel] [176949.801364] hub 2-7:1.0: hub_suspend
Aug 04 13:06:00 [kernel] [176949.801371] usb 2-7: unlink qh256-0001/ffff88024ea28f00 start 14 [1/0 us]
Aug 04 13:06:00 [kernel] [176949.801383] hub 5-0:1.0: port 1, status 0103, change 0000, 12 Mb/s
Aug 04 13:06:00 [kernel] [176949.801386] hub 8-0:1.0: state 7 ports 2 chg 0006 evt 0002
Aug 04 13:06:00 [kernel] [176949.801399] hub 8-0:1.0: port 1, status 0103, change 0000, 12 Mb/s
Aug 04 13:06:00 [kernel] [176949.801409] hub 8-0:1.0: port 2, status 0103, change 0000, 12 Mb/s
Aug 04 13:06:00 [kernel] [176949.803337] usb 2-7: usb auto-suspend, wakeup 1
Aug 04 13:06:00 [kernel] [176949.814263] hub 2-0:1.0: hub_suspend
Aug 04 13:06:00 [kernel] [176949.814276] usb usb2: bus auto-suspend, wakeup 1
Aug 04 13:06:00 [kernel] [176949.814279] ehci-pci 0000:00:1d.7: suspend root hub
Aug 04 13:23:44 [kernel] [178015.046625] conftest[11738]: segfault at 0 ip 00000000004005a0 sp 00007fff564e4000 error 4 in conftest[400000+1000]
Aug 04 13:23:44 [kernel] [178015.228798] conftest[11761]: segfault at 0 ip 00007f6d3695b6ca sp 00007fffb5a73ac8 error 4 in libc-2.21.so[7f6d368cb000+191000]
Aug 04 14:01:39 [kernel] [180293.329258] conftest[27168]: segfault at 0 ip 00000000004005a0 sp 00007fff098e3550 error 4 in conftest[400000+1000]
Aug 04 14:01:39 [kernel] [180293.443642] conftest[27191]: segfault at 0 ip 00007f1d511666ca sp 00007fff4c7e8b68 error 4 in libc-2.21.so[7f1d510d6000+191000]
Aug 04 15:18:44 [kernel] [184925.221090] conftest[29935]: segfault at 0 ip 00000000004005a0 sp 00007fffcabb2320 error 4 in conftest[400000+1000]
Aug 04 15:18:44 [kernel] [184925.365512] conftest[29958]: segfault at 0 ip 00007f2e543276ca sp 00007fffbc43b458 error 4 in libc-2.21.so[7f2e54297000+191000]
Aug 04 16:49:26 [kernel] [190374.242646] uhci_hcd 0000:00:1d.2: release dev 3 ep83-INT, period 1, phase 0, 17 us
Aug 04 16:49:27 [kernel] [190374.875084] uhci_hcd 0000:00:1d.2: reserve dev 3 ep83-INT, period 1, phase 0, 17 us


--------------------------------------------------------------------------------

kdm.log (a lot of->)

Errors from xkbcomp are not fatal to the X server
(II) AIGLX: Suspending AIGLX clients for VT switch
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Compat map for group 2 redefined
> Using new definition
> Warning: Compat map for group 3 redefined
> Using new definition
> Warning: Compat map for group 4 redefined
> Using new definition

........

Errors from xkbcomp are not fatal to the X server
(II) AIGLX: Suspending AIGLX clients for VT switch
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(EE) Server terminated successfully (0). Closing log file.
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Cannot mix incompatible Qt library (version 0x40805) with this library (version 0x40806)
KCrash: Application 'kdmgreet' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi directly
Cannot mix incompatible Qt library (version 0x40805) with this library (version 0x40806)
(EE) Server terminated successfully (0). Closing log file.
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
klauncher(2061) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(2055)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"

kdmgreet(2055)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(II) AIGLX: Suspending AIGLX clients for VT switch
setversion 1.4 failed: Permission denied

--------------

Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x58ab56]
(EE) 1: /usr/bin/X (mieqEnqueue+0x24b) [0x56d19b]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x44f0e2]
(EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fe13348a000+0x5f57) [0x7fe13348ff57]
(EE) 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fe13348a000+0x667d) [0x7fe13349067d]
(EE) 5: /usr/bin/X (0x400000+0x75018) [0x475018]
(EE) 6: /usr/bin/X (0x400000+0x9e197) [0x49e197]
(EE) 7: /lib64/libc.so.6 (0x7fe13ba18000+0x33ad0) [0x7fe13ba4bad0]
(EE) 8: /usr/bin/X (0x400000+0x18f020) [0x58f020]
(EE) 9: /lib64/libc.so.6 (0x7fe13ba18000+0x33ad0) [0x7fe13ba4bad0]
(EE) 10: /lib64/libc.so.6 (0x7fe13ba18000+0x90e45) [0x7fe13baa8e45]
(EE) 11: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7fe1373c7000+0x32bad) [0x7fe1373f9bad]
(EE) 12: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0x581b) [0x7fe136d9781b]
(EE) 13: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0x7fbf) [0x7fe136d99fbf]
(EE) 14: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0x11918) [0x7fe136da3918]
(EE) 15: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0xe8c0) [0x7fe136da08c0]
(EE) 16: /usr/bin/X (0x400000+0x1145c1) [0x5145c1]
(EE) 17: /usr/bin/X (0x400000+0x10a384) [0x50a384]
(EE) 18: /usr/bin/X (0x400000+0x37867) [0x437867]
(EE) 19: /usr/bin/X (0x400000+0x3b99b) [0x43b99b]
(EE) 20: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7fe13ba37fa0]
(EE) 21: /usr/bin/X (0x400000+0x25eee) [0x425eee]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x58ab56]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44f0e2]
(EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fe13348a000+0x5f57) [0x7fe13348ff57]
(EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fe13348a000+0x667d) [0x7fe13349067d]
(EE) 4: /usr/bin/X (0x400000+0x75018) [0x475018]
(EE) 5: /usr/bin/X (0x400000+0x9e197) [0x49e197]
(EE) 6: /lib64/libc.so.6 (0x7fe13ba18000+0x33ad0) [0x7fe13ba4bad0]
(EE) 7: /usr/bin/X (0x400000+0x18f020) [0x58f020]
(EE) 8: /lib64/libc.so.6 (0x7fe13ba18000+0x33ad0) [0x7fe13ba4bad0]
(EE) 9: /lib64/libc.so.6 (0x7fe13ba18000+0x90e45) [0x7fe13baa8e45]
(EE) 10: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7fe1373c7000+0x32bad) [0x7fe1373f9bad]
(EE) 11: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0x581b) [0x7fe136d9781b]
(EE) 12: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0x7fbf) [0x7fe136d99fbf]
(EE) 13: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0x11918) [0x7fe136da3918]
(EE) 14: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0xe8c0) [0x7fe136da08c0]
(EE) 15: /usr/bin/X (0x400000+0x1145c1) [0x5145c1]
(EE) 16: /usr/bin/X (0x400000+0x10a384) [0x50a384]
(EE) 17: /usr/bin/X (0x400000+0x37867) [0x437867]
(EE) 18: /usr/bin/X (0x400000+0x3b99b) [0x43b99b]
(EE) 19: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7fe13ba37fa0]
(EE) 20: /usr/bin/X (0x400000+0x25eee) [0x425eee]
(EE)
[mi] Increasing EQ size to 1024 to prevent dropped events.
[mi] EQ processing has resumed after 105 dropped events.
[mi] This may be caused my a misbehaving driver monopolizing the server's resources.
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x58ab56]
(EE) 1: /usr/bin/X (mieqEnqueue+0x24b) [0x56d19b]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x44f0e2]
(EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fe13348a000+0x5f57) [0x7fe13348ff57]
(EE) 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fe13348a000+0x667d) [0x7fe13349067d]
(EE) 5: /usr/bin/X (0x400000+0x75018) [0x475018]
(EE) 6: /usr/bin/X (0x400000+0x9e197) [0x49e197]
(EE) 7: /lib64/libc.so.6 (0x7fe13ba18000+0x33ad0) [0x7fe13ba4bad0]
(EE) 8: /usr/bin/X (0x400000+0x18f020) [0x58f020]
(EE) 9: /lib64/libc.so.6 (0x7fe13ba18000+0x33ad0) [0x7fe13ba4bad0]
(EE) 10: /lib64/libc.so.6 (0x7fe13ba18000+0x90e45) [0x7fe13baa8e45]
(EE) 11: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7fe1373c7000+0x32bad) [0x7fe1373f9bad]
(EE) 12: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0x581b) [0x7fe136d9781b]
(EE) 13: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0x7fbf) [0x7fe136d99fbf]
(EE) 14: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0x119eb) [0x7fe136da39eb]
(EE) 15: /usr/lib64/xorg/modules/libexa.so (0x7fe136d92000+0xe8c0) [0x7fe136da08c0]
(EE) 16: /usr/bin/X (0x400000+0x1145c1) [0x5145c1]
(EE) 17: /usr/bin/X (0x400000+0x10a384) [0x50a384]
(EE) 18: /usr/bin/X (0x400000+0x37867) [0x437867]
(EE) 19: /usr/bin/X (0x400000+0x3b99b) [0x43b99b]
(EE) 20: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7fe13ba37fa0]
(EE) 21: /usr/bin/X (0x400000+0x25eee) [0x425eee]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
[mi] Increasing EQ size to 2048 to prevent dropped events.
[mi] EQ processing has resumed after 41 dropped events.
[mi] This may be caused my a misbehaving driver monopolizing the server's resources.
(II) AIGLX: Suspending AIGLX clients for VT switch
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server


Last edited by as.gentoo on Tue Aug 11, 2015 6:58 pm; edited 1 time in total
Back to top
View user's profile Send private message
Buffoon
Veteran
Veteran


Joined: 17 Jun 2015
Posts: 1369
Location: EU or US

PostPosted: Mon Aug 10, 2015 7:11 pm    Post subject: Reply with quote

Bad SATA cable. You can always buy a good add-on SATA controller if it really is the M/B.
_________________
Life is a tragedy for those who feel and a comedy for those who think.
Back to top
View user's profile Send private message
as.gentoo
Guru
Guru


Joined: 07 Aug 2004
Posts: 319

PostPosted: Mon Aug 10, 2015 7:17 pm    Post subject: Reply with quote

Thanks, I will try that.
I already have a second controller. ;) My worry is that the chip - if the SATA part breaks - soon all other functionality like connection to the PCI port an whatever those mainboard chips do will break. It is not a dedicated SATA chip but what was called south-/northbridge a few years ago.
Back to top
View user's profile Send private message
as.gentoo
Guru
Guru


Joined: 07 Aug 2004
Posts: 319

PostPosted: Tue Aug 11, 2015 6:57 pm    Post subject: Reply with quote

Buffoon wrote:
Bad SATA cable. You can always buy a good add-on SATA controller if it really is the M/B.

Well, thanks a lot. :!: It was the cable. I tried it with another one, the system seems stable.

I didn't move the bad cable recently. How can a cable with conductors of 1mm square break just like that?
Is there any rule of the thumb for when to expect a cable to fail?
Back to top
View user's profile Send private message
albright
Advocate
Advocate


Joined: 16 Nov 2003
Posts: 2588
Location: Near Toronto

PostPosted: Tue Aug 11, 2015 7:51 pm    Post subject: Reply with quote

Quote:
Is there any rule of the thumb for when to expect a cable to fail?


the most inconvenient time possible ... :wink:
_________________
.... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme)
Back to top
View user's profile Send private message
as.gentoo
Guru
Guru


Joined: 07 Aug 2004
Posts: 319

PostPosted: Wed Aug 12, 2015 12:25 pm    Post subject: Reply with quote

albright wrote:
Quote:
Is there any rule of the thumb for when to expect a cable to fail?


the most inconvenient time possible ... :wink:

Which is any time then. ;)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum