On 2023-02-23 08:27+0100, to...@tuxteam.de wrote:
On Thu, Feb 23, 2023 at 01:41:42PM +0800, Qiming Ye wrote:
We have found out it's problem of the current.
You mean electrical current?
Yes that's what I meant.
On Thu, Feb 23, 2023 at 01:41:42PM +0800, Qiming Ye wrote:
> We have found out it's problem of the current.
You mean electrical current?
Cheers
--
t
signature.asc
Description: PGP signature
We have found out it's problem of the current.
Thank you for the support.
- Tim
On 2023-02-22 22:38+0700, Max Nikulin wrote:
On 22/02/2023 11:34, Qiming Ye wrote:
I have a Debian box running for 280+ days without rebooting,
recently it crashes pretty much everyday. Where should I look for
On 22/02/2023 11:34, Qiming Ye wrote:
I have a Debian box running for 280+ days without rebooting, recently it
crashes pretty much everyday. Where should I look for the reason of
crashing?
sudo journalctl
You may limit logs to specific boot by adding option like "--boot=-1".
Scroll to
On 2023-02-22 03:21-0500, Felix Miata wrote:
Qiming Ye composed on 2023-02-22 15:30 (UTC+0800):
Actually /dev/sdb is an mSata drive. Here's output of smartctl:
...
9 Power_On_Hours -O--C- 100 100 000-15975
12 Power_Cycle_Count -O--C- 100 100 000-
Qiming Ye composed on 2023-02-22 15:30 (UTC+0800):
> Actually /dev/sdb is an mSata drive. Here's output of smartctl:
...
>9 Power_On_Hours -O--C- 100 100 000-15975
> 12 Power_Cycle_Count -O--C- 100 100 000-69
Reasonably low use. I don't see a
On 2023-02-22 02:05-0500, Felix Miata wrote:
Qiming Ye composed on 2023-02-22 12:34 (UTC+0800):
I have a Debian box running for 280+ days without rebooting, recently it crashes
pretty much everyday. Where should I look for the reason of crashing?
If you're running Bullseye from that
Qiming Ye composed on 2023-02-22 12:34 (UTC+0800):
> I have a Debian box running for 280+ days without rebooting, recently it
> crashes
> pretty much everyday. Where should I look for the reason of crashing?
If you're running Bullseye from that external HD, I'd suspect the external HD's
power
It's running Debian 11, the last updates were applied few weeks ago.
This is the output of inxi -Faz
% inxi -Faz
System:Kernel: 5.10.0-21-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-21-amd64
Qiming Ye composed on 2023-02-22 12:34 (UTC+0800):
> I have a Debian box running for 280+ days without rebooting, recently it
> crashes
> pretty much everyday. Where should I look for the reason of crashing?
Which Debian is installed? When were updates last applied?
When was its hardware
Hello,
I have a Debian box running for 280+ days without rebooting, recently it crashes
pretty much everyday. Where should I look for the reason of crashing?
Thank you,
- Tim
11 matches
Mail list logo
