I am new to Bodhi and I am having trouble installing it on my old acer travel mate 8371. I have a bootable usb but the installation just stops and starts again. At the beginning there seems to be errors ( I have attached a screen shot).
I'd suggest booting to the Bodhi LIVE (USB) and checking the disk for errors. When you boot the Live USB there's an option "Check disk for Errors", select that and see what the outcome is.
An alternative would be to fully boot Bodhi live and from terminology, mount the hard drive and scan the disk - but I'm not entirely sure what the commands are (although easily found with a bit of google foo).
from live usb, using terminology :
sudo fdisk -l this will list a lot of info, it will also identify your internal drive (most likely /dev/sda1) - this assumes your entire disk is dedicated to Bodhi Linux. If you're dual booting then replace /dev/sda1 with the partition relevant to Bodhi Linux (there's a type column in the output, look for Linux or similar and make note of device - an example being /dev/sda7 ).
Using details to match your hardware, then run the following replacing /dev/sda1 as appropriate. The output will be to a file named badsectors.txt. take a look through it (and/or post here if not too large, if large then just a subset of data - or upload to pastebin.com and link)
sudo badblocks -v /dev/sda1 > badsectors.txt
if you're having trouble running the last command, then post the output from the first command and we'll guide you further.
Ultimately, you can instruct the disk not to write to the bad sectors - however, bad sectors (read: Physical Damage), is often an indicator that your disk is starting to fail.
NOTE substitute /dev/sda1 as appropriate.
sudo e2fsck -l badsectors.txt /dev/sda1
Last Edit: Oct 29, 2020 14:30:55 GMT by fidoedidoe
Just had a go but it just hangs. txt file is produced but is empty. Does that mean I need a new disk?
Possibly. I'd first check whether you can see the disk using the PCManFM File Manager on the Live USB. If you can see the drive and can also drill into the disk to see files then perhaps the command is failing (maybe output the results of fdisk and the command you ran so it can be validated).
Also, from the Live USB (assuming you have internet connection), you could probably install an app to interrogate the disks SMART data. This shoudl give you a "health" status and possibly show you how many bad blocks there (amongst other things).
EDIT - FYI the commends in my earlier post may take a quiet while to run (depends on how defective disk is and how large). If you can see the disk light on - then I'd say walk away for 10-20 mins (may be longer) and see whether the command eventually completes. You can just run sudo badblocks -v /dev/sda1 to have the output sent to screen (rather than file) - but be mindful that the command e2fsck will need an the file badsectors.txt to mark blocks as bad.
Last Edit: Oct 29, 2020 15:59:31 GMT by fidoedidoe