Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
04-04-2020, 11:09 AM
|
#1
|
Senior Member
Registered: Mar 2010
Distribution: Slackware
Posts: 2,240
|
e2fsck stalls at 1.73%
Code:
e2fsck -ccfy /dev/sdc1
returned:
Quote:
e2fsck 1.45.6 (20-Mar-2020)
Checking for bad blocks (non-destructive read-write test)
Testing with random pattern: 1.73% done, 5:17 elapsed. (0/0/0 errors)
|
where it stuck for an hour.
Code:
e2fsck -cfy /dev/sdc1
doesn't stick there, finishes in 20 minutes.
That the time stalls, not just the progress, indicate that e2fsck has stalled, not just found a sector that puzzles it so that it can't proceed? Or is the updating of time dependent on the progress of the program?
|
|
|
04-05-2020, 08:40 AM
|
#2
|
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 24,192
|
I can guess only: e2fsck examines the disk and you will see "nothing" when the disk itself works on the current I/O request. Probably some internal housekeeping...
Can you reproduce it?
|
|
|
04-05-2020, 11:53 PM
|
#3
|
Senior Member
Registered: Mar 2010
Distribution: Slackware
Posts: 2,240
Original Poster
|
Quote:
Originally Posted by pan64
I can guess only: e2fsck examines the disk and you will see "nothing" when the disk itself works on the current I/O request. Probably some internal housekeeping...
|
I don't think I understand this comment. I would hope the time-keeping works off the timer interrupt, independently of what the program reads from the disk.
Quote:
Originally Posted by pan64
Can you reproduce it?
|
It happens every time. I gave up. The disk has worked for 11 years.
|
|
|
04-06-2020, 01:47 AM
|
#4
|
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 24,192
|
the disk has its own OS. The system (any PC, linux, windows, whatever) can only ask that OS to do something (usually read or write). But in this case it is some kind of housekeeping (or similar?) and the kernel just waits for the response. Cannot do anything [else] as long as the process is running (=no response from the disk).
Probably the disk is over, probably the best you can do is to replace it.
(and probably smartctl can give you more info, but probably that is not relevant any more)
|
|
|
04-06-2020, 05:30 PM
|
#5
|
Senior Member
Registered: Mar 2010
Distribution: Slackware
Posts: 2,240
Original Poster
|
Quote:
Originally Posted by pan64
Probably the disk is over, probably the best you can do is to replace it.
|
Nah, just specifying the block size made it work.
|
|
|
All times are GMT -5. The time now is 09:43 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|