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