On Tue, 2024-01-02 at 17:47 -0500, Dan Ritter wrote:
> > root@tiassa:~# journalctl -u smartmontools.service | grep unreadable
> > Jan 02 13:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently
> > unreadable (pending) sectors
> > Jan 02 13:37:39 tiassa smartd[740]: Device: /dev/sda [SAT],
On Wed, 3 Jan 2024 00:29:42 +
Andy Smith wrote:
> Hello,
>
> On Tue, Jan 02, 2024 at 04:42:37PM -0700, Charles Curley wrote:
> [...]
>
> If a SMART long self-test came back clean then it already has been
> re-mapped as a long self-test reads every user-accessible sector.
I'm not so sure
Charles Curley wrote:
> On Tue, 2 Jan 2024 17:47:18 -0500
> Dan Ritter wrote:
>
> root@tiassa:~# smartctl -a /dev/sda
> smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-amd64] (local build)
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WOR
Hello,
On Tue, Jan 02, 2024 at 04:42:37PM -0700, Charles Curley wrote:
> If I understand that entry in the SMART report, the offending
> sector should eventually be re-mapped or else marked as
> unrecoverable. If the latter, I'll get really concerned.
If a SMART long self-test came back clean the
On Tue, 2 Jan 2024 18:01:32 -0500
Dan Purgert wrote:
> On Jan 02, 2024, Charles Curley wrote:
> > I have a brand new NVME device, details below, in a brand new
> > computer. smartd just started returning pending sector errors.
>
> Means you've got "N" bad sector(s) on the drive. It happens, e
On Tue, 2 Jan 2024 17:47:18 -0500
Dan Ritter wrote:
> Charles Curley wrote:
> > I have a brand new NVME device, details below, in a brand new
> > computer.
>
> You might, but that's not what the details you show us are
> saying.
>
> [...]
>
> That says this is a SATA device, not an NVMe
Charles Curley wrote:
> I have a brand new NVME device, details below, in a brand new computer.
You might, but that's not what the details you show us are
saying.
> smartd just started returning pending sector errors.
>
> A recent extended (long) test run since the first reported pending
> sect
On Jan 02, 2024, Charles Curley wrote:
> I have a brand new NVME device, details below, in a brand new computer.
> smartd just started returning pending sector errors.
Means you've got "N" bad sector(s) on the drive. It happens, even on
new drives.
>
> A recent extended (long) test run since th
I have a brand new NVME device, details below, in a brand new computer.
smartd just started returning pending sector errors.
A recent extended (long) test run since the first reported pending
sector returned no errors.
How worried should I be?
Device Model: NS256GSSD330
Serial Number:W3
Debian-user is a mailing list provided for support for Debian users,
and to facilitate discussion on relevant topics.
A Debian resource - Codes of Conduct
* The list is a Debian communication forum hosted on Debian resources.
As such, it is subject to both
Install urlview
Il 28/12/2023 23:17, Valerio Vanni ha scritto:
I found that pm-suspend works because it unloads and reloades that module
In "/etc/pm/config.d/modules" there is
---
SUSPEND_MODULES="cx23885"
---
Now I've replicated this on systemd side with this script similar to yours:
/usr/lib/systemd/syste
Hi,
I have had 2 freezes as my laptop wakes up from suspend mode.
I have the following message printed on the screen then the
computer freezes and I have to do a hard reboot:
x86/tme: configuration is inconsistent between CPUs
x86/tme: MKTME is not usable
I just upgraded my bookworm stable insta
Paul M Foster (12024-01-01):
> Of course, it doesn't fix the retarded way Mutt handles links.
To the better of my knowledge, Mutt does not handle links at all. Please
refrain from calling it retarded.
> For those
> familiar with Mutt,
Hi,
Debian 12, bookworm. I'm trying to get fluidsynth and pipewire
playing together.
TL;DR everything seems to be running as it should, but I seem
unable to get a beep from the MIDI keyboard.
I carried over the config from a working 11/Bullseye installation.
The aim is to get a USB MIDI keyboard
On Tue, Jan 02, 2024 at 03:26:03AM +, Andy Smith wrote:
> Hello,
>
> On Mon, Jan 01, 2024 at 07:32:18PM -0700, Charles Curley wrote:
> > If one changes subject, would it not be better to simply start a new
> > thread? With most mail readers threading using the In-Reply-To header,
> > the new s
16 matches
Mail list logo
