| 1 |
On Wednesday, 3 June 2020 18:28:33 BST Dale wrote: |
| 2 |
> tedheadster wrote: |
| 3 |
> > Yes, you do need to capture the kernel output. |
| 4 |
> > |
| 5 |
> > The usual way is to hook up a serial cable to another computer and |
| 6 |
> > pipe the output to it. You interrupt the boot (usually by hitting |
| 7 |
> > <shift> or <tab> in GRUB), and then edit the kernel command line thus: |
| 8 |
> > |
| 9 |
> > console=tty1 console=ttyS0,115200n8 |
| 10 |
> > |
| 11 |
> > If you can do that you can give us some debug output. |
| 12 |
> > |
| 13 |
> > - Matthew |
| 14 |
> |
| 15 |
> Could she boot from some other media, mount the partitions to get to |
| 16 |
> dmesg and get it from that? Or since it may not be mounting any |
| 17 |
> partitons, would that lead down the wrong path if it is outdated? |
| 18 |
> |
| 19 |
> Dale |
| 20 |
> |
| 21 |
> :-) :-) |
| 22 |
|
| 23 |
If the /dev/sda3 partition is the correct swap partition as fdisk reports with |
| 24 |
a LiveCD, the OP can create a new swap on it and see if it can be activated: |
| 25 |
|
| 26 |
mkswap -L SWAP /dev/sda3 |
| 27 |
swapon /dev/sda3 |
| 28 |
|
| 29 |
If there are still I/O errors try reseating the SATA cable, there may be |
| 30 |
corrosion on the contacts. dmesg with the LiveCD will also reveal any other |
| 31 |
hardware issues. |
Archives