On 31.05.21 22:10, Morten Bo Johansen via arch-general wrote:
> OK, I will heed your advice. Too bad, I just installed Arch a
> couple of months ago and I have set up a really nice system. Now,
> I have to go through it all again ;(
For a quick and dirty disaster-recovery backup you could try dump
On 2021-05-31 Thore Bödecker via arch-general wrote:
>> 187 Reported_Uncorrect -O--CK 099 099 000-1
>> 188 Command_Timeout -O--CK 100 099 000-12
>> 189 High_Fly_Writes -O-RCK 067 067 000-33
>> 190 Airflow_Temperature_Cel -O---K 051
On 31.05.21 20:27, Morten Bo Johansen via arch-general wrote:
> I include it below. It says "Device Error Count: 12".
> Oddly enough, the command
>sudo smartctl -t long /dev/sda
> completes without any errors at all. The problem is also
> intermittent. It is rather odd.
This seems odd indeed,
On 2021-05-31 Thore Bödecker via arch-general wrote:
> Uncorrectable Errors with specific LBAs are usually a very solid
> indicator for a defective drive.
>
> If you could share the full `smartctl -x /dev/sda` output, we might be
> able to establish/identify some further hints on a failing drive
>
On 31.05.21 13:37, Morten Bo Johansen via arch-general wrote:
> On 2021-05-31 Thore Bödecker via arch-general wrote:
>
> > The output of `smartctl -x /dev/sda` could provide some further
> > insights into the health state of that drive.
>
> Good call. It reports that there are 12 errors on the dr
On Mon, 31 May 2021 at 21:12, Morten Bo Johansen via arch-general
wrote:
> badblocks reports that there are absolutely zero bad sectors or
> other errors on the hard drive.
https://serverfault.com/questions/506281/how-are-smart-selftests-related-to-badblocks
On 2021-05-31 Thore Bödecker via arch-general wrote:
> The output of `smartctl -x /dev/sda` could provide some further
> insights into the health state of that drive.
Good call. It reports that there are 12 errors on the drive.
They all look more or less the same:
Error 9 [8] occurred at disk
On 2021-05-31 Morten Linderud via arch-general wrote:
> Check if it's a bad sata cable. These errors usually indicates a broken cable,
> connector or a bad disk. But if there are no bad sectors I wouldn't bet on the
> disk being broken.
I will check the cable.
> Clearly we can only resolve this
On 31.05.21 13:11, Morten Bo Johansen via arch-general wrote:
> Do you have some suggestions as to how I should go about dealing
> with this? Other commands to test the hard drive? Kernel
> parameters? Anything?
The output of `smartctl -x /dev/sda` could provide some further
insights into the heal
On Mon, May 31, 2021 at 01:11:19PM +0200, Morten Bo Johansen via arch-general
wrote:
> Do you have some suggestions as to how I should go about dealing
> with this? Other commands to test the hard drive? Kernel
> parameters? Anything?
Check if it's a bad sata cable. These errors usually indicates
Hi
Arch is occasionally - only occasionally - very slow to start
up. After examining the dmesg log, I see errors like
100.740566] blk_update_request: I/O error, dev sda, sector 119400712 op
0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[ 100.740584] ata1: EH complete
[ 101.100769] a
11 matches
Mail list logo
