I'm sure you're right. Mainly in the sense of "I should have got on with doing it ages ago" (story of my life...). However, the sneaky timing is at the limit of acceptable behaviour from an inanimate object - note how it didn't fail to record, play, and delete until yesterday, a day after the...
Oh, I was forgetting. Since yesterday morning it has been showing a message saying the HDD needs formatting to allow recording. But yesterday it was still recording and deleting, while today it was deleting but does not now appear to have recorded anything.
Well, after partly fixing the disk errors I was busy with other things, and have only spent a little time on this problem. I've checked the pending error count, which shot up from 24 to 271 after a couple of weeks. However, since then it has only gone up by four more - but obviously 275 is a...
Well, so far so ... I'm not sure.
fix-disk, run with the new options, was left running for ages; after which is has reduced the current_pending_sector count from 152 to 24. But in doing that it found (and says it successfully re-wrote) 9,411 bad sectors. Yup, that many. In the end I stopped it...
Running fix-disk -P has got rid of the "deleting...." problem. As you said, I still have the flagged bad sectors, and smartctl now reports a total of 960 errors (up from 914) and 152 pending (down from 156). I think I'd prefer to process (rewrite) those and then see how many come up in the...
Currently I've got another couple of hours of FTP transfer to do. At least FTPing has a lot less hassle than I was expecting, based on past experience, but at 100 Mb/s max it's not ideal. I was then going to do as you suggested, and use fix-disk -P to rewrite all the flagged sectors. So that...
Indeed - bought September 2012, so 41 months * 17 hours per day * 325 days per year hits that figure pretty exactly. I turn it off at night, but otherwise it runs all day if I'm not away (and I retired in 2012).
I didn't run smartctl before - but this is what it says:
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1...
I did stop it - again ctrl+] did nothing, but closing the telnet session and starting a new one worked. Of course the "deleting" was still there.
So I've been trying to copy my recordings off the HDR to my USB disk, as I can't see any way to avoid at least a reformat, and probably a new hard...
What does stop fix-disk during its usage scan?
The first time, it took several hours finding 180 bad sectors, waiting for my input each time. It then said "Skipped repair of LBA__" and found 62 unused bad sectors, then took no more tan five hours (probably much less) finding the file ID and...
What's tedious about the bad sector search is that it stops to ask permission to repair for each one, and it can take minutes to get from an error to one at the next LBA. And I don't see why, as Ican't really imagine the answer is going to be different each time. Checking usage is just very...
Thanks for that - though I'm not sure what I then do with that information.
In fact, I started another run of fix-disk, thinking it would not re-find the "re-written" sectors. If it does, that'll be a pain - is there a way of stopping it?
This time, the short disk self test found and...
Unfair of me. I'd forgotten that the laptop I was using does, eventually, hibernate if left, and that stopped the logging. So I don't know how the fix-disk run ended.
The Telnet session was dead, but it was happy enough to accept a new one. On exiting, and following the restart, the box...
That's now looking optimistic. Having spent about two hours checking 53 sectors that were unused, it then spent nearly five hours over eight that were all in a single programme file, seven of them close (spanning ten sectors). It's now been (so it says) looking for the owner of the same sector...
Yes - that's what I did. Then went out, hoping it would run for the predicted 3:40. But it didn't get that far before finding bad sectors; and quite a lot of them. Note that it stopped and asked [y/n] before every repair, which I didn't expect as the Wiki just says "Once the disk check and...
I have a variant on the "Unable to find disk" issue - it only arose because I have the "permanent delete" problem, and was trying to use the custom firmware to get rid of that. I can't find quite this case on the forum - apologies if I have missed it.
Details:
HDR-FOX-T2 never modified (so...
I'm sure you're right. Mainly in the sense of "I should have got on with doing it ages ago" (story of my life...). However, the sneaky timing is at the limit of acceptable behaviour from an inanimate object - note how it didn't fail to record, play, and delete until yesterday, a day after the...
Oh, I was forgetting. Since yesterday morning it has been showing a message saying the HDD needs formatting to allow recording. But yesterday it was still recording and deleting, while today it was deleting but does not now appear to have recorded anything.
Well, after partly fixing the disk errors I was busy with other things, and have only spent a little time on this problem. I've checked the pending error count, which shot up from 24 to 271 after a couple of weeks. However, since then it has only gone up by four more - but obviously 275 is a...
Well, so far so ... I'm not sure.
fix-disk, run with the new options, was left running for ages; after which is has reduced the current_pending_sector count from 152 to 24. But in doing that it found (and says it successfully re-wrote) 9,411 bad sectors. Yup, that many. In the end I stopped it...
Running fix-disk -P has got rid of the "deleting...." problem. As you said, I still have the flagged bad sectors, and smartctl now reports a total of 960 errors (up from 914) and 152 pending (down from 156). I think I'd prefer to process (rewrite) those and then see how many come up in the...
Currently I've got another couple of hours of FTP transfer to do. At least FTPing has a lot less hassle than I was expecting, based on past experience, but at 100 Mb/s max it's not ideal. I was then going to do as you suggested, and use fix-disk -P to rewrite all the flagged sectors. So that...
Indeed - bought September 2012, so 41 months * 17 hours per day * 325 days per year hits that figure pretty exactly. I turn it off at night, but otherwise it runs all day if I'm not away (and I retired in 2012).
I didn't run smartctl before - but this is what it says:
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1...
I did stop it - again ctrl+] did nothing, but closing the telnet session and starting a new one worked. Of course the "deleting" was still there.
So I've been trying to copy my recordings off the HDR to my USB disk, as I can't see any way to avoid at least a reformat, and probably a new hard...
What does stop fix-disk during its usage scan?
The first time, it took several hours finding 180 bad sectors, waiting for my input each time. It then said "Skipped repair of LBA__" and found 62 unused bad sectors, then took no more tan five hours (probably much less) finding the file ID and...
What's tedious about the bad sector search is that it stops to ask permission to repair for each one, and it can take minutes to get from an error to one at the next LBA. And I don't see why, as Ican't really imagine the answer is going to be different each time. Checking usage is just very...
Thanks for that - though I'm not sure what I then do with that information.
In fact, I started another run of fix-disk, thinking it would not re-find the "re-written" sectors. If it does, that'll be a pain - is there a way of stopping it?
This time, the short disk self test found and...
Unfair of me. I'd forgotten that the laptop I was using does, eventually, hibernate if left, and that stopped the logging. So I don't know how the fix-disk run ended.
The Telnet session was dead, but it was happy enough to accept a new one. On exiting, and following the restart, the box...
That's now looking optimistic. Having spent about two hours checking 53 sectors that were unused, it then spent nearly five hours over eight that were all in a single programme file, seven of them close (spanning ten sectors). It's now been (so it says) looking for the owner of the same sector...
Yes - that's what I did. Then went out, hoping it would run for the predicted 3:40. But it didn't get that far before finding bad sectors; and quite a lot of them. Note that it stopped and asked [y/n] before every repair, which I didn't expect as the Wiki just says "Once the disk check and...
I have a variant on the "Unable to find disk" issue - it only arose because I have the "permanent delete" problem, and was trying to use the custom firmware to get rid of that. I can't find quite this case on the forum - apologies if I have missed it.
Details:
HDR-FOX-T2 never modified (so...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.