System fails into emergency mode? What happened?

This morning my computer was frozen and upon restarting it got into emergency mode. I didn’t know what to do and I booted with PartedMagic to see the status of the harddisk fearing for the worse(who wouldn’t). I started to scan the disk with some tools available and stopped the process as it was estimated to be around 6:30 hours which made things even worse as other tools were not even able to see what was on the disk( a very good tool - TestDisk). I got more and more depressed about it and then I decided to restart the scan of the disk which I stopped earlier to see what would be the result of it(after rebooting with PartedMagic). After 6:30 long hours the result was that there are no errors!!! and I was able to mount the partitions and see the contents. Booting w/o PartedMagic got me again into emergency mode which was solved only by running fsck -A. That fixed few nodes with problems and finally I was able to boot in the system from where I’m telling you this story. Well beside the soap story I would like to get info on how what can I check to understand what happened. Here is the contents of /var/log/messages


Mar 11 21:50:13 aruba rsyslogd: -- MARK --
Mar 11 21:50:30 aruba smartd[2383]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 162 to 157
Mar 11 22:45:53 aruba kernel: [93182.886692] ata1.00: exception Emask 0x50 SAct 0x1000 SErr 0x400800 action 0x6 frozen
Mar 11 22:45:53 aruba kernel: [93182.886702] ata1.00: irq_stat 0x08000000, interface fatal error
Mar 11 22:45:53 aruba kernel: [93182.886711] ata1: SError: { HostInt Handshk }
Mar 11 22:45:53 aruba kernel: [93182.886719] ata1.00: failed command: WRITE FPDMA QUEUED
Mar 11 22:45:53 aruba kernel: [93182.886734] ata1.00: cmd 61/48:60:80:5c:74/00:00:0a:00:00/40 tag 12 ncq 36864 out
Mar 11 22:45:53 aruba kernel: [93182.886737]          res 50/00:48:80:5c:74/00:00:0a:00:00/40 Emask 0x50 (ATA bus error)
Mar 11 22:45:53 aruba kernel: [93182.886744] ata1.00: status: { DRDY }
Mar 11 22:45:53 aruba kernel: [93182.886753] ata1: hard resetting link
Mar 11 22:45:54 aruba kernel: [93183.345247] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 11 22:45:54 aruba kernel: [93183.348063] ata1.00: configured for UDMA/133
Mar 11 22:45:54 aruba kernel: [93183.358266] ata1: EH complete
Mar 11 22:50:31 aruba smartd[2383]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 157 to 153
Mar 11 22:50:31 aruba smartd[2383]: Device: /dev/sda [SAT], ATA error count increased from 287 to 288
Mar 11 22:53:19 aruba kernel: [93627.915037] ata1.00: exception Emask 0x50 SAct 0x3 SErr 0x400800 action 0x6 frozen
Mar 11 22:53:19 aruba kernel: [93627.915040] ata1.00: irq_stat 0x08000000, interface fatal error
Mar 11 22:53:19 aruba kernel: [93627.915043] ata1: SError: { HostInt Handshk }
Mar 11 22:53:19 aruba kernel: [93627.915046] ata1.00: failed command: WRITE FPDMA QUEUED
Mar 11 22:53:19 aruba kernel: [93627.915051] ata1.00: cmd 61/08:00:50:dd:bc/00:00:99:00:00/40 tag 0 ncq 4096 out
Mar 11 22:53:19 aruba kernel: [93627.915052]          res 50/00:18:d0:a4:c7/00:00:78:00:00/40 Emask 0x50 (ATA bus error)
Mar 11 22:53:19 aruba kernel: [93627.915054] ata1.00: status: { DRDY }
Mar 11 22:53:19 aruba kernel: [93627.915055] ata1.00: failed command: WRITE FPDMA QUEUED
Mar 11 22:53:19 aruba kernel: [93627.915059] ata1.00: cmd 61/18:08:d0:a4:c7/00:00:78:00:00/40 tag 1 ncq 12288 out
Mar 11 22:53:19 aruba kernel: [93627.915060]          res 50/00:18:d0:a4:c7/00:00:78:00:00/40 Emask 0x50 (ATA bus error)
Mar 11 22:53:19 aruba kernel: [93627.915062] ata1.00: status: { DRDY }
Mar 11 22:53:19 aruba kernel: [93627.915065] ata1: hard resetting link
Mar 11 22:53:20 aruba kernel: [93628.373609] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 11 22:53:20 aruba kernel: [93628.376526] ata1.00: configured for UDMA/133
Mar 11 22:53:20 aruba kernel: [93628.387635] ata1: EH complete
Mar 11 22:54:42 aruba kernel: [93710.093166] ata1.00: exception Emask 0x50 SAct 0xc SErr 0x400800 action 0x6 frozen
Mar 11 22:54:42 aruba kernel: [93710.093168] ata1.00: irq_stat 0x08000000, interface fatal error
Mar 11 22:54:42 aruba kernel: [93710.093171] ata1: SError: { HostInt Handshk }
Mar 11 22:54:42 aruba kernel: [93710.093173] ata1.00: failed command: WRITE FPDMA QUEUED
Mar 11 22:54:42 aruba kernel: [93710.093176] ata1.00: cmd 61/00:10:00:10:62/04:00:09:00:00/40 tag 2 ncq 524288 out
Mar 11 22:54:42 aruba kernel: [93710.093177]          res 50/00:d0:00:14:62/00:00:09:00:00/40 Emask 0x50 (ATA bus error)
Mar 11 22:54:42 aruba kernel: [93710.093179] ata1.00: status: { DRDY }
Mar 11 22:54:42 aruba kernel: [93710.093180] ata1.00: failed command: WRITE FPDMA QUEUED
Mar 11 22:54:42 aruba kernel: [93710.093183] ata1.00: cmd 61/d0:18:00:14:62/00:00:09:00:00/40 tag 3 ncq 106496 out
Mar 11 22:54:42 aruba kernel: [93710.093184]          res 50/00:d0:00:14:62/00:00:09:00:00/40 Emask 0x50 (ATA bus error)
Mar 11 22:54:42 aruba kernel: [93710.093185] ata1.00: status: { DRDY }
Mar 11 22:54:42 aruba kernel: [93710.093188] ata1: hard resetting link
Mar 11 22:54:42 aruba kernel: [93710.551412] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 11 22:54:42 aruba kernel: [93710.554287] ata1.00: configured for UDMA/133
Mar 11 22:54:42 aruba kernel: [93710.565410] ata1: EH complete
Mar 11 22:59:34 aruba kernel: [94002.084726] ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x400800 action 0x6 frozen
Mar 11 22:59:34 aruba kernel: [94002.084735] ata1.00: irq_stat 0x08000000, interface fatal error
Mar 11 22:59:34 aruba kernel: [94002.084744] ata1: SError: { HostInt Handshk }
Mar 11 22:59:34 aruba kernel: [94002.084751] ata1.00: failed command: WRITE FPDMA QUEUED
Mar 11 22:59:34 aruba kernel: [94002.084765] ata1.00: cmd 61/58:00:60:10:bd/00:00:99:00:00/40 tag 0 ncq 45056 out
Mar 11 22:59:34 aruba kernel: [94002.084769]          res 50/00:58:60:10:bd/00:00:99:00:00/40 Emask 0x50 (ATA bus error)
Mar 11 22:59:34 aruba kernel: [94002.084776] ata1.00: status: { DRDY }
Mar 11 22:59:34 aruba kernel: [94002.084785] ata1: hard resetting link
Mar 11 22:59:35 aruba kernel: [94002.543538] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 11 22:59:35 aruba kernel: [94002.546364] ata1.00: configured for UDMA/133
Mar 11 22:59:35 aruba kernel: [94002.557507] ata1: EH complete
Mar 11 23:02:48 aruba kernel: [94195.984523] ata1: limiting SATA link speed to 1.5 Gbps
Mar 11 23:02:48 aruba kernel: [94195.984527] ata1.00: exception Emask 0x50 SAct 0xf00 SErr 0x400800 action 0x6 frozen
Mar 11 23:02:48 aruba kernel: [94195.984529] ata1.00: irq_stat 0x08000000, interface fatal error
Mar 11 23:02:48 aruba kernel: [94195.984531] ata1: SError: { HostInt Handshk }
Mar 11 23:02:48 aruba kernel: [94195.984533] ata1.00: failed command: WRITE FPDMA QUEUED
Mar 11 23:02:48 aruba kernel: [94195.984537] ata1.00: cmd 61/08:40:18:0c:40/00:00:99:00:00/40 tag 8 ncq 4096 out
Mar 11 23:02:48 aruba kernel: [94195.984538]          res 50/00:08:28:09:80/00:00:9e:00:00/40 Emask 0x50 (ATA bus error)
Mar 11 23:02:48 aruba kernel: [94195.984539] ata1.00: status: { DRDY }
Mar 11 23:02:48 aruba kernel: [94195.984541] ata1.00: failed command: WRITE FPDMA QUEUED
Mar 11 23:02:48 aruba kernel: [94195.984543] ata1.00: cmd 61/08:48:a8:18:41/00:00:99:00:00/40 tag 9 ncq 4096 out
Mar 11 23:02:48 aruba kernel: [94195.984544]          res 50/00:08:28:09:80/00:00:9e:00:00/40 Emask 0x50 (ATA bus error)
Mar 11 23:02:48 aruba kernel: [94195.984546] ata1.00: status: { DRDY }
Mar 11 23:02:48 aruba kernel: [94195.984547] ata1.00: failed command: WRITE FPDMA QUEUED
Mar 11 23:02:48 aruba kernel: [94195.984550] ata1.00: cmd 61/08:50:70:08:80/00:00:99:00:00/40 tag 10 ncq 4096 out
Mar 11 23:02:48 aruba kernel: [94195.984551]          res 50/00:08:28:09:80/00:00:9e:00:00/40 Emask 0x50 (ATA bus error)
Mar 11 23:02:48 aruba kernel: [94195.984552] ata1.00: status: { DRDY }
Mar 11 23:02:48 aruba kernel: [94195.984553] ata1.00: fMar 12 20:16:51 aruba rsyslogd: [origin software="rsyslogd" swVersion="5.10.1" x-pid="907" x-info="http://www.rsyslog.com"] start
Mar 12 20:16:51 aruba kernel:   108.244559] type=1400 audit(1363133810.497:2): apparmor="STATUS" operation="profile_load" name="/{usr/,}bin/ping" pid=729 comm="apparmor_parser"

This doesn’t tell me much and beside the fact that I need to backup right now what can I check to try to understand the sudden problem, to be able to pinpoint what component failed. The Hardware, the OS? Any help and suggestions are appreciated. Thanks

On Wed, 13 Mar 2013 00:46:01 +0000, dmera wrote:

> The Hardware, the OS?

Hardware.

These types of errors come from the controller. You can try pulling
status information with smartctl (if you have it installed) and see if
the hardware logs tell you anything. But you are correct that you need
to back up your data ASAP, if the drive will let you access it.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

smart - Is this drive failure or something else? - Ask Ubuntu

On 2013-03-13 01:46, dmera wrote:

> Booting w/o PartedMagic got me again into emergency mode which was
> solved only by running fsck

This was what the initial emergency mode was about, the first tool to run.

And the logs show that you may have disk hardware problem. A smartctl
run might say (long test). It is advisable to have a full backup made.

An smartctl short test may tell you quick it there are bad sectors
pending a remap, which is a bad sign - specially if the number increases.


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

Thank you hendersj my backup was on full speed but last night got the same messages from kernel, but after rebooting twice I was able to get logged in. I’m copying my home as fast as I can. smartctl is the tool I ran under PartedMagic(the long test 6:30) which gave me no errors at all.I ran the command which I think it runs a short test but no errors. Any other suggestions?

Thank you vazhavandan. I do have an ASUS motherboard but I was not able to figure out visually or via BIOS if it’s because of the problem described in your link, but as soon as my backup is finish I will investigate further. Thanks for the link

Thank robin_listas. I ran the long test and no errors were logged that’s why I’m puzzled now. I’m backing up now my entire home(>2 TB). What would you do after is completed? format the disks and reinstall? Your suggestions/thoughts are needed.

the only annoying thing right now is that the screen gets black after 4-5 seconds of idle like there is no input and any input via keyboard/mouse will get it back. I checked all the settings but nothing will correct it. This was present in the past but only after several minutes, specially I notice it when playing a movie but was not that annoyed by it. Now is a nuisance for which I don’t find any solution.

" They had a defect that caused the sata ports to break down over time and had a big recall." <==This was a very weird stuff in that link . Don’t know how ports can wear out. No mechanical action there.

On Wed, 13 Mar 2013 16:06:01 +0000, dmera wrote:

> Thank you hendersj my backup was on full speed but last night got the
> same messages from kernel, but after rebooting twice I was able to get
> logged in. I’m copying my home as fast as I can. smartctl is the tool I
> ran under PartedMagic(the long test 6:30) which gave me no errors at
> all.I ran the command which I think it runs a short test but no errors.
> Any other suggestions?

Try the long test. :slight_smile:

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

Hi hendersj. as we say sometimes “too much english” referring to talking too much(in this case me). That long smartctl test was performed and no errors were encountered. After the backing was completed when trying to reboot I got the same problems and in a terminal session(Ctrl-Alt-F2) i get after logging in:
every 10 errors like bellow


INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty" 
.....
INIT: Id "3" respawning too fast: disabled for 5 minutes

Any terminal session I try to open is exactly the same so I need to hard power off. (CTRL-Alt-Del doesn’t work )

What can/should be done? any suggestions?

On 2013-03-13 23:56, dmera wrote:
> That long smartctl test was
> performed and no errors were encountered

Please print the “smartctl -a /dev/whatever” output, in code tags. Not
only “errors” are the things to look at.


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

robin_listas - Today, so far it works fine. I did a cleanup of it(dust wise - which forced me to change CPU - pin bend, but c’est la vie) and i don’t see any symptoms which I encountered yesterday(monitor turning off after 4-5 seconds). Here is the output.


# smartctl -a /dev/sda
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.4.11-2.16-desktop] (SUSE RPM)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar 5K3000
Device Model:     Hitachi HDS5C3020ALA632
Serial Number:    ML4220F318T4VK
LU WWN Device Id: 5 000cca 369d21527
Firmware Version: ML6OA580
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5940 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Thu Mar 14 11:37:53 2013 EDT
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:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
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:                (24155) 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 403) minutes.
SCT capabilities:              (0x003d) 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     0x000b   100   100   016    Pre-fail  Always       -       1
  2 Throughput_Performance  0x0005   129   129   054    Pre-fail  Offline      -       119
  3 Spin_Up_Time            0x0007   189   189   024    Pre-fail  Always       -       221 (Average 360)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       279
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   148   148   020    Pre-fail  Offline      -       28
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       7903
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       278
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       280
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       280
194 Temperature_Celsius     0x0002   176   176   000    Old_age   Always       -       34 (Min/Max 18/47)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       526

SMART Error Log Version: 1
ATA Error Count: 529 (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 529 occurred at disk power-on lifetime: 7902 hours (329 days + 6 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
  -- -- -- -- -- -- --
  84 51 01 df 8e 29 00  Error: ICRC, ABRT at LBA = 0x00298edf = 2723551

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 18 10 10 4e 45 40 08      09:35:48.191  WRITE FPDMA QUEUED
  61 08 08 80 ca 6f 40 08      09:35:48.191  WRITE FPDMA QUEUED
  61 08 00 d8 8e 29 40 08      09:35:48.191  WRITE FPDMA QUEUED
  ef 90 03 00 00 00 a0 08      09:35:48.181  SET FEATURES [Reserved for Serial ATA]
  ef 10 02 00 00 00 a0 08      09:35:48.180  SET FEATURES [Reserved for Serial ATA]

Error 528 occurred at disk power-on lifetime: 7902 hours (329 days + 6 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
  -- -- -- -- -- -- --
  84 51 09 1f 4e 45 01  Error: ICRC, ABRT at LBA = 0x01454e1f = 21319199

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 10 d8 8e 29 40 08      09:35:47.721  WRITE FPDMA QUEUED
  61 08 08 80 ca 6f 40 08      09:35:47.721  WRITE FPDMA QUEUED
  61 18 00 10 4e 45 40 08      09:35:47.721  WRITE FPDMA QUEUED
  ef 90 03 00 00 00 a0 08      09:35:47.711  SET FEATURES [Reserved for Serial ATA]
  ef 10 02 00 00 00 a0 08      09:35:47.710  SET FEATURES [Reserved for Serial ATA]

Error 527 occurred at disk power-on lifetime: 7902 hours (329 days + 6 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
  -- -- -- -- -- -- --
  84 51 01 df 8e 29 00  Error: ICRC, ABRT at LBA = 0x00298edf = 2723551

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 18 10 10 4e 45 40 08      09:35:47.251  WRITE FPDMA QUEUED
  61 08 08 80 ca 6f 40 08      09:35:47.251  WRITE FPDMA QUEUED
  61 08 00 d8 8e 29 40 08      09:35:47.251  WRITE FPDMA QUEUED
  ef 90 03 00 00 00 a0 08      09:35:47.240  SET FEATURES [Reserved for Serial ATA]
  ef 10 02 00 00 00 a0 08      09:35:47.240  SET FEATURES [Reserved for Serial ATA]

Error 526 occurred at disk power-on lifetime: 7902 hours (329 days + 6 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
  -- -- -- -- -- -- --
  84 51 08 20 4e 45 01  Error: ICRC, ABRT at LBA = 0x01454e20 = 21319200

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 10 d8 8e 29 40 08      09:35:46.781  WRITE FPDMA QUEUED
  61 08 08 80 ca 6f 40 08      09:35:46.781  WRITE FPDMA QUEUED
  61 18 00 10 4e 45 40 08      09:35:46.781  WRITE FPDMA QUEUED
  ef 90 03 00 00 00 a0 08      09:35:46.770  SET FEATURES [Reserved for Serial ATA]
  ef 10 02 00 00 00 a0 08      09:35:46.770  SET FEATURES [Reserved for Serial ATA]

Error 525 occurred at disk power-on lifetime: 7902 hours (329 days + 6 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
  -- -- -- -- -- -- --
  84 51 01 df 8e 29 00  Error: ICRC, ABRT at LBA = 0x00298edf = 2723551

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 18 20 10 4e 45 40 08      09:35:46.307  WRITE FPDMA QUEUED
  61 08 18 80 ca 6f 40 08      09:35:46.307  WRITE FPDMA QUEUED
  61 08 10 d8 8e 29 40 08      09:35:46.307  WRITE FPDMA QUEUED
  60 00 08 e0 03 c0 40 08      09:35:46.307  READ FPDMA QUEUED
  60 00 00 e0 02 c0 40 08      09:35:46.307  READ 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%      7883         -
# 2  Short offline       Completed without error       00%      7876         -
# 3  Extended offline    Interrupted (host reset)      90%      7875         -
# 4  Short offline       Completed without error       00%      7874         -

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.