LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
Reload this Page SATA disk problems up after resume from memory
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 02-02-2015, 02:42 AM   #1
alleyoopster
Member
 
Registered: Jul 2008
Location: Cape Town
Distribution: Debian testing / unstable
Posts: 38

Rep: Reputation: 0
Unhappy SATA disk problems up after resume from memory

I have installed a newish Seagate 2TB SATA disk to use as home in my system. It was previously a backup device and has worked flawlessly. GPT tables, formatted EXT4 and using LVM. This is working fine until I suspend the computer and resume. Then /home is not available and only a reboot seems to fix the problem. There are no disk errors outside of the suspend / resume times and SMART has not reported any problems.

Kernel 3.13.0-37

Can anyone suggest what I can do to fix this?

kern log below

thanks



Code:
Jan 28 14:07:05 hornswaggle kernel: [ 7871.742753] PM: Syncing filesystems ... done.
Jan 28 14:07:05 hornswaggle kernel: [ 7871.894266] PM: Preparing system for mem sleep
Jan 28 14:07:05 hornswaggle kernel: [ 7871.894365] Freezing user space processes ... (elapsed 0.001 seconds) done.
Jan 28 14:07:05 hornswaggle kernel: [ 7871.896069] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jan 28 14:07:05 hornswaggle kernel: [ 7871.897133] PM: Entering mem sleep
Jan 28 14:07:05 hornswaggle kernel: [ 7871.897155] Suspending console(s) (use no_console_suspend to debug)
Jan 28 14:07:05 hornswaggle kernel: [ 7871.897390] sd 5:0:0:0: [sdc] Synchronizing SCSI cache
Jan 28 14:07:05 hornswaggle kernel: [ 7871.897522] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Jan 28 14:07:05 hornswaggle kernel: [ 7871.897589] sd 5:0:0:0: [sdc] Stopping disk
Jan 28 14:07:05 hornswaggle kernel: [ 7871.897669] sd 2:0:0:0: [sda] Synchronizing SCSI cache
Jan 28 14:07:05 hornswaggle kernel: [ 7871.897835] sd 2:0:0:0: [sda] Stopping disk
Jan 28 14:07:05 hornswaggle kernel: [ 7871.897880] sd 3:0:0:0: [sdb] Stopping disk
Jan 28 14:07:05 hornswaggle kernel: [ 7871.905076] i8042 aux 00:08: System wakeup disabled by ACPI
Jan 28 14:07:05 hornswaggle kernel: [ 7871.905268] parport_pc 00:04: disabled
Jan 28 14:07:05 hornswaggle kernel: [ 7872.954573] PM: suspend of devices complete after 1055.763 msecs
Jan 28 14:07:05 hornswaggle kernel: [ 7872.954754] PM: late suspend of devices complete after 0.179 msecs
Jan 28 14:07:05 hornswaggle kernel: [ 7872.954882] forcedeth 0000:00:07.0: System wakeup enabled by ACPI
Jan 28 14:07:05 hornswaggle kernel: [ 7872.970594] ehci-pci 0000:00:02.1: System wakeup enabled by ACPI
Jan 28 14:07:05 hornswaggle kernel: [ 7872.986604] ohci-pci 0000:00:02.0: System wakeup enabled by ACPI
Jan 28 14:07:05 hornswaggle kernel: [ 7873.002701] PM: noirq suspend of devices complete after 47.875 msecs
Jan 28 14:07:05 hornswaggle kernel: [ 7873.002760] ACPI: Preparing to enter system sleep state S3
Jan 28 14:07:05 hornswaggle kernel: [ 7873.003932] PM: Saving platform NVS memory
Jan 28 14:07:05 hornswaggle kernel: [ 7873.004052] Disabling non-boot CPUs ...
Jan 28 14:07:05 hornswaggle kernel: [ 7873.004329] Broke affinity for irq 22
Jan 28 14:07:05 hornswaggle kernel: [ 7873.005335] kvm: disabling virtualization on CPU1
Jan 28 14:07:05 hornswaggle kernel: [ 7873.005342] smpboot: CPU 1 is now offline
Jan 28 14:07:05 hornswaggle kernel: [ 7873.006024] ACPI: Low-level resume complete
Jan 28 14:07:05 hornswaggle kernel: [ 7873.006086] PM: Restoring platform NVS memory
Jan 28 14:07:05 hornswaggle kernel: [ 7873.006915] PCI-DMA: Resuming GART IOMMU
Jan 28 14:07:05 hornswaggle kernel: [ 7873.006915] PCI-DMA: Restoring GART aperture settings
Jan 28 14:07:05 hornswaggle kernel: [ 7873.007084] LVT offset 1 assigned for vector 0x400
Jan 28 14:07:05 hornswaggle kernel: [ 7873.007090] IBS: LVT offset 1 assigned
Jan 28 14:07:05 hornswaggle kernel: [ 7873.007273] Enabling non-boot CPUs ...
Jan 28 14:07:05 hornswaggle kernel: [ 7873.007303] x86: Booting SMP configuration:
Jan 28 14:07:05 hornswaggle kernel: [ 7873.007304] smpboot: Booting Node 0 Processor 1 APIC 0x1
Jan 28 14:07:05 hornswaggle kernel: [ 7873.018271] kvm: enabling virtualization on CPU1
Jan 28 14:07:05 hornswaggle kernel: [ 7873.020581] CPU1 is up
Jan 28 14:07:05 hornswaggle kernel: [ 7873.020950] ACPI: Waking up from system sleep state S3
Jan 28 14:07:05 hornswaggle kernel: [ 7873.036154] ohci-pci 0000:00:02.0: System wakeup disabled by ACPI
Jan 28 14:07:05 hornswaggle kernel: [ 7873.052179] ehci-pci 0000:00:02.1: System wakeup disabled by ACPI
Jan 28 14:07:05 hornswaggle kernel: [ 7873.052232] pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 28 14:07:05 hornswaggle kernel: [ 7873.068232] pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 28 14:07:05 hornswaggle kernel: [ 7873.100283] pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 28 14:07:05 hornswaggle kernel: [ 7873.116305] pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 28 14:07:05 hornswaggle kernel: [ 7873.132338] pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 28 14:07:05 hornswaggle kernel: [ 7873.132411] pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 28 14:07:05 hornswaggle kernel: [ 7873.132481] pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 28 14:07:05 hornswaggle kernel: [ 7873.132553] pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 28 14:07:05 hornswaggle kernel: [ 7873.148386] PM: noirq resume of devices complete after 126.383 msecs
Jan 28 14:07:05 hornswaggle kernel: [ 7873.148520] PM: early resume of devices complete after 0.092 msecs
Jan 28 14:07:05 hornswaggle kernel: [ 7873.149338] forcedeth 0000:00:07.0: System wakeup disabled by ACPI
Jan 28 14:07:05 hornswaggle kernel: [ 7873.151066] ata2: port disabled--ignoring
Jan 28 14:07:05 hornswaggle kernel: [ 7873.151347] parport_pc 00:04: activated
Jan 28 14:07:05 hornswaggle kernel: [ 7873.213674] forcedeth 0000:00:07.0: irq 43 for MSI/MSI-X
Jan 28 14:07:05 hornswaggle kernel: [ 7873.213698] forcedeth 0000:00:07.0 eth0: MSI enabled
Jan 28 14:07:05 hornswaggle kernel: [ 7873.213913] forcedeth 0000:00:07.0 eth0: no link during initialization
Jan 28 14:07:05 hornswaggle kernel: [ 7873.312837] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES) filtered out
Jan 28 14:07:05 hornswaggle kernel: [ 7873.312839] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 28 14:07:05 hornswaggle kernel: [ 7873.312852] ata1: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc5000000) ACPI=0x1f
01f (30:900:0x11)
Jan 28 14:07:05 hornswaggle kernel: [ 7873.328576] usb 1-3: reset high-speed USB device number 3 using ehci-pci
Jan 28 14:07:05 hornswaggle kernel: [ 7873.328804] ata1.00: configured for UDMA/66
Jan 28 14:07:05 hornswaggle kernel: [ 7873.883567] ata5: SATA link down (SStatus 0 SControl 300)
Jan 28 14:07:05 hornswaggle kernel: [ 7873.945247] psmouse serio1: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
Jan 28 14:07:05 hornswaggle kernel: [ 7874.941549] forcedeth 0000:00:07.0 eth0: link up
Jan 28 14:07:05 hornswaggle kernel: [ 7878.664236] ata6: link is slow to respond, please be patient (ready=0)
Jan 28 14:07:05 hornswaggle kernel: [ 7878.664241] ata3: link is slow to respond, please be patient (ready=0)
Jan 28 14:07:05 hornswaggle kernel: [ 7878.664246] ata4: link is slow to respond, please be patient (ready=0)
Jan 28 14:07:05 hornswaggle kernel: [ 7883.206774] ata4: SRST failed (errno=-16)
Jan 28 14:07:05 hornswaggle kernel: [ 7883.206784] ata3: SRST failed (errno=-16)
Jan 28 14:07:05 hornswaggle kernel: [ 7883.206793] ata6: SRST failed (errno=-16)
Jan 28 14:07:05 hornswaggle kernel: [ 7883.675471] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 28 14:07:05 hornswaggle kernel: [ 7883.675601] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 28 14:07:05 hornswaggle kernel: [ 7883.683572] ata3.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out
Jan 28 14:07:05 hornswaggle kernel: [ 7883.683574] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 28 14:07:05 hornswaggle kernel: [ 7883.683649] ata4.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out
Jan 28 14:07:05 hornswaggle kernel: [ 7883.683651] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 28 14:07:05 hornswaggle kernel: [ 7883.699792] ata3.00: configured for UDMA/133
Jan 28 14:07:05 hornswaggle kernel: [ 7883.699856] sd 2:0:0:0: [sda] Starting disk
Jan 28 14:07:05 hornswaggle kernel: [ 7883.767147] ata4.00: configured for UDMA/133
Jan 28 14:07:05 hornswaggle kernel: [ 7883.767210] sd 3:0:0:0: [sdb] Starting disk
Jan 28 14:07:05 hornswaggle kernel: [ 7888.722705] ata6: link is slow to respond, please be patient (ready=0)
Jan 28 14:07:05 hornswaggle kernel: [ 7893.265240] ata6: SRST failed (errno=-16)
Jan 28 14:07:05 hornswaggle kernel: [ 7898.781176] ata6: link is slow to respond, please be patient (ready=0)
Jan 28 14:07:05 hornswaggle kernel: [ 7928.335717] ata6: SRST failed (errno=-16)
Jan 28 14:07:05 hornswaggle kernel: [ 7928.335720] ata6: limiting SATA link speed to 1.5 Gbps
Jan 28 14:07:05 hornswaggle kernel: [ 7933.346914] ata6: SRST failed (errno=-16)
Jan 28 14:07:05 hornswaggle kernel: [ 7933.357146] ata6: reset failed, giving up
Jan 28 14:07:05 hornswaggle kernel: [ 7933.357148] ata6.00: disabled
Jan 28 14:07:05 hornswaggle kernel: [ 7933.357204] sd 5:0:0:0: [sdc] Starting disk
Jan 28 14:07:05 hornswaggle kernel: [ 7933.357234] sd 5:0:0:0: [sdc] START_STOP FAILED
Jan 28 14:07:05 hornswaggle kernel: [ 7933.357236] sd 5:0:0:0: [sdc]  
Jan 28 14:07:05 hornswaggle kernel: [ 7933.357237] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:05 hornswaggle kernel: [ 7933.357245] dpm_run_callback(): scsi_bus_resume+0x0/0x40 returns -5
Jan 28 14:07:05 hornswaggle kernel: [ 7933.357249] PM: Device 5:0:0:0 failed to resume async: error -5
Jan 28 14:07:05 hornswaggle kernel: [ 7933.357304] PM: resume of devices complete after 60122.145 msecs
Jan 28 14:07:05 hornswaggle kernel: [ 7934.522539] set resolution quirk: cval->res = 384
Jan 28 14:07:05 hornswaggle kernel: [ 7934.522883] PM: Finishing wakeup.
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529932] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529936] sd 5:0:0:0: [sdc]  
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529938] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529939] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:07:05 hornswaggle kernel: [ 7934.522884] Restarting tasks ... 
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529941] Write(10): 2a 00 12 05 1f 60 00 00 08 00
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529946] end_request: I/O error, dev sdc, sector 302325600
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529950] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error writing to inode 9439414
 (offset 0 size 0 starting block 37790188)
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529952] Buffer I/O error on device dm-2, logical block 37790188
Jan 28 14:07:05 hornswaggle kernel: [ 7934.544465] done.
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572381] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572386] sd 5:0:0:0: [sdc]  
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572388] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572389] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572390] Write(10): 2a 00 12 05 1f 60 00 00 08 00
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572396] end_request: I/O error, dev sdc, sector 302325600
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572400] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error writing to inode 9439414
 (offset 0 size 0 starting block 37790188)
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572403] Buffer I/O error on device dm-2, logical block 37790188
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810294] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810307] sd 5:0:0:0: [sdc]  
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810314] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810320] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810324] Write(10): 2a 00 4b 04 11 40 00 00 38 00
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810345] end_request: I/O error, dev sdc, sector 1258557760
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810393] Aborting journal on device dm-2-8.
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810420] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810426] sd 5:0:0:0: [sdc]  
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810430] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810439] EXT4-fs error (device dm-2) in ext4_reserve_inode_write:4849: Journal has aborted
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810449] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810453] Write(10): 2a 00 4b 04 10 00 00 00 08 00
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810474] end_request: I/O error, dev sdc, sector 1258557440
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810482] Buffer I/O error on device dm-2, logical block 157319168
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810486] lost page write due to I/O error on dm-2
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810517] JBD2: Error -5 detected when updating journal superblock for dm-2-8.
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810539] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810547] sd 5:0:0:0: [sdc]  
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810551] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810557] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810561] Write(10): 2a 00 00 00 10 00 00 00 08 00
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810582] end_request: I/O error, dev sdc, sector 4096
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810591] Buffer I/O error on device dm-2, logical block 0
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810595] lost page write due to I/O error on dm-2
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810633] EXT4-fs error (device dm-2) in ext4_dirty_inode:4968: Journal has aborted
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810639] EXT4-fs (dm-2): previous I/O error to superblock detected
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810664] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810669] sd 5:0:0:0: [sdc]  
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810673] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810678] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810681] Write(10): 2a 00 00 00 10 00 00 00 08 00
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810699] end_request: I/O error, dev sdc, sector 4096
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810704] Buffer I/O error on device dm-2, logical block 0
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810707] lost page write due to I/O error on dm-2
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810722] EXT4-fs (dm-2): previous I/O error to superblock detected
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810746] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810751] sd 5:0:0:0: [sdc]  
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810755] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810759] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810762] Write(10): 2a 00 00 00 10 00 00 00 08 00
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810779] end_request: I/O error, dev sdc, sector 4096
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810784] Buffer I/O error on device dm-2, logical block 0
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810787] lost page write due to I/O error on dm-2
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810799] EXT4-fs error (device dm-2): ext4_journal_check_start:56: Detected aborted journal
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810806] EXT4-fs (dm-2): Remounting filesystem read-only
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810810] EXT4-fs (dm-2): previous I/O error to superblock detected
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810833] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810838] sd 5:0:0:0: [sdc]  
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810842] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810846] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810849] Write(10): 2a 00 00 00 10 00 00 00 08 00
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810865] end_request: I/O error, dev sdc, sector 4096
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810870] Buffer I/O error on device dm-2, logical block 0
Jan 28 14:07:10 hornswaggle kernel: [ 7939.810873] lost page write due to I/O error on dm-2
Jan 28 14:12:01 hornswaggle kernel: [ 8231.431065] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:12:01 hornswaggle kernel: [ 8231.431073] sd 5:0:0:0: [sdc]  
Jan 28 14:12:01 hornswaggle kernel: [ 8231.431076] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:12:01 hornswaggle kernel: [ 8231.431078] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:12:01 hornswaggle kernel: [ 8231.431081] Read(10): 28 00 12 05 6c 40 00 00 20 00
Jan 28 14:12:01 hornswaggle kernel: [ 8231.431091] end_request: I/O error, dev sdc, sector 302345280
Jan 28 14:12:01 hornswaggle kernel: [ 8231.431125] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:12:01 hornswaggle kernel: [ 8231.431128] sd 5:0:0:0: [sdc]
 
Old 02-02-2015, 06:17 AM   #2
Keruskerfuerst
Senior Member
 
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199

Rep: Reputation: 164Reputation: 164
Please post /etc/fstab.
 
Old 02-02-2015, 06:58 AM   #3
Lsatenstein
Member
 
Registered: Jul 2005
Location: Montreal Canada
Distribution: Fedora 31and Tumbleweed) Gnome versions
Posts: 311
Blog Entries: 1

Rep: Reputation: 59
Quote:
Originally Posted by Keruskerfuerst View Post
Please post /etc/fstab.
and tell us more about the disk.
size in Terrabytes
partition formats (ext4, xfs, btrfs,...)
partition sizes.
 
Old 02-02-2015, 07:24 AM   #4
alleyoopster
Member
 
Registered: Jul 2008
Location: Cape Town
Distribution: Debian testing / unstable
Posts: 38

Original Poster
Rep: Reputation: 0
2TB Seagate sata
Ext4 with LVM2
Partition size 1.82TB

/etc/fstab
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/stripey-root /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
UUID=f0508820-4555-45eb-9c17-bc1eed31f93f /boot           ext4    defaults        0       2
#/dev/mapper/stripey-daily /home           xfs    defaults        0       2
/dev/mapper/data-home   /home           ext4    defaults        0       2
# swap was on /dev/sdc1 during installation
UUID=b4630733-0123-47b3-ae4d-141ebdf5889b  none            swap    sw              0       0



#sshfs#alleyoopster@hostchestnut.com:/home/alleyoopster /home/alleyoopster/hostchestnut  fuse defaults,idmap=user,allow_other    0   0


/dev/stripey/daily              /mnt/daily              xfs     defaults        1 2
 
Old 02-02-2015, 01:48 PM   #5
Keruskerfuerst
Senior Member
 
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199

Rep: Reputation: 164Reputation: 164
Please post fdisk -l.
And some hardwareinfo.
Last edited by Keruskerfuerst; 02-02-2015 at 01:49 PM.
 
Old 02-03-2015, 04:24 AM   #6
alleyoopster
Member
 
Registered: Jul 2008
Location: Cape Town
Distribution: Debian testing / unstable
Posts: 38

Original Poster
Rep: Reputation: 0
Motherboard is ASUS Socket AM3 Mainboard M4N68T-M+AMD Athlon II X2 260
Disk drives are mixture, mostly Seagate
Below is lspci. Is there anything else you wanted to know about the hardware?

lspci
Code:
00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control
01:06.0 Network controller: Ralink corp. RT3060 Wireless 802.11n 1T/1R

fdisk -l
Code:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00067ec1

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63     1028159      514048+  83  Linux
/dev/sda2         1028160   933894143   466432992   83  Linux
/dev/sda3       933894144   950278143     8192000   82  Linux swap / Solaris
/dev/sda4       950278144   976773119    13247488   8e  Linux LVM

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4229f6f6

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048  1953521663   976759808    7  HPFS/NTFS/exFAT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1  3907029167  1953514583+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/mapper/data-home: 1288.5 GB, 1288490188800 bytes                                                                            
255 heads, 63 sectors/track, 156650 cylinders, total 2516582400 sectors                                                               
Units = sectors of 1 * 512 = 512 bytes                                                                                                
Sector size (logical/physical): 512 bytes / 4096 bytes                                                                                
I/O size (minimum/optimal): 4096 bytes / 4096 bytes                                                                                   
Disk identifier: 0x00000000                                                                                                           
                                                                                                                                      
Disk /dev/mapper/data-home doesn't contain a valid partition table                                                                    
                                                                                                                                      
Disk /dev/mapper/stripey-root: 42.9 GB, 42949672960 bytes                                                                             
255 heads, 63 sectors/track, 5221 cylinders, total 83886080 sectors                                                                   
Units = sectors of 1 * 512 = 512 bytes                                                                                                
Sector size (logical/physical): 512 bytes / 512 bytes                                                                                 
I/O size (minimum/optimal): 65536 bytes / 131072 bytes                                                                                
Disk identifier: 0x00000000                                                                                                           
                                                                                                                                      
Disk /dev/mapper/stripey-root doesn't contain a valid partition table                                                                 
                                                                                                                                      
Disk /dev/mapper/stripey-daily: 1305.7 GB, 1305665863680 bytes                                                                        
255 heads, 63 sectors/track, 158738 cylinders, total 2550128640 sectors                                                               
Units = sectors of 1 * 512 = 512 bytes                                                                                                
Sector size (logical/physical): 512 bytes / 512 bytes                                                                                 
I/O size (minimum/optimal): 512 bytes / 512 bytes                                                                                     
Disk identifier: 0x00000000                                                                                                           
                                                                                                                                      
Disk /dev/mapper/stripey-daily doesn't contain a valid partition table
parted -l
Code:
parted -l
Model: ATA ST3500418AS (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size    Type     File system     Flags
 1      32.3kB  526MB  526MB   primary  ext4            boot
 2      526MB   478GB  478GB   primary
 3      478GB   487GB  8389MB  primary  linux-swap(v1)
 4      487GB   500GB  13.6GB  primary                  lvm


Model: ATA ST3_INVALID_PFM (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1000GB  1000GB  primary


Model: ATA ST2000DM001-1CH1 (scsi)
Disk /dev/sdc: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  2000GB  2000GB                     lvm


Model: Linux device-mapper (striped) (dm)
Disk /dev/mapper/stripey-root: 42.9GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  42.9GB  42.9GB  ext4


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/stripey-daily: 1306GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  1306GB  1306GB  xfs


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/data-home: 1288GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  1288GB  1288GB  ext4
and for good measure here is gdisk info
Code:
Command (? for help): p
Disk /dev/sdc: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 7ECB9540-98DF-4040-999F-B8E32D63607A
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2157 sectors (1.1 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048      3907028991   1.8 TiB     8E00  

Command (? for help): i
Using 1
Partition GUID code: E6D6D379-F507-44C2-A23C-238F2A3DF928 (Linux LVM)
Partition unique GUID: 6CE8543C-9749-432F-94CA-3EF79C708939
First sector: 2048 (at 1024.0 KiB)
Last sector: 3907028991 (at 1.8 TiB)
Partition size: 3907026944 sectors (1.8 TiB)
Attribute flags: 0000000000000000
Partition name: ''
Last edited by alleyoopster; 02-03-2015 at 04:28 AM.
 
Old 02-04-2015, 07:58 AM   #7
Keruskerfuerst
Senior Member
 
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199

Rep: Reputation: 164Reputation: 164
I havenīt seen any problems in your posted information.
There are problems with suspend to disk and to ram.
 
Old 02-04-2015, 08:33 AM   #8
alleyoopster
Member
 
Registered: Jul 2008
Location: Cape Town
Distribution: Debian testing / unstable
Posts: 38

Original Poster
Rep: Reputation: 0
The problems are after resume where the disk appears to go offline. This is shown in the first post and in the extract below. I cannot see any apparent suspend resume issues here, but this particular disk, which is reasonably new and functions well in other systems, will not come online. I can only think this is a kernel bug. I was looking at something else I could do to troubleshoot this further and ultimately fix it.

Code:
Jan 28 14:07:05 hornswaggle kernel: [ 7934.522883] PM: Finishing wakeup.
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529932] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529936] sd 5:0:0:0: [sdc]  
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529938] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529939] sd 5:0:0:0: [sdc] CDB: 
Jan 28 14:07:05 hornswaggle kernel: [ 7934.522884] Restarting tasks ... 
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529941] Write(10): 2a 00 12 05 1f 60 00 00 08 00
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529946] end_request: I/O error, dev sdc, sector 302325600
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529950] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error writing to inode 9439414
 (offset 0 size 0 starting block 37790188)
Jan 28 14:07:05 hornswaggle kernel: [ 7934.529952] Buffer I/O error on device dm-2, logical block 37790188
Jan 28 14:07:05 hornswaggle kernel: [ 7934.544465] done.
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572381] sd 5:0:0:0: [sdc] Unhandled error code
Jan 28 14:07:05 hornswaggle kernel: [ 7934.572386] sd 5:0:0:0: [sdc]
 
Old 03-29-2022, 10:58 AM   #9
txangel
LQ Newbie
 
Registered: Mar 2022
Location: UK
Distribution: Arch
Posts: 1

Rep: Reputation: 0
I just had this similar issue with just one of my drives. When resuming from sleep.

This drive I took from a NAS (Toshiba N300) and it supports SATA hotplugging (so it can be removed and installed in a NAS without stopping the NAS box).

It was failing to resume from sleep because of the SATA link was not coming back up fast enough for the kernel.
Code:
Mar 29 15:16:13.531073 ArmchairTraveller kernel: ata1: SATA max UDMA/133 abar m2048@0x53f02000 port 0x53f02100 irq 129
Mar 29 15:16:13.531415 ArmchairTraveller kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 29 15:16:13.531418 ArmchairTraveller kernel: ata1.00: ATA-10: TOSHIBA HDWG440, 0601, max UDMA/133
Mar 29 15:16:13.531475 ArmchairTraveller kernel: ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Mar 29 15:16:13.531478 ArmchairTraveller kernel: ata1.00: Features: NCQ-prio
Mar 29 15:16:13.531512 ArmchairTraveller kernel: ata1.00: configured for UDMA/133
Mar 29 16:31:05.202605 ArmchairTraveller kernel: ata1: SATA link down (SStatus 4 SControl 300)
Mar 29 16:31:05.203185 ArmchairTraveller kernel: ata1: SATA link down (SStatus 4 SControl 300)
Mar 29 16:31:05.203222 ArmchairTraveller kernel: ata1: SATA link down (SStatus 4 SControl 300)
Mar 29 16:31:05.203289 ArmchairTraveller kernel: ata1.00: disabled
Mar 29 16:31:05.203333 ArmchairTraveller kernel: ata1.00: detaching (SCSI 0:0:0:0)
The solution in this case was to enable in the BIOS hotplug for this SATA port.

After doing that it did resume from sleep correctly.
Code:
[Tue Mar 29 16:45:20 2022] ata1: SATA max UDMA/133 abar m2048@0x53f02000 port 0x53f02100 irq 129
[Tue Mar 29 16:45:20 2022] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Tue Mar 29 16:45:20 2022] ata1.00: ATA-10: TOSHIBA HDWG440, 0601, max UDMA/133
[Tue Mar 29 16:45:20 2022] ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[Tue Mar 29 16:45:20 2022] ata1.00: Features: NCQ-prio
[Tue Mar 29 16:45:20 2022] ata1.00: configured for UDMA/133
[Tue Mar 29 16:46:29 2022] ata1: link is slow to respond, please be patient (ready=0)
[Tue Mar 29 16:46:34 2022] ata1: COMRESET failed (errno=-16)
[Tue Mar 29 16:46:36 2022] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Tue Mar 29 16:46:36 2022] ata1.00: configured for UDMA/133
COMRESET seems to be a normal thing when waking up from sleep
 
Old 04-01-2022, 07:20 AM   #10
Arnulf
Member
 
Registered: Jan 2022
Location: Hanover, Germany
Distribution: Slackware
Posts: 321

Rep: Reputation: 117Reputation: 117
Quote:
Originally Posted by alleyoopster View Post

end_request: I/O error, dev sdc, sector 302325600

Normally this indicates dying hardware, mostly disk drive.
Backup data from disk drive if possibe, than run
badblocks -wsv /dev/sdc
 
Old 04-01-2022, 09:02 PM   #11
computersavvy
Senior Member
 
Registered: Aug 2016
Posts: 3,345

Rep: Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486Reputation: 1486
The only thing I see that is curious for me is that you have a newish 2TB drive and your OS is running a very old kernel.
"Kernel 3.13.0-37"
I wonder if the (old) age of the OS and the age of the drive (new) may be causing a conflict during resume from suspend. I suspect the rest of the machine is as aged as the OS.

There is one item of note in your first post in that there are several references to read errors and it seems to indicate that an fsck may be in order for that file system. Some of the corrupted sectors seem to be in the journal blocks, which could prevent a clean read and activate.

My first step would be to boot to a live media and run fsck on the file system on that drive, JIC. Then reboot and see if there is any difference in the resume after suspend.

Also I note that you have an nvidia GPU and that has been known to have problems with suspend/resume under certain conditions. By chance could you tell us the OS and version you are running.
 
Old 04-02-2022, 01:22 AM   #12
Jan K.
Member
 
Registered: Apr 2019
Location: Esbjerg
Distribution: Windows 7...
Posts: 773

Rep: Reputation: 489Reputation: 489Reputation: 489Reputation: 489Reputation: 489
It's kinda two threads in one... resurrected from some 7 years ago...
 
  


Reply

Tags
disk, resume, suspend


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] SATA write speed drops after resume machs Linux - Hardware 2 10-14-2012 09:35 AM
redhat linux installation problems - SATA hard disk not detected jjs_anand Linux - Newbie 4 05-13-2008 10:18 AM
Problems with SATA Disk Drive (software or hardware)? ]Trix[ Linux - Hardware 1 01-25-2007 05:30 AM
mandrake 10.2 x86_64 - ext3 and sata disk problems renas.r Linux - Hardware 1 08-22-2005 06:09 PM
problems installing grub on sata disk atharh Linux - Hardware 3 09-19-2004 07:22 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 02:12 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration