Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #275337
| From | Jörg-Volker Peetz <jvpeetz@web.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: ext4 FS Crash |
| Date | 2024-12-06 14:30 +0100 |
| Message-ID | <JQGz8-ebyf-15@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <JQ0JA-dIUe-21@gated-at.bofh.it> <JQ1cB-dJjO-9@gated-at.bofh.it> <JQglj-dT03-7@gated-at.bofh.it> <JQlXH-dWpk-1@gated-at.bofh.it> <JQo9b-dXPx-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi, Michael Stone wrote on 05/12/2024 18:41: > On Thu, Dec 05, 2024 at 10:26:18PM +0700, Max Nikulin wrote: >> On 05/12/2024 16:19, Jörg-Volker Peetz wrote: >>> 1. SSD's have some self healing capacities (discarding defect sectors) which >>> are performed when the drive is not mounted. Therefore, enter the BIOS of the >>> computer and let it running for ca. an hour. Then restart the computer. >> >> I am curious which way OS notifies a drive that it is mounted. I believed that >> drivers read and write blocks, maybe switch power save states, but mount is >> performed on a higher level. > > It doesn't: leaving the system unmounted ensures that the drive is idle, but in > general that's not necessary--just leaving the system alone will usually have > the same result unless you've got a runaway process chewing on the disk. The SSD > will do maintenance tasks when it's idle, or under pressure (has no other choice > because there are no writable blocks available). Should have been more clear. The drive should be idle for a longer time. This is assured by not mounting any partition of the SSD. I was able to "repair" unreadable sectors on a built-in SSD of an HP-Probook laptop. As far as I remember I also deleted files which could not be read any more because of defective sectors and restored the files from backup. Such unreadable files can be found by performing, e.g., a checksum calculation of all files on the SSD. Then, leaving the SSD alone, it was able to "replace" the defective sectors by spare sectors. Regards, Jörg.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2024-12-04 13:30 +0100
Re: ext4 FS Crash Jochen Spieker <ml@well-adjusted.de> - 2024-12-04 13:50 +0100
Re: ext4 FS Crash Eike Lantzsch ZP5CGE / KY4PZ <zp6cge@gmx.net> - 2024-12-04 15:40 +0100
Re: ext4 FS Crash "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-04 19:20 +0100
Re: ext4 FS Crash "Alexander V. Makartsev" <avbetev@gmail.com> - 2024-12-04 17:30 +0100
Re: ext4 FS Crash Klaus Singvogel <deb-user-ml@singvogel.net> - 2024-12-04 17:50 +0100
Re: ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2024-12-04 18:20 +0100
Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-05 00:50 +0100
Re: ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2024-12-05 12:00 +0100
Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-05 13:40 +0100
Re: ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2024-12-05 16:40 +0100
Re: ext4 FS Crash Jörg-Volker Peetz <jvpeetz@web.de> - 2024-12-05 10:30 +0100
Re: ext4 FS Crash Max Nikulin <manikulin@gmail.com> - 2024-12-05 16:30 +0100
Re: ext4 FS Crash Erwan David <erwan@rail.eu.org> - 2024-12-05 16:40 +0100
Re: ext4 FS Crash Andy Smith <andy@strugglers.net> - 2024-12-05 17:10 +0100
Re: ext4 FS Crash gene heskett <gheskett@shentel.net> - 2024-12-06 02:00 +0100
Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-05 18:50 +0100
Re: ext4 FS Crash Jörg-Volker Peetz <jvpeetz@web.de> - 2024-12-06 14:30 +0100
Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-06 15:00 +0100
Re: ext4 FS Crash Jörg-Volker Peetz <jvpeetz@web.de> - 2024-12-06 15:10 +0100
Re: ext4 FS Crash Max Nikulin <manikulin@gmail.com> - 2024-12-06 17:00 +0100
Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-06 17:40 +0100
Re: ext4 FS Crash Max Nikulin <manikulin@gmail.com> - 2024-12-08 17:30 +0100
Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-08 18:20 +0100
Re: ext4 FS Crash Max Nikulin <manikulin@gmail.com> - 2024-12-10 04:50 +0100
Re: ext4 FS Crash Daniel Harris <mail.dharris@googlemail.com> - 2025-01-13 16:30 +0100
Re: ext4 FS Crash Jeffrey Walton <noloader@gmail.com> - 2024-12-04 22:00 +0100
Re: ext4 FS Crash Klaus Singvogel <deb-user-ml@singvogel.net> - 2024-12-05 08:30 +0100
Re: ext4 FS Crash gene heskett <gheskett@shentel.net> - 2024-12-05 11:10 +0100
Re: ext4 FS Crash Klaus Singvogel <deb-user-ml@singvogel.net> - 2024-12-05 13:10 +0100
Re: ext4 FS Crash gene heskett <gheskett@shentel.net> - 2024-12-05 13:40 +0100
Re: ext4 FS Crash Michael Stone <mstone@debian.org> - 2024-12-05 14:00 +0100
Re: ext4 FS Crash Klaus Singvogel <deb-user-ml@singvogel.net> - 2024-12-05 15:00 +0100
Re: ext4 FS Crash gene heskett <gheskett@shentel.net> - 2024-12-05 22:30 +0100
Re: ext4 FS Crash Jeffrey Walton <noloader@gmail.com> - 2024-12-04 18:20 +0100
csiph-web