- This topic has 74 replies, 7 voices, and was last updated 9 years, 8 months ago by
.
-
Posts
-
bill3579 – 16 minutes ago »
I will try again in a few days with a wireless dongle.
OK. Installing should be a case of clicking on a button and waiting although there have been some recent cases of people needing to make several attempts before it successfully downloads all the files required.
I had considered doing a factory reset, but cannot find assurance that records on the HDD will be left undisturbed. It is said to be the case for Foxsat, but is it the same for Fox?
Yes it is the same with recordings left untouched but I don’t see the point. You have a possible problem with the hard drive and the starting point should be looking at the SMART data which will say whether it is worth attempting to fix the errors or better to replace drive.
Thanks, I’ll wait for the dongle. The reset query was only for future reference.
The HDR now has a wireless connection and the custom firmware has been downloaded and installed. Results of a disk diagnostic check are in a pdf file which I intended to attach to this post, but when I pressed Upload, I was ejected from the forum and my draft was wiped.
I want to copy some recordings to my laptop before doing anything else like logging in with Telnet to run Fixdisk, but I do not know what to do next.
Can you see the pdf file?
bill3579 – 34 minutes ago »
Can you see the pdf file?
No. The critical items from the diagnostics are the “Raw values” of the following attributes:
5 Reallocated_Sector_Ct
9 Power_On_Hours
187 Reported_Uncorrect
197 Current_Pending_Sector
198 Offline_Uncorrectable
I do not understand how I can send you the file. Extracts for the items you mention are:-
5 Reallocated_Sector_Ct, PO–CK, 8, 100, 100, 036, 100%
9 Power_On_Hours, -O–CK, 9545, 090, 090, 000, 90%
187 Reported_Uncorrect, -O–CK, 14, 086, 086, 000
197 Current_Pending_Sector, -O–C-, 7, 100, 100, 000
198 Offline_Uncorrectable, —-C-, 7, 100, 100, 000
bill3579 – 1 hour ago »
I do not understand how I can send you the file. Extracts for the items you mention are:-
5 Reallocated_Sector_Ct, PO–CK, 8, 100, 100, 036, 100%
9 Power_On_Hours, -O–CK, 9545, 090, 090, 000, 90%
187 Reported_Uncorrect, -O–CK, 14, 086, 086, 000
197 Current_Pending_Sector, -O–C-, 7, 100, 100, 000
198 Offline_Uncorrectable, —-C-, 7, 100, 100, 000
The reallocated sector count is low (up to say a thousand reallocated sectors would be OK). The Current_Pending_Sector and Offline_Uncorrectable are a concern. As I think you suspected, running fix-disk is the next thing to try.
I have tried Fix Disk. it gets into a loop repeatedly asking if I want to attempt repair of the same bad block. After choosing N, it checks to see if the block is in use
” Checking to see if this block is in use…
debugfs 1.42.10 (18-May-2014)
/dev/sda2: Can’t read an inode bitmap while reading inode bitmap
testb: Filesystem not open
Unknown error”
I suppose the last thing left is format. Can I recover some of my recordings first?
The raw values for the five items are different-
5 Reallocated_Sector_Ct 16 coloured buff
9 Power_On_Hours 9553
187 Reported_Uncorrect 27
197 Current_Pending_Sector 14 coloured orange
198 Offline_Uncorrectable 14 ditto
My efforts appear to have restored the ethernet connectiom
In the self test logs there are five instances of #1 and 16 of #6
# 1 Short offline Completed: read failure 90% 9553 1805655240
# 6 Short offline Completed: read failure 90% 9553 1805655232
bill3579 – 3 hours ago »
In the self test logs there are five instances of #1 and 16 of #6
# 1 Short offline Completed: read failure 90% 9553 1805655240
# 6 Short offline Completed: read failure 90% 9553 1805655232
These are linked to the problems reported by attributes 197 and 198. fix-disk will hopefully map out the sectors concerned; if not it should be possible to do it from the command line.
bill3579 – 5 hours ago »
I have tried Fix Disk. it gets into a loop repeatedly asking if I want to attempt repair of the same bad block. After choosing N, it checks to see if the block is in use
” Checking to see if this block is in use…
debugfs 1.42.10 (18-May-2014)
/dev/sda2: Can’t read an inode bitmap while reading inode bitmap
testb: Filesystem not open
Unknown error”
I suppose the last thing left is format. Can I recover some of my recordings first?
Why did you choose N? You should be choosing Y to reallocate the bad block, that’s the way to fix them.
I chose N because the program appeared to be repeating the same thing. I will try again. is that is what I should have done.
bill3579 – 1 hour ago »
is that is what I should have done.
Yes and worth trying. If you format without fixing the problems then they will remain in place; the filesystem will be fixed for the time being but the problems will come back in due course.
Fix Disk ran for about two hours, the first 20 min were taken up by what I thought was a loop, then the rest of the action followed. All seemed to go well and the HDR appears to work without any hitches.
However, the HDD test in Settings – Data Storage shows a disk failure, error 81, and a suggestion that format should be used to recover the data storage. The raw values in the drive diagnostics are 16 (buff), 9560, 27, 2 (orange) and 2 (orange).
I will run Fix Disk again
@bill3579 – take a look at this thread here. Is your disk advanced format (4k physical sectors)? I think it probably is. The current version of fix-disk does not reallocate 4k sectors correctly. One physical 4k sector corresponds to 8 logical sectors: fix disk reallocates the first logical sector only and gets stuck in a loop. To clear the problem, you will have to manually write to the next seven sectors using telnet. It is easier than it sounds. Note where the problem occurs (fix-disk should report the LBA of the bad sector/s) and start from there. What you need to do is described in the above link.
- You must be logged in to reply to this topic.