Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #233246
| From | "Alexander V. Makartsev" <avbetev@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary |
| Date | 2021-03-20 11:20 +0100 |
| Message-ID | <BUGS6-6Ty-5@gated-at.bofh.it> (permalink) |
| References | <BU5fP-8w-1@gated-at.bofh.it> <BUd3H-4Iv-1@gated-at.bofh.it> <BUj98-aB-9@gated-at.bofh.it> <BUFCF-5Xk-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On 20.03.2021 13:50, David wrote: > On Fri, 19 Mar 2021 at 19:53, Alexander V. Makartsev <avbetev@gmail.com> wrote: > >> To perform surface scans you can use SMART short and long scans, and also a program called "badblocks" from the package "e2fsprogs". >> Be sure to unmount "/dev/sda1" before performing the scans. > Hi, I wonder why you give this advice to unmount. > Are you aware of a smartmontools reference document > that gives this advice? > > If not using captive mode --captive option then > I feel it is unnecessary. > > If using captive mode then I would suggest to unmount > the entire drive, not just one partition. > > This is my casual understanding, corrections with > authoritative sources are welcome. > Normally, a SMART scans are non-destructive and would finish with an error as soon as first bad block is found. But if HDD would encounter a real bad block or a long sequence of them during test scans, there is always a chance that HDD won't recover right away and as a consequence, kernel will remount partitions as read-only making OS unresponsive, even if later HDD's controller will return to normal state after processing bad blocks. For me it is simply a proactive measure, to prevent tests from interrupting mid-scan and any external interference. This might prevent a huge time waste when you scan a multi-terrabyte drives. Additionally, a manpage for "badblocks" program strongly recommends to unmount partitions before performing non-destructive read-write or destructive write tests on the device. If you look through information OP gathered for us, you should notice "/dev/sda" has only one partition with NTFS filesystem. -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄⠀⠀⠀⠀
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Robbi Nespu <robbinespu@gmail.com> - 2021-03-18 14:40 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary IL Ka <kazakevichilya@gmail.com> - 2021-03-18 15:00 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary IL Ka <kazakevichilya@gmail.com> - 2021-03-18 15:50 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary David Wright <deblis@lionunicorn.co.uk> - 2021-03-18 16:30 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary IL Ka <kazakevichilya@gmail.com> - 2021-03-18 17:00 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary David Wright <deblis@lionunicorn.co.uk> - 2021-03-18 17:30 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Robbi Nespu <robbinespu@gmail.com> - 2021-03-19 03:00 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Felix Miata <mrmazda@earthlink.net> - 2021-03-18 16:40 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary IL Ka <kazakevichilya@gmail.com> - 2021-03-18 16:50 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Felix Miata <mrmazda@earthlink.net> - 2021-03-18 17:00 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Robbi Nespu <robbinespu@gmail.com> - 2021-03-19 02:50 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Robbi Nespu <robbinespu@gmail.com> - 2021-03-18 15:50 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-03-18 19:10 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Robbi Nespu <robbinespu@gmail.com> - 2021-03-19 03:30 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-03-19 10:00 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary David <bouncingcats@gmail.com> - 2021-03-20 10:00 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-03-20 11:20 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Robbi Nespu <robbinespu@gmail.com> - 2021-03-23 05:10 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Jochen Spieker <ml@well-adjusted.de> - 2021-03-19 17:30 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-03-19 18:40 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Jochen Spieker <ml@well-adjusted.de> - 2021-03-19 22:10 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary Andy Smith <andy@strugglers.net> - 2021-03-20 18:10 +0100
Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-03-20 20:30 +0100
csiph-web