So /dev/sda5 may contain a damaged filesystem, and it might be an important
one. There are some posts on the Internet with problems kind of similar to
yours. Most of them recommend trying to fix the damaged partition, which
fixed the problem. Did you try running "fsck -y /dev/sda5"?
However, as far as I can see fsck may not be included in Trisquel's version
of BusyBox. Do you have some Trisquel Live medium like a CD or a USB drive?
If so, you could try using that to fix the damaged filesystem. Insert the
CD/USB, boot into the live environment ("try trisquel without installing")
and run "sudo fsck -y /dev/sda5" in a terminal.
- [Trisquel-users] Unable to boot Ray Brown
- Re: [Trisquel-users] Unable to boot liberpool
- Re: [Trisquel-users] Unable to boot Ray Brown
- Re: [Trisquel-users] Unable to boot liberpool
- Re: [Trisquel-users] Unable to boot Ray Brown
- Re: [Trisquel-users] Unable to boot Ray Brown
- Re: [Trisquel-users] Unable to boot strypey
