Hard disk not detected?!

[Aaron-B]

Hi,

Following the death of my first box, I've just received a second-hand HDR-Fox T2 purchased on eBay. I've installed CFW, but am being told that it cannot find the hard disk.

Having attempted to record, nothing happens or appears in the Media browser. The Data Storage menu confirms a drive is present (1TB, and the warranty seal is in tact), with 885.8GB available, 20.2GB used and 114GB reserved. HDD Test fails with error code 8 and recommends Format Storage, which I've done, but no change.

Any ideas what could be causing this? Have I been lumbered with a dud? The box was sufficiently wrapped in layers of thick bubble wrap for postage so I wouldn't have expected any damage to have occurred en route.

Thanks in advance.

 

[Ezra Pound]

It might be worth following this thread :-

https://hummy.tv/forum/threads/replacement-hdd-advice.10357/#post-157578

Another error code 8

 

[Aaron-B]

Thanks Ezra, but looks like that's specifically about what new drive to get, with no particular diagnostic.

Predictably, within minutes of posting this thread the box suddenly clicked (partially) into operation. A live recording started being saved, and I was able to progress through the CFW set up.

However, the HDD Test still fails with error code 8 (message is that hard drive could not be found), whilst Format Storage tells me the disk is too large to format!

On logging in to the CFW diagnostics, I get:

Disk realloc sector count is: 16
Disk pending sector count is: 7
Disk offline sector count is: 7

Disk Information

SMART Status	PASSED
Model Family	Seagate Video 3.5 HDD
Device Model	ST1000VM002-1CT162
Serial Number	W1G0EW3Z
LU WWN Device Id	5 000c50 05c5e9bdd
Firmware Version	SC23
User Capacity	1,000,204,886,016 bytes [1.00 TB]
Sector Sizes	512 bytes logical, 4096 bytes physical
Rotation Rate	5900 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	Tue Oct 19 16:46:31 2021 BST
SMART support is	Available - device has SMART capability.
SMART support is	Enabled

Attributes

ID	Name	Flags	Raw Value	Value	Worst	Threshold	Life Left	Notes
1	Raw_Read_Error_Rate	POSR--	152878542	086	077	006		-
3	Spin_Up_Time	PO----	0	097	097	000		-
4	Start_Stop_Count	-O--CK	2387	098	098	020	98%	-
5	Reallocated_Sector_Ct	PO--CK	16	100	100	036	100%	-
7	Seek_Error_Rate	POSR--	131712064	081	060	030		-
9	Power_On_Hours	-O--CK	4760	095	095	000	95%	-
10	Spin_Retry_Count	PO--C-	0	100	100	097	100%	-
12	Power_Cycle_Count	-O--CK	2388	098	098	020	98%	-
184	End-to-End_Error	-O--CK	0	100	100	099		-
187	Reported_Uncorrect	-O--CK	1480	001	001	000		-
188	Command_Timeout	-O--CK	0	100	100	000		-
189	High_Fly_Writes	-O-RCK	3	097	097	000		-
190	Airflow_Temperature_Cel	-O---K	53	047 (53°C)	034 (66°C)	045 (55°C)		In_the_past
191	G-Sense_Error_Rate	-O--CK	0	100	100	000		-
192	Power-Off_Retract_Count	-O--CK	2386	099	099	000	99%	-
193	Load_Cycle_Count	-O--CK	2387	099	099	000	99%	-
194	Temperature_Celsius	-O---K	53	053	066	000		-
197	Current_Pending_Sector	-O--C-	7	100	100	000		-
198	Offline_Uncorrectable	----C-	7	100	100	000		-
199	UDMA_CRC_Error_Count	-OSRCK	0	200	200	000		-

Self-test logs

No.	Description	Status	Remaining	When	First Error LBA
# 1	Short offline	Completed: read failure	90%	4760	920174024
# 2	Short offline	Completed: read failure	90%	4760	920174024
# 3	Short offline	Completed: read failure	90%	4759	920174024
# 4	Short offline	Completed: read failure	90%	4759	920174024
# 5	Short offline	Completed: read failure	90%	4759	920174024
# 6	Short offline	Interrupted (host reset)	00%	4750	-
# 7	Short offline	Interrupted (host reset)	00%	4749	-
# 8	Short offline	Interrupted (host reset)	00%	4747	-
# 9	Short offline	Interrupted (host reset)	00%	4744	-
#10	Short offline	Interrupted (host reset)	00%	4742	-
#11	Short offline	Interrupted (host reset)	00%	4740	-
#12	Short offline	Interrupted (host reset)	00%	4739	-
#13	Short offline	Interrupted (host reset)	00%	4731	-
#14	Short offline	Interrupted (host reset)	00%	4729	-
#15	Short offline	Completed: read failure	10%	4703	920174024
#16	Short offline	Completed: read failure	90%	4698	920174024
#17	Short offline	Interrupted (host reset)	00%	4696	-
#18	Short offline	Completed: read failure	90%	4687	920174024
#19	Short offline	Completed: read failure	90%	4687	920174024
#20	Short offline	Completed: read failure	90%	4687	920174024
#21	Short offline	Completed: read failure	90%	4687	920174024

Can anyone decipher the meanings of the above? Is it worth trying a full factory reset and starting afresh?

 

[Ezra Pound]

I was thinking that maybe the OP on the other thread would confirm (or not) whether the HDD was working when not in the Humax, the fact that your Humax sometimes records and sometimes doesn't would make me think that it is more likely to be a problem with the Humax power supply than a HDD failure

I don't think a factory reset is going to help, but as you have the Custom FirmWare installed, I would try a fix disk

 

[MartinLiddle]

The current pending sector count (attribute 197) needs attention (it should be zero). The rest of the data looks OK and the power on hours are quite low. As Ezra suggests try running fix-disk.

 

[Black Hole]

Hi

Quick Guide to Disk Recovery (click)

 

[prpr]

Can anyone decipher the meanings of the above?

It's got a bit hot. It has some bad sectors. You need to fix those first.

Is it worth trying a full factory reset and starting afresh?

No. Factory reset won't fix the disk. Run fixdisk and then see what the stats. say.
Then format the disk.

Format Storage tells me the disk is too large to format!

You need to reboot into Safe mode from the menu after fixdisk. Then once formatted, reboot again to go back to normal CF mode.

 

[Aaron-B]

Thanks for the tips, everyone. I'm currently running fixdisk (thanks Black Hole for your excellent, clear instructions).

It's been sat at 1-70 for the last hour or so, so I'm now rather worrying it's crashed, but I know it can take an age so will leave it overnight and report back.

Spoiler: Output so far

Running /bin/fix-disk

Checking disk sda (4096 byte sectors)

Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3


Running short disk self test
Error at LBA 920174024

/dev/sda:
re-writing sector 920174024: succeeded
This is an advanced-format disk.
Also checking blocks 920174024 - 920174031 (8 blocks)
Block 920174024 - OK
Block 920174025 - FAILED: Input/output error
- Repaired
Block 920174026 - FAILED: Input/output error
- Repaired
Block 920174027 - FAILED: Input/output error
- Repaired
Block 920174028 - FAILED: Input/output error
- Repaired
Block 920174029 - FAILED: Input/output error
- Repaired
Block 920174030 - FAILED: Input/output error
- Repaired
Block 920174031 - FAILED: Input/output error
- Repaired

Running short disk self test

No pending sectors found - skipping sector repair

Checking partition tables...

MBR Status: MBR only
GPT Status: not present

Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Dev: /dev/sda LBA: 920174024
LBA: 920174024 is on partition /dev/sda2, start: 2104515, bad sector offset: 918 069509
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 920174024 maps to file system block 114758688 on /dev/sda2

Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 114758688 is not in use


Tue Oct 19 18:59:43 BST 2021: Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 240k/0k (157k/84k), time: 6.13/ 1.92/ 2.48
Pass 1: I/O read: 163MB, write: 0MB, rate: 26.58MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 340k/0k (259k/82k), time: 0.01/ 0.00/ 0.01
Pass 2: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 340k/0k (259k/82k), time: 6.79/ 2.18/ 2.53
/lost+found not found. Create? yes

Pass 3A: Memory used: 340k/0k (263k/78k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 340k/0k (262k/79k), time: 0.72/ 0.06/ 0.03
Pass 3: I/O read: 1MB, write: 0MB, rate: 1.38MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 340k/0k (57k/284k), time: 0.98/ 0.98/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 340k/0k (53k/288k), time: 1.84/ 1.84/ 0.00
Pass 5: I/O read: 0MB, write: 0MB, rate: 0.00MB/s

/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****

13 inodes used (0.00%, out of 655776)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 1/1/0
112533 blocks used (4.29%, out of 2622611)
0 bad blocks
1 large file

2 regular files
1 directory
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
3 files
Memory used: 340k/0k (53k/288k), time: 10.43/ 5.07/ 2.57
I/O read: 165MB, write: 1MB, rate: 15.82MB/s
Tue Oct 19 18:59:53 BST 2021

Tue Oct 19 18:59:53 BST 2021: Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectl y set)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 140k/0k (62k/79k), time: 1.78/ 0.24/ 0.47
Pass 1: I/O read: 17MB, write: 0MB, rate: 9.55MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 140k/0k (72k/69k), time: 0.00/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 1059.32MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 140k/0k (72k/69k), time: 2.51/ 0.26/ 0.47
/lost+found not found. Create? yes

Pass 3A: Memory used: 140k/0k (73k/68k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 140k/0k (72k/69k), time: 0.37/ 0.01/ 0.00
Pass 3: I/O read: 1MB, write: 0MB, rate: 2.71MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 140k/0k (51k/90k), time: 0.09/ 0.09/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 140k/0k (50k/91k), time: 0.22/ 0.22/ 0.00
Pass 5: I/O read: 0MB, write: 0MB, rate: 0.00MB/s

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****

14 inodes used (0.02%, out of 65808)
1 non-contiguous file (7.1%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 2/1/0
15599 blocks used (5.93%, out of 263064)
0 bad blocks
1 large file

2 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
4 files
Memory used: 140k/0k (50k/91k), time: 3.27/ 0.60/ 0.48
I/O read: 17MB, write: 1MB, rate: 5.21MB/s
Tue Oct 19 18:59:57 BST 2021

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=b904f60a-f981-40e6-84fe-ef55e70738e2

Tue Oct 19 19:00:40 BST 2021: Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Inode 14590224 has illegal block(s). Clear? yes

Illegal block #65548 (3908500774) in inode 14590224. CLEARED.
Illegal block #65549 (365500743) in inode 14590224. CLEARED.
Illegal block #65550 (3695208277) in inode 14590224. CLEARED.
Illegal block #65551 (3475068230) in inode 14590224. CLEARED.
Illegal block #65552 (2412397037) in inode 14590224. CLEARED.
Illegal block #65553 (3355154414) in inode 14590224. CLEARED.
Illegal block #65554 (3883767149) in inode 14590224. CLEARED.
Illegal block #65555 (2120374638) in inode 14590224. CLEARED.
Illegal block #65556 (532413507) in inode 14590224. CLEARED.
Illegal block #65557 (3107946035) in inode 14590224. CLEARED.
Illegal block #65558 (3418536460) in inode 14590224. CLEARED.
Too many illegal blocks in inode 14590224.
Clear inode? yes

Inode 44811109 has illegal block(s). Clear? yes

Illegal block #47119 (536903166) in inode 44811109. CLEARED.
Illegal block #47127 (536903166) in inode 44811109. CLEARED.
Illegal block #47135 (536903166) in inode 44811109. CLEARED.
Illegal block #47143 (536903166) in inode 44811109. CLEARED.
Illegal block #47151 (536903166) in inode 44811109. CLEARED.
Illegal block #47159 (536903166) in inode 44811109. CLEARED.
Illegal block #47167 (536609129) in inode 44811109. CLEARED.
Illegal block #47175 (536870912) in inode 44811109. CLEARED.
Illegal block #47183 (536870912) in inode 44811109. CLEARED.
Illegal block #47191 (536870918) in inode 44811109. CLEARED.
Illegal block #47199 (536870912) in inode 44811109. CLEARED.
Too many illegal blocks in inode 44811109.
Clear inode? yes

Pass 1: Memory used: 1032k/9432k (631k/402k), time: 1787.56/947.71/163.71
Pass 1: I/O read: 15054MB, write: 1MB, rate: 8.42MB/s
Restarting e2fsck from the beginning...
Pass 1: Checking inodes, blocks, and sizes

Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 8: 5760 5761 5762 5763 5764 5765 5766 5767 57 68 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 57 84 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 58 00 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 58 16 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 58 32 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 58 48 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 58 64 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 58 80 5881 5882 5883 5884 5885 5886 5887
Multiply-claimed block(s) in inode 14590440: 79579136
Multiply-claimed block(s) in inode 19890177: 79579136
Multiply-claimed block(s) in inode 44811110: 5760 5761 5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 5784 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 5864 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 5880 5881 5882 5883 5884 5885 5886 5887
Pass 1b: Memory used: 1032k/9432k (694k/339k), time: 1097.92/349.45/186.46
Pass 1b: I/O read: 15054MB, write: 0MB, rate: 13.71MB/s
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1c: Memory used: 1032k/9432k (694k/339k), time: 0.74/ 0.03/ 0.04
Pass 1c: I/O read: 2MB, write: 0MB, rate: 2.72MB/s
Pass 1D: Reconciling multiply-claimed blocks
(There are 3 inodes containing multiply-claimed blocks.)

File <The journal inode> (inode #8, mod time Tue Oct 19 15:49:22 2021)
has 128 multiply-claimed block(s), shared with 1 file(s):
... (inode #44811110, mod time Wed Apr 27 19:31:02 2016)
Clone multiply-claimed blocks? yes

File ... (inode #14590440, mod time Fri Jan 8 20:02:55 2016)
has 1 multiply-claimed block(s), shared with 1 file(s):
/virtual_disk (inode #19890177, mod time Tue Oct 19 16:57:20 2021)
Clone multiply-claimed blocks? yes

 

[Aaron-B]

And just like that it completed.

Spoiler: Final output

File /virtual_disk (inode #19890177, mod time Tue Oct 19 16:57:20 2021)
has 1 multiply-claimed block(s), shared with 1 file(s):
... (inode #14590440, mod time Fri Jan 8 20:02:55 2016)
Multiply-claimed blocks already reassigned or cloned.

File ... (inode #44811110, mod time Wed Apr 27 19:31:02 2016)
has 128 multiply-claimed block(s), shared with 1 file(s):
<The journal inode> (inode #8, mod time Tue Oct 19 15:49:22 2021)
Multiply-claimed blocks already reassigned or cloned.

Pass 1d: Memory used: 1032k/9432k (987k/46k), time: 5142.58/5001.19/ 2.64
Pass 1d: I/O read: 59MB, write: 1MB, rate: 0.01MB/s
hmx_int_stor: e2fsck canceled.

hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
Memory used: 1032k/9432k (925k/108k), time: 10004.92/7339.00/517.56
I/O read: 30168MB, write: 30MB, rate: 3.02MB/s
Tue Oct 19 21:47:26 BST 2021
Removing extra swap space.

Finished
fix-disk: session terminated with exit status 0

So some fixes and modifications have taken place. Probably not surprising there may be those handful of dead sectors on the disk, given it's obviously not a brand new device.

Having booted back into normality, I run the HDD Test successfully and it passes with "no defects found". Phew.

 

[MartinLiddle]

And just like that it completed.

Could you show us the SMART data now please?

 

[Aaron-B]

Could you show us the SMART data now please?

Of course; apologies for the delay, and thanks again to everyone who's advised so far. 'Just' that reallocated sector (line 5) now.

Disk Information

SMART Status	PASSED
Model Family	Seagate Video 3.5 HDD
Device Model	ST1000VM002-1CT162
Serial Number	W1G0EW3Z
LU WWN Device Id	5 000c50 05c5e9bdd
Firmware Version	SC23
User Capacity	1,000,204,886,016 bytes [1.00 TB]
Sector Sizes	512 bytes logical, 4096 bytes physical
Rotation Rate	5900 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	Sat Oct 23 13:32:04 2021 BST
SMART support is	Available - device has SMART capability.
SMART support is	Enabled

Attributes

ID	Name	Flags	Raw Value	Value	Worst	Threshold	Life Left	Notes
1	Raw_Read_Error_Rate	POSR--	149525984	117	077	006		-
3	Spin_Up_Time	PO----	0	097	097	000		-
4	Start_Stop_Count	-O--CK	2404	098	098	020	98%	-
5	Reallocated_Sector_Ct	PO--CK	16	100	100	036	100%	-
7	Seek_Error_Rate	POSR--	132218586	081	060	030		-
9	Power_On_Hours	-O--CK	4769	095	095	000	95%	-
10	Spin_Retry_Count	PO--C-	0	100	100	097	100%	-
12	Power_Cycle_Count	-O--CK	2405	098	098	020	98%	-
184	End-to-End_Error	-O--CK	0	100	100	099		-
187	Reported_Uncorrect	-O--CK	1480	001	001	000		-
188	Command_Timeout	-O--CK	0	100	100	000		-
189	High_Fly_Writes	-O-RCK	3	097	097	000		-
190	Airflow_Temperature_Cel	-O---K	35	065 (35°C)	034 (66°C)	045 (55°C)		In_the_past
191	G-Sense_Error_Rate	-O--CK	0	100	100	000		-
192	Power-Off_Retract_Count	-O--CK	2403	099	099	000	99%	-
193	Load_Cycle_Count	-O--CK	2404	099	099	000	99%	-
194	Temperature_Celsius	-O---K	35	035	066	000		-
197	Current_Pending_Sector	-O--C-	0	100	100	000		-
198	Offline_Uncorrectable	----C-	0	100	100	000		-
199	UDMA_CRC_Error_Count	-OSRCK	0	200	200	000		-

Self-test logs

No.	Description	Status	Remaining	When	First Error LBA
# 1	Short offline	Completed without error	00%	4764	-
# 2	Short offline	Completed without error	00%	4761	-
# 3	Short offline	Completed: read failure	90%	4761	920174024
# 4	Short offline	Completed: read failure	90%	4760	920174024
# 5	Short offline	Completed: read failure	90%	4760	920174024
# 6	Short offline	Completed: read failure	90%	4759	920174024
# 7	Short offline	Completed: read failure	90%	4759	920174024
# 8	Short offline	Completed: read failure	90%	4759	920174024
# 9	Short offline	Interrupted (host reset)	00%	4750	-
#10	Short offline	Interrupted (host reset)	00%	4749	-
#11	Short offline	Interrupted (host reset)	00%	4747	-
#12	Short offline	Interrupted (host reset)	00%	4744	-
#13	Short offline	Interrupted (host reset)	00%	4742	-
#14	Short offline	Interrupted (host reset)	00%	4740	-
#15	Short offline	Interrupted (host reset)	00%	4739	-
#16	Short offline	Interrupted (host reset)	00%	4731	-
#17	Short offline	Interrupted (host reset)	00%	4729	-
#18	Short offline	Completed: read failure	10%	4703	920174024
#19	Short offline	Completed: read failure	90%	4698	920174024
#20	Short offline	Interrupted (host reset)	00%	4696	-
#21	Short offline	Completed: read failure	90%	4687	920174024

 

[MartinLiddle]

Of course; apologies for the delay, and thanks again to everyone who's advised so far. 'Just' that reallocated sector (line 5) now.

The reallocated sector count of 16 is not a concern; start worrying if it gets above a thousand. I would say the drive now looks in very good condition.

 

[Aaron-B]

Thanks Martin, that's what I thought but very good to have it confirmed. Appreciate your time.