It is possible but I thought we had seen reported power on hours over 40,000 hours on these drives?
Ways to repair or time to replace? - Solved
- Thread starter gebbly
- Start date
Hi All,
Thanks so much for all the help everyone. I got back to my machine today and things are looking a little better. The fixdisk run has completed and looks like it has fixed some issues and left others. When I then set the box in stand by with the remote the noise of the disk spinning down is back. Since this problem started when spinning down it would make those noises for about 3 seconds, now its back to doing them for a minute or so. Most importantly I am now able to get back into the media menu on the box Hurrah!
Going back to the web interface I still get :
!! WARNING !!
There are potential hardware problems with the internal hard disk on this device.
Disk pending sector count is: 2
Disk offline sector count is: 2
So I will run another fixdisk overnight tonight to see if it can fix anything further. From the web interface I was able to go to the media section and see all the recordings. I will be following the guide at https://wiki.hummy.tv/wiki/2TB_Disk_Installation_Blog as I am no longer 100% confident in the stability of the drive and will swap it out for a new one before it fails again.
In case anyone is able to get further information from the output of the fixdisk I include it below (I think I need to delete some corrupted "Upstart Crow" and "Andromeda" recordings?) :
Thanks so much for all the help everyone. I got back to my machine today and things are looking a little better. The fixdisk run has completed and looks like it has fixed some issues and left others. When I then set the box in stand by with the remote the noise of the disk spinning down is back. Since this problem started when spinning down it would make those noises for about 3 seconds, now its back to doing them for a minute or so. Most importantly I am now able to get back into the media menu on the box Hurrah!
Going back to the web interface I still get :
!! WARNING !!
There are potential hardware problems with the internal hard disk on this device.
Disk pending sector count is: 2
Disk offline sector count is: 2
So I will run another fixdisk overnight tonight to see if it can fix anything further. From the web interface I was able to go to the media section and see all the recordings. I will be following the guide at https://wiki.hummy.tv/wiki/2TB_Disk_Installation_Blog as I am no longer 100% confident in the stability of the drive and will swap it out for a new one before it fails again.
In case anyone is able to get further information from the output of the fixdisk I include it below (I think I need to delete some corrupted "Upstart Crow" and "Andromeda" recordings?) :
Code:
Please select option: fixdisk
Any additional options (-h for list or press return for none): -d -l -y
Are you sure you wish to run the hard disk checker (-d -l -y)? [Y/N] Y
Running /bin/fix-disk
PART: [3 1 2]
FSCKOPTS: []
Checking disk sda (512 byte sectors)
Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3
Running long disk self test
Error at LBA 862996781
/dev/sda:
re-writing sector 862996781: succeeded
Running select disk self test
Error at LBA 862998043
/dev/sda:
re-writing sector 862998043: succeeded
Running select disk self test
Error at LBA 862999045
/dev/sda:
re-writing sector 862999045: succeeded
Running select disk self test
Error at LBA 1625827723
/dev/sda:
re-writing sector 1625827723: succeeded
Running select disk self test
Error at LBA 1625827724
/dev/sda:
re-writing sector 1625827724: succeeded
Running select disk self test
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: 862996781
LBA: 862996781 is on partition /dev/sda2, start: 2104515, bad sector offset: 860892266
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 862996781 maps to file system block 107611533 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 107611533 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 26599452
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
ncheck: EXT2 directory corrupted while calling ext2_dir_iterate
Inode Pathname
26599452 /mnt/hd2/My Video/Upstart Crow/Upstart Crow_20171016_2020.ts
Dev: /dev/sda LBA: 862998043
LBA: 862998043 is on partition /dev/sda2, start: 2104515, bad sector offset: 860893528
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 862998043 maps to file system block 107611691 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 107611691 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 26599452
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
ncheck: EXT2 directory corrupted while calling ext2_dir_iterate
Inode Pathname
26599452 /mnt/hd2/My Video/Upstart Crow/Upstart Crow_20171016_2020.ts
Dev: /dev/sda LBA: 862999045
LBA: 862999045 is on partition /dev/sda2, start: 2104515, bad sector offset: 860894530
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 862999045 maps to file system block 107611816 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 107611816 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 26599452
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
ncheck: EXT2 directory corrupted while calling ext2_dir_iterate
Inode Pathname
26599452 /mnt/hd2/My Video/Upstart Crow/Upstart Crow_20171016_2020.ts
Dev: /dev/sda LBA: 1625827723
LBA: 1625827723 is on partition /dev/sda2, start: 2104515, bad sector offset: 1623723208
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 1625827723 maps to file system block 202965401 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 202965401 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Block Inode number 202965401 <block not found>
Dev: /dev/sda LBA: 1625827724
LBA: 1625827724 is on partition /dev/sda2, start: 2104515, bad sector offset: 1623723209
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 1625827724 maps to file system block 202965401 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 202965401 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Block Inode number 202965401 <block not found>
Fri Oct 20 20:48:54 BST 2017: 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: 7.33/ 2.49/ 2.60
Pass 1: I/O read: 164MB, write: 0MB, rate: 22.38MB/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: 7.94/ 2.75/ 2.66
/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.73/ 0.08/ 0.02
Pass 3: I/O read: 1MB, write: 0MB, rate: 1.37MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 340k/0k (57k/284k), time: 1.01/ 0.97/ 0.01
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.90/ 1.86/ 0.00
Pass 5: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
15 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: 2/2/0
177971 blocks used (6.79%, out of 2622611)
0 bad blocks
1 large file
4 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
------------
5 files
Memory used: 340k/0k (53k/288k), time: 11.75/ 5.67/ 2.71
I/O read: 165MB, write: 1MB, rate: 14.12MB/s
Fri Oct 20 20:49:06 BST 2017
Fri Oct 20 20:49:06 BST 2017: Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 140k/0k (62k/79k), time: 0.80/ 0.23/ 0.41
Pass 1: I/O read: 17MB, write: 0MB, rate: 21.21MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 140k/0k (72k/69k), time: 0.01/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 79.93MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 140k/0k (72k/69k), time: 0.93/ 0.26/ 0.41
/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.09/ 0.01/ 0.01
Pass 3: I/O read: 1MB, write: 0MB, rate: 11.19MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 140k/0k (51k/90k), time: 0.11/ 0.11/ 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.26/ 0.25/ 0.01
Pass 5: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
15 inodes used (0.02%, out of 65808)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 2/2/0
16843 blocks used (6.40%, out of 263064)
0 bad blocks
1 large file
3 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
------------
5 files
Memory used: 140k/0k (50k/91k), time: 1.40/ 0.63/ 0.44
I/O read: 17MB, write: 1MB, rate: 12.11MB/s
Fri Oct 20 20:49:08 BST 2017
Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=a2c02ee5-5cb9-4032-bb1d-4a5b6d0d364b
Fri Oct 20 20:49:33 BST 2017: Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 8044546 has zero dtime. Fix? yes
Pass 1: Memory used: 1420k/9432k (794k/627k), time: 3570.11/2082.78/192.09
Pass 1: I/O read: 15380MB, write: 1MB, rate: 4.31MB/s
Pass 2: Checking directory structure
Entry 'New_ Andromeda_20150520_1855.ts' in /My Video/Andromeda (26599644) has deleted/unused inode
26601199. Clear? yes
Entry 'New_ Andromeda_20150520_1855.nts' in /My Video/Andromeda (26599644) has deleted/unused inode
26601200. Clear? yes
Directory inode 26600738, block #6, offset 0: directory corrupted
Salvage? yes
Pass 2: Memory used: 1420k/18864k (783k/638k), time: 1.49/ 0.62/ 0.14
Pass 2: I/O read: 4MB, write: 1MB, rate: 2.68MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 1420k/18864k (783k/638k), time: 3613.84/2123.52/192.39
/lost+found not found. Create? yes
Pass 3A: Memory used: 1420k/18864k (1157k/264k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 1420k/18864k (1143k/278k), time: 64.67/ 6.12/ 2.38
Pass 3: I/O read: 58MB, write: 1MB, rate: 0.90MB/s
Pass 4: Checking reference counts
Unattached inode 26599595
Connect to /lost+found? yes
Inode 26599595 ref count is 2, should be 1. Fix? yes
Unattached inode 26599609
Connect to /lost+found? yes
Inode 26599609 ref count is 2, should be 1. Fix? yes
Unattached inode 26599718
Connect to /lost+found? yes
Inode 26599718 ref count is 2, should be 1. Fix? yes
Unattached inode 26600258
Connect to /lost+found? yes
Inode 26600258 ref count is 2, should be 1. Fix? yes
Unattached inode 26600346
Connect to /lost+found? yes
Inode 26600346 ref count is 2, should be 1. Fix? yes
Unattached inode 26600388
Connect to /lost+found? yes
Inode 26600388 ref count is 2, should be 1. Fix? yes
Unattached inode 26600403
Connect to /lost+found? yes
Inode 26600403 ref count is 2, should be 1. Fix? yes
Unattached inode 26600531
Connect to /lost+found? yes
Inode 26600531 ref count is 2, should be 1. Fix? yes
Unattached inode 26600892
Connect to /lost+found? yes
Inode 26600892 ref count is 2, should be 1. Fix? yes
Unattached inode 26600911
Connect to /lost+found? yes
Inode 26600911 ref count is 2, should be 1. Fix? yes
Unattached inode 26600934
Connect to /lost+found? yes
Inode 26600934 ref count is 2, should be 1. Fix? yes
Unattached inode 26601082
Connect to /lost+found? yes
Inode 26601082 ref count is 2, should be 1. Fix? yes
Unattached inode 26601212
Connect to /lost+found? yes
Inode 26601212 ref count is 2, should be 1. Fix? yes
Unattached inode 26601238
Connect to /lost+found? yes
Inode 26601238 ref count is 2, should be 1. Fix? yes
Unattached inode 26601267
Connect to /lost+found? yes
Inode 26601267 ref count is 2, should be 1. Fix? yes
Unattached inode 26601284
Connect to /lost+found? yes
Inode 26601284 ref count is 2, should be 1. Fix? yes
Unattached inode 26601304
Connect to /lost+found? yes
Inode 26601304 ref count is 2, should be 1. Fix? yes
Unattached inode 26601355
Connect to /lost+found? yes
Inode 26601355 ref count is 2, should be 1. Fix? yes
Unattached inode 26601386
Connect to /lost+found? yes
Inode 26601386 ref count is 2, should be 1. Fix? yes
Unattached inode 26601425
Connect to /lost+found? yes
Inode 26601425 ref count is 2, should be 1. Fix? yes
Unattached inode 26601440
Connect to /lost+found? yes
Inode 26601440 ref count is 2, should be 1. Fix? yes
Unattached inode 26601452
Connect to /lost+found? yes
Inode 26601452 ref count is 2, should be 1. Fix? yes
Unattached inode 26601470
Connect to /lost+found? yes
Inode 26601470 ref count is 2, should be 1. Fix? yes
Pass 4: Memory used: 1420k/0k (1103k/318k), time: 143.67/140.74/ 0.43
Pass 4: I/O read: 1MB, write: 1MB, rate: 0.01MB/s
Pass 5: Checking group summary information
Block bitmap differences: -(23398196--23398211) -23877247 -(23878338--23878343) -(23882382--238823
83) -(27833108--27833292) -(27957423--27957821) -(28049922--28049927) -(28060764--28082175) -(28082
696--28114943) -(28115464--28147711) -(28148232--28180479) -(28181000--28213247) -(28213768--282460
15) -(28246536--28256736) -(28256886--28260630) -(28262450--28263476) -(28264504--28265530) -(28266
558--28267584) -(28269639--28270665) -(28272720--28273746) -(28274774--28275800) -(28277855--282787
83) -(28279909--28280935) -(28281963--28282989) -(28284017--28284500) -(28284752--28286070) -(28287
098--28288124) -(28289152--28290178) -(28292233--28293259) -(28294287--28295313) -(28296341--282973
67) -(28299422--28300448) -(28301476--28302502) -(28303530--28304556) -(28306611--28307637) -(28308
665--28309691) -(28310719--28311551) -(28312072--28312772) -(28313800--28314826) -(28315854--283179
07) -(28318935--28319961) -(28320989--28322015) -(28323043--28324069) -(28325097--28326123) -(28328
178--28329204) -(28330232--28331258) -(28332286--28333312) -(28334340--28335366) -(28337437--283384
63) -(28339491--28340517) -(28341545--28342571) -(28343599--28344319) -(28345653--28346679) -(28348
734--28349760) -(28350788--28351814) -(28352874--28353900) -(28354928--28355954) -(28356982--283580
08) -(28360063--28362116) -(28363144--28364170) -(28365198--28367251) -(28368279--28369305) -(28370
333--28371359) -(28372387--28373413) -(28374441--28376494) -(28378549--28379575) -(28380667--283816
93) -(28696742--28698795) -(28699823--28700849) -(28701877--28703930) -(28705288--28705984) -(28707
016--28737535) -(28738056--28770303) -(28770824--28775834) -(32200704--32200706) -(203227650--20322
7655) -(206701058--206701063) -(206733826--206733831) -(208595313--208595319) -(212249145--21224915
1)
Fix? yes
Free blocks count wrong for group #714 (0, counted=16).
Fix? yes
Free blocks count wrong for group #728 (31416, counted=31425).
Fix? yes
Free blocks count wrong for group #849 (32069, counted=32254).
Fix? yes
Free blocks count wrong for group #853 (24506, counted=24905).
Fix? yes
Free blocks count wrong for group #856 (10836, counted=32254).
Fix? yes
Free blocks count wrong for group #857 (6, counted=32254).
Fix? yes
Free blocks count wrong for group #858 (6, counted=32254).
Fix? yes
Free blocks count wrong for group #859 (6, counted=32254).
Fix? yes
Free blocks count wrong for group #860 (6, counted=32254).
Fix? yes
Free blocks count wrong for group #861 (6, counted=32254).
Fix? yes
Free blocks count wrong for group #862 (0, counted=21037).
Fix? yes
Free blocks count wrong for group #863 (6, counted=14966).
Fix? yes
Free blocks count wrong for group #864 (6, counted=15806).
Fix? yes
Free blocks count wrong for group #865 (14067, counted=30499).
Fix? yes
Free blocks count wrong for group #866 (30074, counted=32128).
Fix? yes
Free blocks count wrong for group #875 (0, counted=5135).
Fix? yes
Free blocks count wrong for group #876 (0, counted=31217).
Fix? yes
Free blocks count wrong for group #877 (6, counted=32254).
Fix? yes
Free blocks count wrong for group #878 (6, counted=5017).
Fix? yes
Free blocks count wrong for group #982 (20464, counted=20467).
Fix? yes
Free blocks count wrong for group #6202 (0, counted=6).
Fix? yes
Free blocks count wrong for group #6308 (0, counted=6).
Fix? yes
Free blocks count wrong for group #6309 (0, counted=6).
Fix? yes
Free blocks count wrong for group #6365 (6610, counted=6617).
Fix? yes
Free blocks count wrong for group #6477 (0, counted=7).
Fix? yes
Free blocks count wrong (69058175, counted=69385371).
Fix? yes
Inode bitmap differences: -8044546 -(26601199--26601200)
Fix? yes
Free inodes count wrong for group #982 (8187, counted=8188).
Fix? yes
Free inodes count wrong for group #3247 (6323, counted=6325).
Fix? yes
Free inodes count wrong (60326236, counted=60326239).
Fix? yes
Pass 5: Memory used: 1420k/0k (729k/692k), time: 429.48/419.71/ 1.10
Pass 5: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
7841 inodes used (0.01%, out of 60334080)
940 non-contiguous files (12.0%)
14 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 1255/612/1
171918961 blocks used (71.25%, out of 241304332)
0 bad blocks
38 large files
6473 regular files
312 directories
0 character device files
0 block device files
0 fifos
0 links
1046 symbolic links (1046 fast symbolic links)
0 sockets
------------
7808 files
Memory used: 1420k/0k (729k/692k), time: 4289.54/2690.55/197.07
I/O read: 15442MB, write: 58MB, rate: 3.61MB/s
Fri Oct 20 22:01:03 BST 2017
Removing extra swap space.
Finished
fix-disk: session terminated with exit status 0
prpr
Well-Known Member
You need to post your SMART stats. again.
That would seem like a sensible thing to do.
You don't need to do that. The latest firmware handles it. What version of CF are you running?
I'm not even sure you need a new disk yet - you just had filesystem corruption and a few bad sectors.
The new SMART page says :
"The latest firmware handles it" Do you mean that all I would need to do is put the new disk in, reinstall CF and the CF would ensure it is formatted correctly with sectors aligned etc?
"What version of CF are you running?" I installed the latest version "Custom firmware version: 3.13 (build 4028)"
Code:
SMART data read from device /dev/sda
Disk Information
SMART Status PASSED
Model Family Seagate Pipeline HD 5900.2
Device Model ST31000424CS
Serial Number 9VX18040
LU WWN Device Id 5 000c50 02d78968e
Firmware Version SC13
User Capacity 1,000,204,886,016 bytes [1.00 TB]
Sector Size 512 bytes logical/physical
Rotation Rate 5900 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, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is Mon Oct 23 18:44:58 2017 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-- 2128042 102 099 006
-
3 Spin_Up_Time PO---- 0 100 100 000
-
4 Start_Stop_Count -O--CK 1 100 100 020 100% -
5 Reallocated_Sector_Ct PO--CK 0 100 100 036 100% -
7 Seek_Error_Rate POSR-- 0 100 253 030
-
9 Power_On_Hours -O--CK 10352 089 089 000 89% -
10 Spin_Retry_Count PO--C- 0 100 100 097 100% -
12 Power_Cycle_Count -O--CK 4902 096 096 020 95% -
184 End-to-End_Error -O--CK 0 100 100 099
-
187 Reported_Uncorrect -O--CK 274 001 001 000
-
188 Command_Timeout -O--CK 4295032833 100 100 000
-
189 High_Fly_Writes -O-RCK 64 036 036 000
-
190 Airflow_Temperature_Cel -O---K 51 049 (51°C) 045 (55°C) 045 (55°C)
In_the_past
194 Temperature_Celsius -O---K 51 051 055 000
-
195 Hardware_ECC_Recovered -O-RC- 2128042 011 008 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 Selective offline Completed without error 00% 10355 -
# 2 Selective offline Completed: read failure 90% 10354 1625827724
# 3 Selective offline Completed: read failure 90% 10354 1625827723
# 4 Selective offline Completed: read failure 90% 10353 862999045
# 5 Selective offline Completed: read failure 90% 10353 862998043
# 6 Extended offline Completed: read failure 60% 10353 862996781
# 7 Short offline Completed without error 00% 10352 -
# 8 Short offline Completed without error 00% 10351 -
# 9 Short offline Completed: read failure 70% 10351 863870178
#10 Short offline Completed: read failure 60% 10349 863870177
#11 Short offline Completed: read failure 80% 10347 863870176
#12 Short offline Completed: read failure 80% 10345 863870175
#13 Short offline Completed: read failure 50% 10343 863870174
#14 Short offline Completed without error 00% 10341 -
#15 Short offline Completed without error 00% 10341 -
#16 Short offline Completed without error 00% 10341 -
#17 Short offline Completed without error 00% 10341 -
#18 Short offline Completed without error 00% 10341 -
#19 Short offline Completed without error 00% 10341 -
#20 Short offline Completed without error 00% 10341 -
#21 Short offline Completed without error 00% 10341 -"The latest firmware handles it" Do you mean that all I would need to do is put the new disk in, reinstall CF and the CF would ensure it is formatted correctly with sectors aligned etc?
"What version of CF are you running?" I installed the latest version "Custom firmware version: 3.13 (build 4028)"
prpr
Well-Known Member
Your marginal sectors have gone away without being reallocated.
I would run through the fixdisk process again, to make sure it is clean, and then (like I said) keep an eye on things periodically.
If you start having more trouble, then it's probably worth looking at an alt. disk, otherwise not.
You don't need to reinstall the CF - that is in flash. You would need to reinstall the WebIf and all packages and (almost all) settings, as they are held on disk.
I would run through the fixdisk process again, to make sure it is clean, and then (like I said) keep an eye on things periodically.
If you start having more trouble, then it's probably worth looking at an alt. disk, otherwise not.
The on-screen interface handles formatting of blank disks and it does work properly with disks up to 2TB.
You don't need to reinstall the CF - that is in flash. You would need to reinstall the WebIf and all packages and (almost all) settings, as they are held on disk.
Last edited:
Black Hole
May contain traces of nut
I think he means TB. The "2TB blog" started when the Humax menus could only cope with 1TB. Now you only need CF help for drives over 2TB.
Replacing the drive with CF in flash results in you getting the package download page when you try to access the WebIF web page - WebIF etc will then install and after that you can tailor your optional package set.
I'd agree with BennyBoy, the CF is fantastic.
After a second fixdisk my disk doesnt report any errors
And SMART says :
I appreciate what prpr says about the HDD being ok for now. But I'm a little concerned that if it fails again and next time the recordings are unrecoverable so I have a new pipeline 2TB HDD on order.
Thanks so much everyone for all the help. I may post a new topic soon when I bungle the HDD upgrade
After a second fixdisk my disk doesnt report any errors
Code:
Please select option: fixdisk
Any additional options (-h for list or press return for none): -d -l -y
Are you sure you wish to run the hard disk checker (-d -l -y)? [Y/N] y
Running /bin/fix-disk
PART: [3 1 2]
FSCKOPTS: []
Checking disk sda (512 byte sectors)
Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3
Running long disk self test
No pending sector errors found
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
Tue Oct 24 02:02:48 BST 2017: 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: 7.39/ 2.51/ 2.60
Pass 1: I/O read: 164MB, write: 0MB, rate: 22.18MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 340k/0k (259k/82k), time: 0.01/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 104.11MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 340k/0k (260k/81k), time: 8.01/ 2.78/ 2.65
Pass 3A: Memory used: 340k/0k (259k/82k), 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 (259k/82k), time: 0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 340k/0k (53k/288k), time: 1.00/ 0.97/ 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: 2.66/ 1.93/ 0.05
Pass 5: I/O read: 1MB, write: 0MB, rate: 0.38MB/s
16 inodes used (0.00%, out of 655776)
1 non-contiguous file (6.3%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 2/2/0
177974 blocks used (6.79%, out of 2622611)
0 bad blocks
1 large file
5 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
------------
7 files
Memory used: 340k/0k (53k/288k), time: 11.71/ 5.69/ 2.71
I/O read: 165MB, write: 1MB, rate: 14.10MB/s
Tue Oct 24 02:03:00 BST 2017
Tue Oct 24 02:03:00 BST 2017: Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 140k/0k (62k/79k), time: 0.81/ 0.23/ 0.43
Pass 1: I/O read: 17MB, write: 0MB, rate: 20.95MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 140k/0k (72k/69k), time: 0.02/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 44.40MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 140k/0k (72k/69k), time: 0.94/ 0.26/ 0.44
Pass 3A: Memory used: 140k/0k (72k/69k), 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 (71k/70k), time: 0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 140k/0k (50k/91k), time: 0.14/ 0.13/ 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.34/ 0.26/ 0.00
Pass 5: I/O read: 1MB, write: 0MB, rate: 2.95MB/s
15 inodes used (0.02%, out of 65808)
1 non-contiguous file (6.7%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 2/2/0
16837 blocks used (6.40%, out of 263064)
0 bad blocks
1 large file
3 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
6 files
Memory used: 140k/0k (50k/91k), time: 1.43/ 0.65/ 0.45
I/O read: 17MB, write: 1MB, rate: 11.88MB/s
Tue Oct 24 02:03:02 BST 2017
Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=aa3059ad-8e96-4ac1-9e5d-7bd08d7107c2
Tue Oct 24 02:03:27 BST 2017: Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 1428k/9432k (799k/630k), time: 3561.42/2074.16/192.75
Pass 1: I/O read: 15380MB, write: 0MB, rate: 4.32MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 1428k/18864k (786k/643k), time: 1.83/ 0.71/ 0.16
Pass 2: I/O read: 4MB, write: 0MB, rate: 2.19MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 1428k/18864k (786k/643k), time: 3605.56/2114.96/193.04
Pass 3A: Memory used: 1428k/18864k (798k/631k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 1428k/18864k (781k/648k), time: 0.07/ 0.04/ 0.00
Pass 3: I/O read: 1MB, write: 0MB, rate: 15.30MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 1428k/0k (738k/691k), time: 139.07/135.58/ 0.29
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 1428k/0k (726k/703k), time: 334.15/268.94/ 3.12
Pass 5: I/O read: 58MB, write: 0MB, rate: 0.17MB/s
9053 inodes used (0.02%, out of 60334080)
956 non-contiguous files (10.6%)
16 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 1354/613/1
171928308 blocks used (71.25%, out of 241304332)
0 bad blocks
38 large files
7614 regular files
381 directories
0 character device files
0 block device files
0 fifos
0 links
1049 symbolic links (1049 fast symbolic links)
0 sockets
------------
9044 files
Memory used: 1428k/0k (726k/703k), time: 4078.93/2519.51/196.47
I/O read: 15443MB, write: 1MB, rate: 3.79MB/s
Tue Oct 24 03:11:27 BST 2017
Removing extra swap space.
Finished
fix-disk: session terminated with exit status 0And SMART says :
Code:
Disk Information
SMART Status PASSED
Model Family Seagate Pipeline HD 5900.2
Device Model ST31000424CS
Serial Number 9VX18040
LU WWN Device Id 5 000c50 02d78968e
Firmware Version SC13
User Capacity 1,000,204,886,016 bytes [1.00 TB]
Sector Size 512 bytes logical/physical
Rotation Rate 5900 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, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is Tue Oct 24 07:35:37 2017 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-- 1447444 100 099 006
-
3 Spin_Up_Time PO---- 0 100 100 000
-
4 Start_Stop_Count -O--CK 1 100 100 020 100% -
5 Reallocated_Sector_Ct PO--CK 0 100 100 036 100% -
7 Seek_Error_Rate POSR-- 0 100 253 030
-
9 Power_On_Hours -O--CK 10352 089 089 000 89% -
10 Spin_Retry_Count PO--C- 0 100 100 097 100% -
12 Power_Cycle_Count -O--CK 4904 096 096 020 95% -
184 End-to-End_Error -O--CK 0 100 100 099
-
187 Reported_Uncorrect -O--CK 274 001 001 000
-
188 Command_Timeout -O--CK 4295032833 100 100 000
-
189 High_Fly_Writes -O-RCK 64 036 036 000
-
190 Airflow_Temperature_Cel -O---K 35 065 (35°C) 045 (55°C) 045 (55°C)
In_the_past
194 Temperature_Celsius -O---K 35 035 055 000
-
195 Hardware_ECC_Recovered -O-RC- 1447444 008 008 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 Extended offline Completed without error 00% 10355 -
# 2 Selective offline Completed without error 00% 10355 -
# 3 Selective offline Completed: read failure 90% 10354 1625827724
# 4 Selective offline Completed: read failure 90% 10354 1625827723
# 5 Selective offline Completed: read failure 90% 10353 862999045
# 6 Selective offline Completed: read failure 90% 10353 862998043
# 7 Extended offline Completed: read failure 60% 10353 862996781
# 8 Short offline Completed without error 00% 10352 -
# 9 Short offline Completed without error 00% 10351 -
#10 Short offline Completed: read failure 70% 10351 863870178
#11 Short offline Completed: read failure 60% 10349 863870177
#12 Short offline Completed: read failure 80% 10347 863870176
#13 Short offline Completed: read failure 80% 10345 863870175
#14 Short offline Completed: read failure 50% 10343 863870174
#15 Short offline Completed without error 00% 10341 -
#16 Short offline Completed without error 00% 10341 -
#17 Short offline Completed without error 00% 10341 -
#18 Short offline Completed without error 00% 10341 -
#19 Short offline Completed without error 00% 10341 -
#20 Short offline Completed without error 00% 10341 -
#21 Short offline Completed without error 00% 10341 -I appreciate what prpr says about the HDD being ok for now. But I'm a little concerned that if it fails again and next time the recordings are unrecoverable so I have a new pipeline 2TB HDD on order.
Thanks so much everyone for all the help. I may post a new topic soon when I bungle the HDD upgrade
Morning all,
Back to issues with the box I'm afraid. Turned it on this morning and when I went into "Media" and tried to start playing a recording the screen went black as though it were about to play and then immediately went back to the previous menu screen. I shut the box down and restarted and this time when I started playing a recording it started and played for a few seconds and then froze. I shut down and restarted yet again and this time the box powered up and then I got a message pop up on the screen saying the box needed to be formatted before I could start recording. It took me to the drive menu where you can format disks and showed the drive use at 0%. I rebooted once more and the box recognises there is content again but at this point the drive has me really concerned and the new drive turned up yesterday so I will be replacing it today.
Thanks to prpr I understand that I dont need to plug the drive into a pc and manually format it anymore and the humax menus on the TV screen are capable of formatting a 2TB drive. I went with the suggestion on the 2TB installation blog page I posted earlier and have bought a "Seagate Pipeline HD 2TB Drive (ST2000VM002/3)".
Prpr, when you say the tv menus can handle the format will they take care of the details like aligning the partitions or should I do something about that?
Is there anything else I need to be aware of whilst doint the upgrade?
Back to issues with the box I'm afraid. Turned it on this morning and when I went into "Media" and tried to start playing a recording the screen went black as though it were about to play and then immediately went back to the previous menu screen. I shut the box down and restarted and this time when I started playing a recording it started and played for a few seconds and then froze. I shut down and restarted yet again and this time the box powered up and then I got a message pop up on the screen saying the box needed to be formatted before I could start recording. It took me to the drive menu where you can format disks and showed the drive use at 0%. I rebooted once more and the box recognises there is content again but at this point the drive has me really concerned and the new drive turned up yesterday so I will be replacing it today.
Thanks to prpr I understand that I dont need to plug the drive into a pc and manually format it anymore and the humax menus on the TV screen are capable of formatting a 2TB drive. I went with the suggestion on the 2TB installation blog page I posted earlier and have bought a "Seagate Pipeline HD 2TB Drive (ST2000VM002/3)".
Prpr, when you say the tv menus can handle the format will they take care of the details like aligning the partitions or should I do something about that?
Is there anything else I need to be aware of whilst doint the upgrade?
Hi BennyBoy, Do you mean the commands at https://wiki.hummy.tv/wiki/2TB_Disk_Installation_Blog ? Only I dont see any actual commands for creating sized and aligned partitions there.
BennyBoy
Member
Yes that's the correct Wiki. You have to calculate the sectors and ensure there are 3 partitions. But if you check the partition table, and are also using a 2TB drive, I'd imagine you could get away with using the same figures as in the Wiki using gfdisk.
Once done, then in Webif you can go to Diagnostics and run "4kalign" to check if it's all aligned.
Once done, then in Webif you can go to Diagnostics and run "4kalign" to check if it's all aligned.
Trev
The Dumb One
As we are delving into the innermost mysteries of formatting a HDD, is there any credence in BB's supposition about inodes as mentioned in his post #50?
And if there is, does it really matter in practice, and if so, what are the problems that might be encountered? i.e. Does it really matter a toss?
(You should be able to tell that I don't know what the heck you are talking about
)
And if there is, does it really matter in practice, and if so, what are the problems that might be encountered? i.e. Does it really matter a toss?
(You should be able to tell that I don't know what the heck you are talking about
)All questions I would like answered if at all possible?
I have the HDD physically installed and was very relieved to find the recording schedule still in place (thought I might have lost it). Now for the partitioning and formatting. I understand the argument for aligning partitions as it was something we used to have to think about when installing drives in PCs.
I'm going to try the Humax format method first as prpr suggests just to see if it works. I'll then use the 4kalign check as BennyBoy suggests to see if it has worked. I figure if it hasnt worked there is no harm in wiping the partitions and doing it again using gfdisk as BennyBoy suggests.
Once the drive is partitioned and formatted is there any way of checking the number of inodes to see what the Humax box created?
BennyBoy, sorry but I havent used gfdisk before. Last time I created partitions and formatted a drive I used the GUI for GParted. Is there any chance of an example of the command I would need in order to use the same settings as the wiki page specifying the 4k alignment and inode count?
.....
Right drive partitioned and formatted. Humax reports about 1.8TB available for recording.
I have the HDD physically installed and was very relieved to find the recording schedule still in place (thought I might have lost it). Now for the partitioning and formatting. I understand the argument for aligning partitions as it was something we used to have to think about when installing drives in PCs.
I'm going to try the Humax format method first as prpr suggests just to see if it works. I'll then use the 4kalign check as BennyBoy suggests to see if it has worked. I figure if it hasnt worked there is no harm in wiping the partitions and doing it again using gfdisk as BennyBoy suggests.
Once the drive is partitioned and formatted is there any way of checking the number of inodes to see what the Humax box created?
BennyBoy, sorry but I havent used gfdisk before. Last time I created partitions and formatted a drive I used the GUI for GParted. Is there any chance of an example of the command I would need in order to use the same settings as the wiki page specifying the 4k alignment and inode count?
.....
Right drive partitioned and formatted. Humax reports about 1.8TB available for recording.
Well it looks like the 4k alignment is good. Now I just need to read up on inodes and see if there is a way to tell what has happened on the humax box.
Code:
>>> Beginning diagnostic 4kalign
Running: 4kalign
--> This is an Advanced Format (AF) drive.
Model Number: ST2000VM003-1ET164
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
Nominal Media Rotation Rate: 5900
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 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
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sda1 8 2104510 2104503 1G 83 Linux
/dev/sda2 2104512 3886043166 3883938655 1.8T 83 Linux
/dev/sda3 3886043168 3907024062 20980895 10G 83 Linux
* OK * - partiton /dev/sda1 is properly aligned.
* OK * - partiton /dev/sda2 is properly aligned.
* OK * - partiton /dev/sda3 is properly aligned.
>>> Ending diagnostic 4kaligni would have thought you could use the same figures for the start of the first two partitions but will need to recalculate for the end of the second partition and for the third partition (because the second partition is the one that changes size depending on the capacity of the hard drive).
Last edited:
At the command line
tune2fs -l /dev/sda2
and look for "inode count". For reference on my 2TB drive the number is 1896576
"Inode count: 121380864"
Given the increase from 1TB to 2TB I'm not too worried about the amount of space taken up by the inodes. However I do want to make sure that an increased number of inodes wont impact performance or HDD lifespan.
and for reference, here is what you get with a 2TB drive using the Humax's own formatting :
Given the increase from 1TB to 2TB I'm not too worried about the amount of space taken up by the inodes. However I do want to make sure that an increased number of inodes wont impact performance or HDD lifespan.
and for reference, here is what you get with a 2TB drive using the Humax's own formatting :
Code:
humax# tune2fs -l /dev/sda2
tune2fs 1.42.13 (17-May-2015)
Filesystem volume name: hmx_int_stor
Last mounted on: <not available>
Filesystem UUID: 1287876e-a0fb-4c16-983e-0430ebeb37f8
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 121380864
Block count: 485492331
Reserved block count: 24274616
Free blocks: 477704559
Free inodes: 121373927
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 908
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Sat Oct 28 10:55:14 2017
Last mount time: Sat Oct 28 11:32:57 2017
Last write time: Sat Oct 28 11:32:57 2017
Mount count: 4
Maximum mount count: 32
Last checked: Sat Oct 28 10:55:14 2017
Check interval: 15552000 (6 months)
Next check after: Thu Apr 26 10:55:14 2018
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: af694c69-6b3a-4b46-ba61-42277964efe9
Journal backup: inode blocksprpr
Well-Known Member
The details are all in the blog - quicker format and check time, and a better hashing algorithm using half_md4 compared to tea. And you've still got plenty of inodes - you aren't going to be creating millions of files, no matter how many recordings you have.
So it probably is worth doing, if only for the quicker check time.