[mythtv-users] Only Banners & Fanart

Stephen Worthington stephen_agent at jsw.gen.nz
Fri May 10 17:45:42 UTC 2019


On Fri, 10 May 2019 11:29:04 -0400, you wrote:

>On Fri, May 10, 2019 at 10:48 AM Stephen Worthington <
>stephen_agent at jsw.gen.nz> wrote:
>
>> On Fri, 10 May 2019 10:41:31 -0400, you wrote:
>>
>> >On Fri, May 10, 2019 at 10:22 AM Daryl McDonald <darylangela at gmail.com>
>> >wrote:
>> >
>> >>
>> >>
>> >> On Fri, May 10, 2019 at 7:17 AM Stephen Worthington <
>> >> stephen_agent at jsw.gen.nz> wrote:
>> >>
>> >>> On Fri, 10 May 2019 06:34:59 -0400, you wrote:
>> >>>
>> >>> >Greetings Mythizens, my storage1 drive dropped out yesterday,
>> recordings
>> >>> on
>> >>> >that drive are now red on the FE the drive does not show up in either
>> >>> disks
>> >>> >or gparted, but in files (GUI) I see storage1 under /etc/mnt/mythtv,
>> and
>> >>> in
>> >>> >files I see banners and fanart, no recordings or videos, etcetra. I
>> >>> assume
>> >>> >hardware failure, but partial disk failure? Any ideas?
>> >>>
>> >>> First find the /dev partition name that is on the mount point:
>> >>>
>> >>> df -l | grep -w /etc/mnt/mythtv | awk {'print $1'}
>> >>>
>> >>
>> >> Initial post has an erronious path:
>> >>  daryl at trieli:~$ df -l | grep -w /mnt | awk {'print $1'}
>> >> /dev/sdc1
>> >> /dev/sdb1
>> >> daryl at trieli:~$
>> >> But these two devices are storage2 and storage3
>> >>
>> >
>> >I've edited fstab to #out mounting storage1, otherwise the system wont
>> >boot. running e2fsck -y /dev/sd**  has got me up and running again. this
>> >time I cant do anything because the disk is not virtually present to the
>> >system, although it is physically present.
>> >
>> >daryl at trieli:/mnt/storage1$ ls -al
>> >total 12
>> >drwxr-xr-x 3 root   root   4096 Jan  4 22:36 .
>> >drwxrwxrwx 7 root   root   4096 Sep  8  2018 ..
>> >drwxr-xr-x 4 mythtv mythtv 4096 May 10 10:10 mythtv
>> >daryl at trieli:/mnt/storage1$
>> >
>> >Above is the result of right clicking on storage1 in the GUI of files and
>> >selecting "open in terminal". Normally (pre-corruption) storage1 mounts as
>> >/dev/sdb3,(I extended the recordings partition over the boot partition of
>> >my original system drive, hence 3) but because the system does not
>> >recognize it storage2 gets /dev/sdb1 and storage3 gets /dev/sdc1 system is
>> >on an SSD /dev/sda6.
>> >I'm thinking I should physically remove the disk and see if it is visable
>> >with a USB drive mounting hardware? And then run e2fsck -y from there.
>>
>> That sounds like a good idea.  But first check the log files to see if
>> the drive is mentioned there and if there are error messages about it.
>> _______________________________________________
>>
>> On a lark, I shut down my system, disconnected the drive power and sata
>cables, restarted the system, reconnected the drive, found it in /media,
>ran e2fsck -y /dev/sdd3, added it back into storage directories BE, and
>voilla, I'm back. The curious thing is that the check showed "clean" and
>didn't fix anything, and here is the smartmon report:
>smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-48-generic] (local build)
>Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
>
>=== START OF INFORMATION SECTION ===
>Model Family:     Toshiba 3.5" DT01ACA... Desktop HDD
>Device Model:     TOSHIBA DT01ACA100
>Serial Number:    53QYNJ2NS
>LU WWN Device Id: 5 000039 ff6db934a
>Firmware Version: MS2OA750
>User Capacity:    1,000,204,886,016 bytes [1.00 TB]
>Sector Sizes:     512 bytes logical, 4096 bytes physical
>Rotation Rate:    7200 rpm
>Form Factor:      3.5 inches
>Device is:        In smartctl database [for details use: -P show]
>ATA Version is:   ATA8-ACS T13/1699-D revision 4
>SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
>Local Time is:    Fri May 10 11:25:54 2019 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: ( 7944) 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: ( 133) 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
>   -       0
>  2 Throughput_Performance  0x0005   140   140   054    Pre-fail  Offline
>    -       75
>  3 Spin_Up_Time            0x0007   207   207   024    Pre-fail  Always
>   -       110 (Average 112)
>  4 Start_Stop_Count        0x0012   099   099   000    Old_age   Always
>   -       4858
>  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always
>   -       0
>  7 Seek_Error_Rate         0x000b   091   091   067    Pre-fail  Always
>   -       131079
>  8 Seek_Time_Performance   0x0005   110   110   020    Pre-fail  Offline
>    -       36
>  9 Power_On_Hours          0x0012   098   098   000    Old_age   Always
>   -       18420
> 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always
>   -       0
> 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always
>   -       3484
>192 Power-Off_Retract_Count 0x0032   096   096   000    Old_age   Always
>   -       4946
>193 Load_Cycle_Count        0x0012   096   096   000    Old_age   Always
>   -       4951
>194 Temperature_Celsius     0x0002   150   150   000    Old_age   Always
>   -       40 (Min/Max 17/50)
>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
>   -       94
>
>SMART Error Log Version: 1
>ATA Error Count: 94 (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 94 occurred at disk power-on lifetime: 15823 hours (659 days + 7
>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 00 00 00 00 00
>
>  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 08      00:08:13.719  IDENTIFY DEVICE
>  ec 00 01 01 00 00 00 04      00:08:13.558  IDENTIFY DEVICE
>  ec 00 00 00 00 00 a0 ff      00:08:13.245  IDENTIFY DEVICE
>  ec 00 00 00 00 00 a0 08      00:08:08.109  IDENTIFY DEVICE
>  ec 00 01 01 00 00 00 04      00:08:07.948  IDENTIFY DEVICE
>
>Error 93 occurred at disk power-on lifetime: 15823 hours (659 days + 7
>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 00 00 00 00 00
>
>  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 08      00:08:08.109  IDENTIFY DEVICE
>  ec 00 01 01 00 00 00 04      00:08:07.948  IDENTIFY DEVICE
>  ec 00 00 00 00 00 a0 ff      00:08:07.635  IDENTIFY DEVICE
>  ec 00 00 00 00 00 a0 08      00:08:02.483  IDENTIFY DEVICE
>  60 00 01 01 00 00 00 04      00:08:02.322  READ FPDMA QUEUED
>
>Error 92 occurred at disk power-on lifetime: 15823 hours (659 days + 7
>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 00 00 00 00 00
>
>  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 08      00:08:02.483  IDENTIFY DEVICE
>  60 00 01 01 00 00 00 04      00:08:02.322  READ FPDMA QUEUED
>  60 00 51 af 0a 00 00 ff      00:08:02.009  READ FPDMA QUEUED
>  60 00 58 00 0a 00 40 08      00:08:01.998  READ FPDMA QUEUED
>  60 80 40 80 08 00 40 08      00:08:01.995  READ FPDMA QUEUED
>
>Error 91 occurred at disk power-on lifetime: 15823 hours (659 days + 7
>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 51 af 0a 00 00  Error: ICRC, ABRT at LBA = 0x00000aaf = 2735
>
>  Commands leading to the command that caused the error were:
>  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>  -- -- -- -- -- -- -- --  ----------------  --------------------
>  60 00 58 00 0a 00 40 08      00:08:01.998  READ FPDMA QUEUED
>  60 80 40 80 08 00 40 08      00:08:01.995  READ FPDMA QUEUED
>  ef 10 02 00 00 00 a0 08      00:08:01.994  SET FEATURES [Enable SATA
>feature]
>  27 00 00 00 00 00 e0 08      00:08:01.994  READ NATIVE MAX ADDRESS EXT
>[OBS-ACS-3]
>  ec 00 00 00 00 00 a0 08      00:08:01.994  IDENTIFY DEVICE
>
>Error 90 occurred at disk power-on lifetime: 15823 hours (659 days + 7
>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 91 6f 09 00 00  Error: ICRC, ABRT at LBA = 0x0000096f = 2415
>
>  Commands leading to the command that caused the error were:
>  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>  -- -- -- -- -- -- -- --  ----------------  --------------------
>  60 80 30 80 08 00 40 08      00:08:01.505  READ FPDMA QUEUED
>  60 38 28 40 08 00 40 08      00:08:01.505  READ FPDMA QUEUED
>  60 08 20 10 08 00 40 08      00:08:01.505  READ FPDMA QUEUED
>  60 18 18 20 08 00 40 08      00:08:01.505  READ FPDMA QUEUED
>  60 08 10 78 08 00 40 08      00:08:01.505  READ FPDMA QUEUED
>
>SMART Self-test log structure revision number 1
>Num  Test_Description    Status                  Remaining
>LifeTime(hours)  LBA_of_first_error
># 1  Short offline       Completed without error       00%     18231
> -
># 2  Short offline       Completed without error       00%     16219
> -
># 3  Extended offline    Completed without error       00%     10227
> -
># 4  Extended offline    Interrupted (host reset)      90%     10224
> -
># 5  Extended offline    Completed without error       00%     10165
> -
># 6  Extended offline    Completed without error       00%      9743
> -
># 7  Extended offline    Interrupted (host reset)      80%      9674
> -
># 8  Extended offline    Completed without error       00%      9584
> -
># 9  Extended offline    Completed without error       00%      9355
> -
>#10  Extended offline    Interrupted (host reset)      60%      9294
> -
>#11  Extended offline    Completed without error       00%      9159
> -
>#12  Extended offline    Completed without error       00%      8979
> -
>#13  Extended offline    Completed without error       00%      8910
> -
>#14  Extended offline    Interrupted (host reset)      30%      8272
> -
>#15  Extended offline    Completed without error       00%      8190
> -
>#16  Extended offline    Interrupted (host reset)      70%      8096
> -
>#17  Extended offline    Completed without error       00%      7995
> -
>#18  Extended offline    Completed without error       00%      7896
> -
>#19  Extended offline    Completed without error       00%      7798
> -
>#20  Extended offline    Completed without error       00%      7566
> -
>#21  Extended offline    Completed without error       00%      7511
> -
>
>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.
>
>If there are red flags here please let me know, and thanks for everything
>else.

The errors in the SMART log look like what you would expect for a bad
SATA cable or bad SATA port, rather than a bad drive.  It is passing
self tests every time you do one.


More information about the mythtv-users mailing list