Closed admirabilis closed 10 years ago
The disk is not in the best shape but it's not near death either. You can try to run it with --fix and diskscan will rewrite back sectors that took long to read. I've seen it help considerably on some older disks I had that showed some problems. It lets the disk either reallocate or just plain rewrite locations that are slightly off the mark.
Do run --fix only a disk you are not working with and not booted from at the time, that means using it from a live-cd image. Otherwise data corruption may occur. I have issue #20 to handle that automatically for the users.
Hello, Baruch! Thanks for your reply!
Before running it with the `--fix' option, I decided to run the read-only test again, just to see if it would show the same results, because yesterday I run it while working and playing music, which could be the reason for the slow reads.
But see what I got:
(teresaejunior)> sudo diskscan -s seq /dev/sda
diskscan version unknown-1104c45
I: Validating path /dev/sda
I: Opened disk /dev/sda sector size 512 num bytes 8124599280892641280
I: Scanning disk /dev/sda
I: Fixing region by rewriting, offset=-1774232576 size=83
E: Error while attempting to rewrite the data! errno=9: Bad file descriptor
I: Fixing region by rewriting, offset=-1774101504 size=83
E: Error while attempting to rewrite the data! errno=9: Bad file descriptor
^CI: Disk scan interrupted
And I'm sure I run it without `--fix', I just copied the text from the terminal and pasted here. The disk was mounted, now I'm worried!!! Maybe this should be updated on Debian if it was already fixed here!
Thanks for your attention again!
there was a but in that version of diskscan that tried to fix even without the fix flag but it couldn't because the disk was opened as read only. You shouldn't worry about that. On Dec 27, 2013 5:34 PM, "teresaejunior" notifications@github.com wrote:
Hello, Baruch! Thanks for your reply!
Before running it with the `--fix' option, I decided to run the read-only test again, just to see if it would show the same results, because yesterday I run it while working and playing music, which could be the reason for the slow reads.
But see what I got:
(teresaejunior)> sudo diskscan -s seq /dev/sda diskscan version unknown-1104c45
I: Validating path /dev/sda I: Opened disk /dev/sda sector size 512 num bytes 8124599280892641280 I: Scanning disk /dev/sda I: Fixing region by rewriting, offset=-1774232576 size=83 E: Error while attempting to rewrite the data! errno=9: Bad file descriptor I: Fixing region by rewriting, offset=-1774101504 size=83 E: Error while attempting to rewrite the data! errno=9: Bad file descriptor ^CI: Disk scan interrupted
And I'm sure I run it without `--fix', I just copied the text from the terminal and pasted here. The disk was mounted, now I'm worried!!! Maybe this should be updated on Debian if it was already fixed here!
Thanks for your attention again!
— Reply to this email directly or view it on GitHubhttps://github.com/baruch/diskscan/issues/30#issuecomment-31266788 .
But opened read-only by diskscan, you mean? Because the disk was mounted as read-write.
Yes. Diskscan openned the disk as read only. That's why you saw the errors when it tried to fix when it shouldn't have even tried. On Dec 27, 2013 6:39 PM, "teresaejunior" notifications@github.com wrote:
But opened read-only by diskscan, you mean? Because the disk was mounted as read-write.
— Reply to this email directly or view it on GitHubhttps://github.com/baruch/diskscan/issues/30#issuecomment-31269549 .
OK, awesome! Thanks!
The yet unreleased version tries to give an answer if the disk is ok or not. In the case shown above it would say the disk is ok. I hoped to release that version by now but it got delayed. Closing this ticket for now, if you find the next version unsatisfactory in that regard feel free to open another ticket on this.
Cheers!
OK, I'll certainly try it again when the new version comes! Thanks!
Hi,
Just thought to let you now that a new version was released. It should fix that issue you saw.
Let me know how it works for you.
Baruch
On Fri, Dec 27, 2013 at 11:55 PM, teresaejunior notifications@github.comwrote:
OK, I'll certainly try it again when the new version comes! Thanks!
— Reply to this email directly or view it on GitHubhttps://github.com/baruch/diskscan/issues/30#issuecomment-31281855 .
I have just tested the new version, and this problem was fixed, and it also displayed "passed" at the end, which helps the faint of heart!
Thanks, Baruch!
Yay! On Jun 5, 2014 2:32 PM, "teresaejunior" notifications@github.com wrote:
I have just tested the new version, and this problem was fixed, and it also displayed "passed" at the end, which helps the faint of heart!
Thanks, Baruch!
— Reply to this email directly or view it on GitHub https://github.com/baruch/diskscan/issues/30#issuecomment-45208391.
Hello, Baruch!
Last month I dropped my new laptop, and then I saw this nifty tool on Debian News. Thanks for writing and sharing it!
From what I figured out of the man page my disk is doomed? Can you please help me out with this?
What I have noticed from these results is that it starts slow where the disk is full and then gets gradually faster where it is mostly empty...
The results from smartctl don't seem to display anything wrong, though:
Thanks for you attention!