Maintenance Mode

[MontysEvilTwin]

Did the security erase run? In the second link in my first post it points out a mistake in the command in the original thread. If you copied the command from the first post it would not work. As you can run fix-disk, the disk is still accessible. I would try the security erase procedure again, but use the commands listed to see how long the procedure will take and allow extra time to make sure it completes before doing anything else. Did you install the 'hdparm' CFW package as this is required to run the security erase?

 

[hummybee]

Just noticed the WD purple HDD is recommended in the 'Disk failing' post.

I have a Seatgate 1TB but if I go for the 2TB WD can the Humax format this ok?

 

[hummybee]

Thanks MontysEvilTwin I'll have a look later.

 

[MartinLiddle]

I have a Seatgate 1TB but if I go for the 2TB WD can the Humax format this ok?

If the Humax is running 1.03.xx software then it can indeed format a 2TB drive.

 

[johnb]

Just noticed the WD purple HDD is recommended in the 'Disk failing' post.

I have a Seatgate 1TB but if I go for the 2TB WD can the Humax format this ok?

Any reason you are looking at a WD Purple (designed for surveillance storage) in preference to a WD AV HDD?

 

[af123]

Any reason you are looking at a WD Purple (designed for surveillance storage)

Specifically, designed for use in a RAID array for a motion-activated surveillance system. I would not recommend using a WD Purple for a PVR - more details and discussion at http://hummy.tv/forum/threads/disk-failing.6490/#post-85348

 

[hummybee]

Hi johnb and af123

See #22.

Maybe I misread the 'Disk failing' post.

Using my other Humax for recordings so not in a hurry to replace my Humax with the disk problems as all files have been backed up.

 

[hummybee]

Hi MartinLiddle.

Thanks for the info.

I'm on Web interface version: 1.2.4
Custom firmware version: 3.03 (build 2368)
Humax Version: 1.03.12 (kernel HDR_CFW_3.03

so should be ok.

 

[MontysEvilTwin]

hummybee - I have a unit with a 1TB (AF) disk, like yours, and I ran the 'hdparm -I' command to list drive parameters. Abbreviated output is posted below:

One# hdparm -I /dev/sdb                                                       
                                                                              
/dev/sdb:                                                                     
                                                                              
ATA device, with non-removable media                                          
        Model Number:       ST1000VM002-1CT162                                
                                
Security:                                                                     
        Master password revision code = 65534                                 
                supported                                                     
        not     enabled                                                       
        not     locked                                                        
        not     frozen                                                        
        not     expired: security count                                       
                supported: enhanced erase                                     
        124min for SECURITY ERASE UNIT. 124min for ENHANCED SECURITY ERASE UNIT.

The estimated time required for the security erase is two hours and four minutes. From the times of our respective posts yesterday, the procedure could not have had time to complete before you rebooted (unless you started running it before my first post in this thread, of course). Your disk may well be OK. I would try running the security erase again, but allow sufficient time before rebooting.

 

[hummybee]

Hi MontysEvilTwin.

Thanks for #21 and 29#.

I will install 'hdparm' and give security erase another go later and allow more time for it to complete.