On Wednesday, 3 June 2020 18:28:33 BST Dale wrote:
> tedheadster wrote:
> > Yes, you do need to capture the kernel output.
> > 
> > The usual way is to hook up a serial cable to another computer and
> > pipe the output to it. You interrupt the boot (usually by hitting
> > <shift> or <tab> in GRUB), and then edit the kernel command line thus:
> > 
> > console=tty1 console=ttyS0,115200n8
> > 
> > If you can do that you can give us some debug output.
> > 
> > - Matthew
> 
> Could she boot from some other media, mount the partitions to get to
> dmesg and get it from that?  Or since it may not be mounting any
> partitons, would that lead down the wrong path if it is outdated? 
> 
> Dale
> 
> :-)  :-) 

If the /dev/sda3 partition is the correct swap partition as fdisk reports with 
a LiveCD, the OP can create a new swap on it and see if it can be activated:

mkswap -L SWAP /dev/sda3
swapon /dev/sda3

If there are still I/O errors try reseating the SATA cable, there may be 
corrosion on the contacts.  dmesg with the LiveCD will also reveal any other 
hardware issues.

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to