From: HiPhish <HiPhish@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux-firmware-network-20230804_1: [unpack] failed to unpack files from archive
Date: Fri, 15 Sep 2023 13:51:22 +0200 [thread overview]
Message-ID: <20230915115122.pMkvsIXEbR2BJrOBh0_5epxguiTOiFTVk7P9SXIn0lw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46054@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
New comment by HiPhish on void-packages repository
https://github.com/void-linux/void-packages/issues/46054#issuecomment-1721148412
Comment:
I ran `fsck` on boot and this is what I got:
```
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
/dev/sda3 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
[ 54.812468] ata2.00: exception Emask 0x0 SAct 0x400000 SErr 0xc0000 action 0x0
[ 54.812908] ata2.00: irq_stat 0x40000008
[ 54.813207] ata2: SError: { CommWake 10B8B }
[ 54.813490] ata2.00: failed command: READ FPDMA QUEUED
[ 54.813771] ata2.00: cmd 60/08:b0:c8:21:00/00:00:04:00:00/40 tag 22 ncq dma 4096 in
[ 54.813771] res 41/40:00:c8:21:00/00:00:04:00:00/00 Emask 0x409 (media error) <F>
[ 54.814346] ata2.00: status: { DRDY ERR }
[ 54.814627] ata2.00: error: { UNC }
[ 54.821978] I/O error, dev sda, sector 67117512 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[ 54.822427] Buffer I/O error on dev sda3, logical block 569, async page read
Inode 7647940 extent tree (at level 1) could be narrower. Optimize<y>? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: ***** REBOOT SYSTEM *****
/dev/sda3: 1606243/13107200 files (0.2% non-contiguous), 35435138/52428800 blocks
```
I cannot make sense of this. What does this error mean, do I need a new SSD?
next prev parent reply other threads:[~2023-09-15 11:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 7:41 [ISSUE] " HiPhish
2023-09-14 7:51 ` classabbyamp
2023-09-14 7:54 ` HiPhish
2023-09-14 7:56 ` classabbyamp
2023-09-14 7:56 ` classabbyamp
2023-09-14 12:47 ` HiPhish
2023-09-14 13:00 ` Duncaen
2023-09-14 13:03 ` HiPhish
2023-09-14 13:06 ` Duncaen
2023-09-14 13:07 ` Anachron
2023-09-14 13:14 ` HiPhish
2023-09-14 13:17 ` Duncaen
2023-09-14 13:19 ` Duncaen
2023-09-14 13:31 ` HiPhish
2023-09-14 13:33 ` HiPhish
2023-09-14 13:47 ` Duncaen
2023-09-15 11:51 ` HiPhish [this message]
2023-09-15 16:54 ` Anachron
2023-09-15 19:19 ` HiPhish
2023-09-16 15:44 ` Anachron
2023-09-16 15:45 ` Anachron
2023-09-16 15:46 ` Anachron
2023-09-20 17:05 ` [ISSUE] [CLOSED] " HiPhish
2023-09-20 17:05 ` HiPhish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230915115122.pMkvsIXEbR2BJrOBh0_5epxguiTOiFTVk7P9SXIn0lw@z \
--to=hiphish@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).