1 |
ata5.04: SATA link down (SStatus 0 SControl 0) |
2 |
ata5.04: hard resetting link |
3 |
ata5.04: failed to resume link (SStatus 0 Scontrol 0) |
4 |
|
5 |
and |
6 |
|
7 |
ata5.04: SATA link down (SStatus 0 SControl 0) |
8 |
ata5.04: hard resetting link |
9 |
ata5.04: failed to resume link (SStatus 0 Scontrol 0) |
10 |
|
11 |
|
12 |
beside all the install/reinstalls - both errors indicate the drive is |
13 |
failing OR (my best guess) the cable is bad. Replace the cable with a |
14 |
new one and try again. |
15 |
|
16 |
Oli |
17 |
|
18 |
On 2021-02-15 21:13, gevisz wrote: |
19 |
> пн, 15 февр. 2021 г. в 20:59, Jude DaShiell <jdashiel@×××××.com>: |
20 |
>> |
21 |
>> Check the date and time when you boot and if it isn't correct, you |
22 |
>> probably have a dead battery on your motherboard. I had to replace |
23 |
>> one a |
24 |
>> couple days ago. Fortunately the kind of battery my computer uses is |
25 |
>> sold |
26 |
>> in pharmacies since blood sugar meters also use them. |
27 |
> |
28 |
> Legacy system shows incorrect time but I think that it is because of |
29 |
> the dual-boot with Linux and not because of the battery issue. |
30 |
> The date is still correct: Monday, February 15, 2021. |
31 |
> |
32 |
> Well, probably my best option to reinstall the system from scratch. :( |
33 |
> |
34 |
>> On Mon, 15 Feb 2021, gevisz wrote: |
35 |
>> |
36 |
>> > Yesterday, my relatively new install of Gentoo failed to boot with the |
37 |
>> > following repeated messages: |
38 |
>> > |
39 |
>> > ata5.04: SATA link down (SStatus 0 SControl 0) |
40 |
>> > ata5.04: hard resetting link |
41 |
>> > ata5.04: failed to resume link (SStatus 0 Scontrol 0) |
42 |
>> > |
43 |
>> > My first thought was that something is wrong with my old IDE (ATA) |
44 |
>> > drive. (The Gentoo system partition was on /dev/sda5.) |
45 |
>> > |
46 |
>> > Nevertheless, I was able to boot from a flash drive with a live Gentoo |
47 |
>> > CD and chroot into the Gentoo system partition of my IDE drive. |
48 |
>> > |
49 |
>> > So, I formatted a new SATA drive according to instructions given in |
50 |
>> > Gentoo AMD64 Handbook, rsynced the corresponding IDE system partition |
51 |
>> > into it by the following command: |
52 |
>> > |
53 |
>> > rsync -qaHAXS source_dir target_dir |
54 |
>> > |
55 |
>> > made the necessary changes to the corresponding fstab file, chrooted |
56 |
>> > into the new system SATA partition, recompiled grub and installed it |
57 |
>> > on the new disk. |
58 |
>> > |
59 |
>> > After all that I was able to boot the Gentoo system from the new |
60 |
>> > partition. However, the booting process went as slow as hell, and at |
61 |
>> > the end Xorg server failed to start. |
62 |
>> > |
63 |
>> > My next guess was that something went wrong with the last kernel I |
64 |
>> > used to boot. So, I tried to boot using the previous kernel. |
65 |
>> > |
66 |
>> > However, this time the booting failed with almost the same messages as above: |
67 |
>> > |
68 |
>> > ata5.03: failed to resume link (SStatus 0 SControl 0) |
69 |
>> > ata5.03: SATA link down (SStatus 0 SControl 0) |
70 |
>> > ata5.03: hard resetting link |
71 |
>> > ata6.04: failed to resume link (SStatus 0 SControl 0) |
72 |
>> > |
73 |
>> > (Now, my new Gentoo system partition is on /dev/sdb2.) |
74 |
>> > |
75 |
>> > Shall I try to do something to fix it before reinstalling Gentoo anew? |
76 |
>> > |
77 |
>> > For example, I thought of booting with a live Gentoo flash drive, |
78 |
>> > chrooting into the new system partition and recompiling @system. |
79 |
>> > However, if it is not some package that is corrupted, it may be a waste of time. |
80 |
>> > Or, maybe, @system may be narrowed to just a few packages needed at boot time? |
81 |
>> > Shall I try to recreate initramfs, what in my case means re-emerging |
82 |
>> > gentoo-kernel package? |
83 |
>> > What do you think? |
84 |
>> > |
85 |
>> > P.S. Nevertheless, I still can successfully boot my very old legacy |
86 |
>> > system from another partition of my IDE drive. |
87 |
>> > |
88 |
>> > |
89 |
>> |