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