From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux-firmware-network-20230804_1: [unpack] failed to unpack files from archive
Date: Thu, 14 Sep 2023 15:47:25 +0200 [thread overview]
Message-ID: <20230914134725.9SbekjDhnZYGOly6hUgUHiNsA2Lmom8_8gJdVA8F1EM@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: 745 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/46054#issuecomment-1719488618
Comment:
> > smart-tools
>
> Do you mean the `smartmontools` package? A quick scan did not find any issues. I have yet to try the extended scan.
Yes, it should be able to show the drive state and possibly number of recorded read errors etc. From the dmesg it does look like more of an issue with the drive and not the filesystem.
> > fsck
>
> How do I check the file system that hold my OS? Do I need to create a bootable USB drive, boot from USB and then run fsck on my SSD?
Should happen automatically on boot, but you can also `touch /forcefsck` or add `forcefsck` to the kernel command line.
next prev parent reply other threads:[~2023-09-14 13:47 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 [this message]
2023-09-15 11:51 ` HiPhish
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 ` HiPhish
2023-09-20 17:05 ` [ISSUE] [CLOSED] " 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=20230914134725.9SbekjDhnZYGOly6hUgUHiNsA2Lmom8_8gJdVA8F1EM@z \
--to=duncaen@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).