Am 20.11.2023 um 21:56:02 Uhr schrieb fxkl4...@protonmail.com:
> export LOGWATCH_LOGFILE_LIST='/var/log/daemon.log '
>
> it seems my bookworm doesn't have a daemon log
Then tune syslog to create that file or let logwatch use another file
that contains the logs.
On 21/11/2023 04:56, fxkl4...@protonmail.com wrote:
it seems my bookworm doesn't have a daemon log
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#rsyslog-creates-fewer-logfiles
Chapter 5. Issues to be aware of for bookworm
5.1.9. rsyslog creates fewer log
On Mon, 20 Nov 2023, Marco Moock wrote:
> Am 20.11.2023 um 17:54:27 Uhr schrieb fxkl4...@protonmail.com:
>
>> 2023-11-19T07:24:45.772306-06:00 honey smartd[858]: Device: /dev/sdb
>> [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from
>> 111 to 112
>
Am 20.11.2023 um 17:54:27 Uhr schrieb fxkl4...@protonmail.com:
> 2023-11-19T07:24:45.772306-06:00 honey smartd[858]: Device: /dev/sdb
> [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from
> 111 to 112
Looks good. Can you check logwatch for any error messages?
On Mon, 20 Nov 2023, Marco Moock wrote:
> Am 20.11.2023 um 15:14:51 Uhr schrieb fxkl4...@protonmail.com:
>
>> if i look in /var/log/syslog i see many entries
>
> What is the name of the entries?
>
> For me it is smartd.
>
2023-11-19T07:24:45.772306-06:00 honey smartd[
Am 20.11.2023 um 15:14:51 Uhr schrieb fxkl4...@protonmail.com:
> if i look in /var/log/syslog i see many entries
What is the name of the entries?
For me it is smartd.
since i upgraded to bookworm there is no smartd section in logwatch
logwatch runs every night using default settings
if i run
logwatch --service smartd --range Yesterday --detail high
i get nothing
if i look in /var/log/syslog i see many entries
Hi folks,
just a question:
When I am running LXQT, it appears that a window pops up, telling it needs my
root password to allow to write new informations of the smartd into the
device.
This happens only in LXQT, so I believe, something is overwriting the settings
of the smart demon.
But I
From: Andy Smith
Date: Sat, 22 Jan 2022 19:07:23 +
> If the drive is currently not in use then it may be simpler to just
> write over the entire drive with a simple
> # dd if=/dev/zero of=/dev/sda
When convenient will get another drive and substitute in the machine.
Then the dodgy dri
unction described here.
https://lists.debian.org/debian-user/2022/01/msg00863.html
Thanks for the information about the smartd.
... P.
--
mobile: +1 778 951 5147
VoIP: +1 604 670 0140
48.7693 N 123.3053 W
On Du, 23 ian 22, 19:09:48, Linux-Fan wrote:
> pe...@easthope.ca writes:
> >
> > I knew nothing of RAID. Therefore read here.
> > https://en.wikipedia.org/wiki/RAID
> >
> > Reliability is more valuable to me than speed. RAID 0 won't help.
> > For reliability I need a mirrored 2nd drive in the h
On Sunday, January 23, 2022 10:57:53 AM to...@tuxteam.de wrote:
> On Sun, Jan 23, 2022 at 08:14:06AM -0700, Charles Curley wrote:
> > On Sun, 23 Jan 2022 11:09:47 +
> >
> > Andy Smith wrote:
> > > Yes. When a drive sector goes bad, the drive cannot read from it, so
> > > you get an error in L
On Sun, 23 Jan 2022 18:41:36 +
Andy Smith wrote:
> If wanting to play around with mdraid you can do it with loop
> devices created from image files on your regular filesystem.
Nice, thank you.
One would probably have to install mdadm:
# apt install mdadm
> for i in a b; do sudo losetup -
Hello,
On Sun, Jan 23, 2022 at 07:09:48PM +0100, Linux-Fan wrote:
> To really profit from the enhanced reliability, you need to play
> through the recovery scenario, too. I recommend doing this in a VM
> unless you have some dedicated machine with at least two HDDs to
> play with.
If wanting to p
pe...@easthope.ca writes:
From: Andy Smith
Date: Sat, 22 Jan 2022 19:07:23 +
> ... you use RAID.
I knew nothing of RAID. Therefore read here.
https://en.wikipedia.org/wiki/RAID
Reliability is more valuable to me than speed. RAID 0 won't help.
For reliability I need a mirrored 2n
From: Andy Smith
Date: Sat, 22 Jan 2022 19:07:23 +
> ... you use RAID.
I knew nothing of RAID. Therefore read here.
https://en.wikipedia.org/wiki/RAID
Reliability is more valuable to me than speed. RAID 0 won't help.
For reliability I need a mirrored 2nd drive in the host; RAID 1
On Sun, Jan 23, 2022 at 08:14:06AM -0700, Charles Curley wrote:
> On Sun, 23 Jan 2022 11:09:47 +
> Andy Smith wrote:
>
> > Yes. When a drive sector goes bad, the drive cannot read from it, so
> > you get an error in Linux when a read is attempted.
>
> As I understand things, that isn't entir
> You should do a backup ASAP.
Personal data is on a micro SD card. After doing something worth
saving it's backed to the host drive by me running this bash script .
Backup() { \
if [ "$#" -gt 1 ]; then
echo "Too many arguments.";
else
echo "0 or 1 arguments are OK.";
if [ "$#" -eq 0
On Sun, 23 Jan 2022 11:09:47 +
Andy Smith wrote:
> Yes. When a drive sector goes bad, the drive cannot read from it, so
> you get an error in Linux when a read is attempted.
As I understand things, that isn't entirely correct. From what I
understand:
If the drive can read a sector without e
Hello,
On Sat, Jan 22, 2022 at 09:16:53PM -0800, pe...@easthope.ca wrote:
> From: Andy Smith
> Date: Sat, 22 Jan 2022 19:07:23 +
> > You are better off finding the damaged sectors and causing the drive
> > to remap them by writing new content in there. Then you don't have
> > to keep
From: Andy Smith
Date: Sat, 22 Jan 2022 19:07:23 +
> > Two parts are available to mount /root; /root can be on /dev/sda1 or
> > /dev/sda2.
>
> I don't understand what you mean by this statement.
I should have referred to / rather than /root.
peter@joule:/home/peter$ lsblk --list |
On Sat, 22 Jan 2022 09:18:27 -0800
pe...@easthope.ca wrote:
>
> Jan 22 08:49:17 joule smartd[563]: Device: /dev/sda [SAT], 155 Currently
> unreadable (pending) sectors
> Jan 22 08:49:17 joule smartd[563]: Sending warning via
> /usr/share/smartmontools/smartd-runner to root ...
Hello,
On Sat, Jan 22, 2022 at 09:18:27AM -0800, pe...@easthope.ca wrote:
> smartd reports to syslog.
>
> Jan 22 08:49:17 joule smartd[563]: Device: /dev/sda [SAT], 155 Currently
> unreadable (pending) sectors
> Jan 22 08:49:17 joule smartd[563]: Sending warning via
> /usr/s
pe...@easthope.ca wrote:
> smartd reports to syslog.
>
> Jan 22 08:49:17 joule smartd[563]: Device: /dev/sda [SAT], 155 Currently
> unreadable (pending) sectors
> Jan 22 08:49:17 joule smartd[563]: Sending warning via
> /usr/share/smartmontools/smartd-runner to root ...
>
smartd reports to syslog.
Jan 22 08:49:17 joule smartd[563]: Device: /dev/sda [SAT], 155 Currently
unreadable (pending) sectors
Jan 22 08:49:17 joule smartd[563]: Sending warning via
/usr/share/smartmontools/smartd-runner to root ...
Jan 22 08:49:18 joule smartd[563]: Warning via
/usr/share
Now it working
On 5/31/21 1:26 PM, Reco wrote:
I.e you should probably specify DEVICESCAN and -d in other order, i.e
Thanks you
--
Email : Robbi Nespu
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc
Hi.
On Mon, May 31, 2021 at 12:04:20PM +0800, Robbi Nespu wrote:
> Could you spot what I missed and guide me? Thanks in advance
Your smartd.conf has this:
> DEVICESCAN -d removable -n standby -m root -M exec
> /usr/share/smartmontools/smartd-runner
...
> /dev/sdb -d ignore
-U, where ID = 0 turns them off.
# All but -d, -m and -M Directives are only implemented for ATA devices
#
# If the test string DEVICESCAN is the first uncommented text
# then smartd will scan for devices.
# DEVICESCAN may be followed by any desired Directives
#
/dev/sdb -d ignore
my full conf file
Hi everyone!
I have smartd running on my jessie server, to keep an eye on my raid
disks.
One of them has a few pending sectors, but nothing major and I don't
want to replace it yet. Problem is, every 30 min the following message
gets dumped all over my open terminals (ssh as well as
Deas anyone know what are all those Smartd messages in my Watchlog about?
- Smartd Begin
/dev/hda :
Usage: Temperature_Celsius (194) changed to 110, 111, 112, 113, 114, 115, 116
/dev/hdb :
Prefailure: Raw_Read_Error_Rate (1) changed to 100
Christian Christmann wrote:
Hi,
smartd generates permanently the following e-mail (sent to root) on my
Debian Etch system:
[snip]
The following warning/error was logged by the smartd daemon:
Device: /dev/hda, 1 Offline uncorrectable sectors
I'd get a new HD. In my experience
On Sat, 13 May 2006, Christian Christmann wrote:
> Device: /dev/hda, 1 Offline uncorrectable sectors
You need to write over that sector, so that the HD can remap it.
Look at the smart error log to know the sector number. Use the smartctl
program to do it (man smartctl will tell you how).
If you
Hi,
smartd generates permanently the following e-mail (sent to root) on my
Debian Etch system:
---
Subject: SMART error (OfflineUncorrectableSector) detected on host: server
Date: Sun, 7 May 2006 12:33:22 +0200 (CEST)
This email was
>Does anybody else experience similar log events and if so, is there
>anything you did to stop this from happening?
>Thanks,
>Andre
Replace the drive. The error means that the ECC (Error Correcting Code)
of the Barracuda is kicking in to correct corruption in the drives
on-board cache RAM.
--
Hi,
I am using the package smartsuite to monitor my server harddisks.
Unfortunately, a Seagate Barracuda on /dev/hda keeps filling up my
syslog with messages like the one attached below(1).
Attribute 1 and 195 keep changing by 1/-1 almost every time smartd runs
the check. When I run smartctl
35 matches
Mail list logo
