It checked the disk with the first pattern in about 17hrs so it should complete 4TB in about 68hr. The drives are 4K "Advanced Format" drives, hence the 4K block size.
Nothing superior, nowadays, but nice for a pile of old Laptop drives. Hope this helps as much as this thread helped me to find a quick way to do a badblocks run on the disk. I know its use is dubious these days, but when a previous smartctl -t long failed due to read failures, I decided to have all sectors touched and rewritten a few times to see how the S.
Another smartctl Test is pending, if that again fails, I shall shop for a new drive. The current runtime for The rate of progress is 1. At this rate, it will take an additional 31 hours to complete, with an estimated total run time of 85 hours. This a USB 3. So far, zero bad blocks have been found. Should I do so, I don't see the downside of stopping this test, and resuming it in the future later, as this is a disk block-level operation. I must unmount this filesystem before resuming at the percent scan completed.
I know this is an ancient question but, to bring it up to date, I'm currently testing a 14TB drive using:. Driving machine is a rasperry pi 4 over usb3, so maybe there are some gains to be had using a SATA connection? Remember that badblocks writes the entire surface with a pattern, then goes back and reads it. In my case, I've asked it to do all that 4 times -p 4 , so I'm expecting this test to take about 33 days Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more.
How long does badblocks take on a 1TB drive? I will try that. I am afraid to turn off the power, but it may come to that. And if, for some reason, fsck hasn't completed, then the forcefsck file will still be present and it will start again. Nothing appeared on the monitor, but the system completed its boot!
I have lights on my pi to indicate network activity, which started to flash. I was then able to connect with ssh. So apparently it was waiting for some kind of response from me, which it couldn't get because the network wasn't initialized yet. All I can say now is "whew. Jump to. The ideal solution would be switching to solid-state storage since that does not have any of the physical limitations of spinning platters.
But that's probably cost-prohibitive. The next best would be to use a RAID optimized for parallel access. Keep in mind that RAIDs can be configured for many different performance profiles, so you will need to take some time to learn the settings of any given RAID hardware and drivers. You may be able to reduce the problem using aggressive filesystem caching. If your system has sufficient RAM, linux should be doing this fairly well already.
Run a program like top to see how much free RAM there is. A poor-man's work-around would be to split your files across several different physical hard-drives not just different partitions on the same drive.
That's not really a long-term scaleable solution and would end up costing you more than a decent RAID. But it might be a quick fix if you have drives lying around. For any solution involving hard disk drives, make sure they have a fast rotation speed and low seek latency. Your File Server disk should be doing a lot of seek as the other guys said.
Smart will give you some results. If you're sending a hdparm to HDD that is mounted with concurrent access, that could be the answer why your results are a lot less than before. Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Any advice? SMART doesn't remap sectors, it just detects and logs errors. Bad sectors are remapped automatically when written to. You can do this with dd or hdparm --write-sector. If your drive cannot remap the sector because it has run out of reserve sectors then you should be one step before panic. Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Learn more. Extremely long time for an ext4 fsck Ask Question. Asked 8 years, 5 months ago. Active 8 years, 5 months ago. Viewed 11k times. The command that I am running is sudo fsck. However, here is the output so far: e2fsck 1. The disk which I am checking has a newly created ext4 filesystem with nothing on it.
0コメント