Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #275246
| From | Daniel Harris <mail.dharris@googlemail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: ext4 FS Crash |
| Date | 2024-12-04 18:20 +0100 |
| Message-ID | <JQ1cB-dJjO-9@gated-at.bofh.it> (permalink) |
| References | <JPWFX-dGq6-9@gated-at.bofh.it> <JQ0JA-dIUe-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Thanks for all your replies. As far as I can tell there are no errors reported using fsck or smartctl or nvme and the firmware is the correct and newest version so no problems there. The following are the messages that appear but only taken from my phone and copied from the photo (lots of scrolling errors repeating over). I thought these new drives were supposed to last longer than older moving HDD but obviously not I guess its time to buy a new drive : ( EXT4-fs (nvme0n1p2): Remounting filesystem read-onty EXT4-fs error (device nvme01p2): ext4_journal_check_start:83: comm systemd-journal: Detected aborted Jounal [633582.907324] EXT4-fs error (device nvme0n1p2): _ext4_find_entry:1683: inode #5898248: comm ntpd: reading directory iblock 0 [633582 908250] EXT4-fs (nvme0n1p2) : Remounting filesystem read-only EXT4-fs (nvme0n1p2): Remounting filesystem read-only EXT4-fs error (device nvme0n1p2) : ext4_journal.check_start:83: comm systemd-journal: Detected aborted journal [633582.912099] EXT4-fs (nvme0n1p2): Remounting filesystem read-only EXT4-fs error (device nvme0n1p2): ext4_journal-check_start:83: comm systemd-journal: Detected aborted journal [633582.916126] EXT4-fs (nvme0n1p2): Remounting filesystem read-only (633583.797550) EXT4-fs error (device nvme0n1p2) in ext4_setattr:5628: —— Journal has aborted (633583. 798466) EXT4-fs (nvme0n1p2): Remounting filesystem read-only EXT4-fs error (device nvme01p2): ext4_journal_check_start:83: comm systemd-journal: Detected aborted Jounal EXT4-fs (nvme@nip2): Remounting filesystem read-only EXT4-fs error (device nvme0n1p2): _ext4_find_entry:1683: inode #1966081: comm cron: reading directory Iblock 0 EXT4-fs (nvme@nip2): Remounting filesystem read-only EXT4-fs error (device nvme0n1p2) in ext4_setattr:5628: —— Journal has aborted EXT4-fs (nvme@nip2): Remounting filesystem read-only On Wed, Dec 4, 2024 at 4:39 PM Klaus Singvogel <deb-user-ml@singvogel.net> wrote: > Daniel Harris wrote: > > Seeing the similarity especially that we are both using similar drives > > (mine i( Samsung SSD 980 PRO 1TB) makes me think it might be a hardware > > instead of a software issue. > > The referenced Samsung SSD 980 PRO has a critical firmware bug. > > This bug hit me too. I had to replace my broken SSD by a new one, via the > Samsung support. > I use a full-disk encryption, and therefore had a data loss - up to my > last backup (5 days ago). > > Some more details here: > > https://www.pugetsystems.com/support/guides/critical-samsung-ssd-firmware-update/ > > > Best regards, > Klaus. > -- > Klaus Singvogel > GnuPG-Key-ID: 1024R/5068792D 1994-06-27 >
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