On Sun, 9 Mar 2025 15:36:42 -0700
David Christensen wrote:
> Do you know the URL of a "howto" document that describes how to set
> that up?
No, sorry. I put that together ad hoc over several years.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/b
On 3/9/25 14:50, Michael Stone wrote:
On Sun, Mar 09, 2025 at 12:04:10PM -0700, David Christensen wrote:
I have glanced at smartd(8), but have yet to try it because it seems
to prefer sending reports via e-mail (?).
It's highly configurable. It also logs to syslog, and mails can be
disabled e
On 3/9/25 14:28, Charles Curley wrote:
On Sun, 9 Mar 2025 12:04:10 -0700
David Christensen wrote:
I have glanced at smartd(8), but have yet to try it because it seems
to prefer sending reports via e-mail (?). I have yet to figure out
how fetch root mail messages from my daily driver mail clie
On Sun, Mar 09, 2025 at 12:04:10PM -0700, David Christensen wrote:
I have glanced at smartd(8), but have yet to try it because it seems
to prefer sending reports via e-mail (?).
It's highly configurable. It also logs to syslog, and mails can be
disabled entirely or replaced by some other scrip
On Sun, 9 Mar 2025 12:04:10 -0700
David Christensen wrote:
> I have glanced at smartd(8), but have yet to try it because it seems
> to prefer sending reports via e-mail (?). I have yet to figure out
> how fetch root mail messages from my daily driver mail client
> (Thunderbird). My WAG is that I
On 3/9/25 9:26 AM, Eben King wrote:
The "norecovery" option for mount(8) seems like a dangerous design
choice. "readonly" is supposed to mean "do not write to disk".
Yeah, that's what I thought too.
"readonly" means "don't allow the contents of the filesystem to be
changed," e.g. attempts t
On 3/9/25 06:48, Christopher David Howie wrote:
On 3/9/25 9:26 AM, Eben King wrote:
The "norecovery" option for mount(8) seems like a dangerous design
choice. "readonly" is supposed to mean "do not write to disk".
Yeah, that's what I thought too.
"readonly" means "don't allow the contents o
On 3/9/25 06:26, Eben King wrote:
On 3/2/25 14:35, David Christensen wrote:
AIUI SMR does not work well for OS (e.g. /tmp, swap) and general-purpose
(e.g. /home) disks that see frequent small random write workloads. I
prefer small high-quality 2.5" SSD's (Intel SSD 520 Series 60 GB) for my
OS a
On 3/8/25 21:40, Christopher David Howie wrote:
On 3/2/25 2:35 PM, David Christensen wrote:
The "norecovery" option for mount(8) seems like a dangerous design
choice. "readonly" is supposed to mean "do not write to disk". I
must remember that land mine if and when I want to do forensic work.
Eben King wrote:
>
>
> > > === START OF INFORMATION SECTION ===
> > > Model Family: Seagate BarraCuda 3.5 (SMR)
> > > Device Model: ST2000DM008-2UB102
> >
> >
> > AIUI SMR does not work well for OS (e.g. /tmp, swap) and general-purpose
> > (e.g. /home) disks that see frequent small
On Sun, Mar 09, 2025 at 09:26:07AM -0400, Eben King wrote:
>
>
> On 3/2/25 14:35, David Christensen wrote:
[...]
> > AIUI SMR does not work well for OS [...]
> ?MR=Shielded / Conventional Magnetic Recording? How do I tell a priori
> which drives are SMR and which are CMR?
Shingled magnetic r
On 3/2/25 14:35, David Christensen wrote:
At this point, I am uncertain if the /home ext4 file systems are correct
on either the OS disc or the copied image disc (?).
I did a "fsck -f" on each filesystem. Many had no errors, most of the
rest were just "this inode is too wide". So they're
On 3/2/25 2:23 PM, Anssi Saari wrote:
So you actually back up the hibernated / partition? Is that really a
sound backup strategy?
It is effectively like yanking the power cord and then taking a backup.
(Effects of the voltage dropping on the storage controller/disk are
another matter, but in
On 3/2/25 2:35 PM, David Christensen wrote:
The "norecovery" option for mount(8) seems like a dangerous design
choice. "readonly" is supposed to mean "do not write to disk". I must
remember that land mine if and when I want to do forensic work.
To be fair, the first step of forensic work is
On Mon, 3 Mar 2025 at 10:03, Dan Purgert wrote:
> On Mar 02, 2025, Eben King wrote:
> > [...]
> > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
> > WHEN_FAILED RAW_VALUE
> > 1 Raw_Read_Error_Rate 0x000f 082 064 006Pre-fail
> > Always - 146369262
On 06/03/2025 00:00, Eben King wrote:
On 3/4/25 21:59, Max Nikulin wrote:
In this particular case I do not think it is a drive failure. I suspect
mounting /home was a mistake.
Indeed. "-ro" is not read only when a journal is in play.
In some post on data recovery I have seen a mention that
On Fri, 7 Mar 2025 at 00:41, Dan Purgert wrote:
> On Mar 07, 2025, David wrote:
> > The wikipedia page [1] regarding "1 Raw_Read_Error_Rate" says:
> > The raw value has different structure for different vendors and is often
> > not meaningful as a decimal number. For some drives, this number
On Mar 07, 2025, David wrote:
> On Mon, 3 Mar 2025 at 10:03, Dan Purgert wrote:
> > On Mar 02, 2025, Eben King wrote:
>
> > > [...]
> > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
> > > WHEN_FAILED RAW_VALUE
> > > 1 Raw_Read_Error_Rate 0x000f 082 064 006
On 2025-03-06, Max Nikulin wrote:
>
> SMART long test (requested when system high load is not expected) is a
> tool that may help to reveal issues with a disk earlier and give you
> more time to find a replacement and to schedule down time. Certainly a
> disk may still fail unexpectedly despite
On Mon 03 Mar 2025 at 17:55:59 (-0800), David Christensen wrote:
> I have always wondered if the decimal numbers in the smartctl(8)
> "RAW_VALUE" column are actual event counts, or a decimal
> representation of some binary bit field whose correct interpretation
> only the manufacturer knows (?).
On 05/03/2025 23:33, Greg wrote:
Given the cryptic nature of its results and the fact that a positive
result implies that the test itself can be a factor in precipitating the
very failure it intends to preclude, I see no reason to run this
program, which seems to produce more confusion than anyth
On 3/4/25 21:59, Max Nikulin wrote:
In this particular case I do not think it is a drive failure. I suspect
mounting /home was a mistake.
Indeed. "-ro" is not read only when a journal is in play.
Booting a live image may destroy hibernation data since live system may
mount the same swap
On 2025-03-05, Stefan Monnier wrote:
>> I thought the whole point of running the SMART tests was to detect
>> a failing disk, so color me confused.
>
> If we knew how to detect a failing (as opposed to failed) disk, then
> things would be easy. SMART is an attempt to provide relevant
> informatio
> I thought the whole point of running the SMART tests was to detect
> a failing disk, so color me confused.
If we knew how to detect a failing (as opposed to failed) disk, then
things would be easy. SMART is an attempt to provide relevant
information, but that's all. AFAIK, it's still "the best
On 2025-03-05, Max Nikulin wrote:
>
> Running SMART tests (smartctl -t ...) on a failing disk may kill it. If
I thought the whole point of running the SMART tests was to detect a failing
disk, so color me confused.
Greg (HE12025-03-05):
> I thought the whole point of running the SMART tests was to detect a failing
> disk, so color me confused.
Maybe apply some common sense.
If you have a device that is on the verge of breaking down, using it
intensively is likely to push it over the edge, of course.
The po
On 03/03/2025 00:03, Charles Curley wrote:
On Sun, 2 Mar 2025 10:49:41 -0500
Eben King wrote:
So what can I do to fix this, while still
keeping my history, cookies, tabs, etc?
I smell a rat. I wonder if the corruption is because your hard drive is
failing. I would first boot to a live CD and r
On 03/03/2025 17:03, Dan Purgert wrote:
On Mar 02, 2025, Eben King wrote:
[...]
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 082 064 006 Pre-fail
Always - 146369262
146 million read-errors.
On 3/3/25 02:03, Dan Purgert wrote:
On Mar 02, 2025, Eben King wrote:
[...]
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 082 064 006 Pre-fail
Always - 146369262
146 million read-errors.
7
Eben King wrote:
>
>
> On 3/3/25 05:03, Dan Purgert wrote:
> > Well, at least those read errors were all corrected ;)
> >
> > None of the first three bits are absolute proof that the drive is going,
> > but they're certainly cause for suspicion.
>
> Is there a way of seeing how many spare bloc
On 3/3/25 05:03, Dan Purgert wrote:
Well, at least those read errors were all corrected ;)
None of the first three bits are absolute proof that the drive is going,
but they're certainly cause for suspicion.
Is there a way of seeing how many spare blocks are left?
The "space at the end of a
On Mar 02, 2025, Eben King wrote:
> [...]
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
> WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000f 082 064 006 Pre-fail
> Always - 146369262
146 million read-errors.
> 7 Seek_Error_Rate 0x000
Chris Green writes:
> With modern systems booting so fast I wonder why anyone bothers with
> hibernate or sleep.
I guess my modern systems are different from yours, boot times are long.
Also, in my life software has state and that is kept by sleep and
hibernate. So when the computer wakes up, a
On Monday, 03-03-2025 at 06:46 Chris Green wrote:
> Anssi Saari wrote:
> > Eben King writes:
> >
> > > Normally I hibernate, and while it's hibernated, boot off a thumb drive
> > > and back up (either by partition or the whole drive) to a dedicated
> > > drive. The idea is if my main drive t
On Sun, 2 Mar 2025 12:51:03 -0500
Eben King wrote:
> > I smell a rat. I wonder if the corruption is because your hard
> > drive is failing. I would first boot to a live CD and run smartctl
> > tests on it.
>
> At the end of this message.
Nothing there jumps out at me, but maybe someone else w
On 3/2/25 14:46, Chris Green wrote:
Anssi Saari wrote:
Eben King writes:
Normally I hibernate, and while it's hibernated, boot off a thumb drive
and back up (either by partition or the whole drive) to a dedicated
drive. The idea is if my main drive takes a dump, I could replace it
with t
On 3/2/25 14:23, Anssi Saari wrote:
Eben King writes:
Normally I hibernate, and while it's hibernated, boot off a thumb drive
and back up (either by partition or the whole drive) to a dedicated
drive. The idea is if my main drive takes a dump, I could replace it
with the backup drive, boot,
Anssi Saari wrote:
> Eben King writes:
>
> > Normally I hibernate, and while it's hibernated, boot off a thumb drive
> > and back up (either by partition or the whole drive) to a dedicated
> > drive. The idea is if my main drive takes a dump, I could replace it
> > with the backup drive, boot,
On 3/2/25 07:49, Eben King wrote:
I backed up my system on Saturday (yesterday), and pulled a stupid.
I'll explain.
Normally I hibernate, and while it's hibernated, boot off a thumb drive
and back up (either by partition or the whole drive) to a dedicated
drive. The idea is if my main drive ta
Eben King writes:
> Normally I hibernate, and while it's hibernated, boot off a thumb drive
> and back up (either by partition or the whole drive) to a dedicated
> drive. The idea is if my main drive takes a dump, I could replace it
> with the backup drive, boot, and be on my merry way. After t
On 3/2/25 12:03, Charles Curley wrote:
On Sun, 2 Mar 2025 10:49:41 -0500
Eben King wrote:
So what can I do to fix this, while still
keeping my history, cookies, tabs, etc?
I smell a rat. I wonder if the corruption is because your hard drive is
failing. I would first boot to a live CD and r
On Sun, Mar 02, 2025 at 10:49:41AM -0500, Eben King wrote:
So. This time, while the backup was in process, I mounted /home
read-only to check something out. Apparently that's not good enough to
keep the filesystem intact, because at the end when I resumed, several
things in $HOME didn't work ri
> So. This time, while the backup was in process, I mounted /home
> read-only to check something out. Apparently that's not good enough to
> keep the filesystem intact,
Indeed, with ext4 (and maybe other journaled filesystems as well), even
if you mount read-only the system starts by (re)playing
On Sun, 2 Mar 2025 10:49:41 -0500
Eben King wrote:
> So what can I do to fix this, while still
> keeping my history, cookies, tabs, etc?
I smell a rat. I wonder if the corruption is because your hard drive is
failing. I would first boot to a live CD and run smartctl tests on it.
How did you do
44 matches
Mail list logo
