You are Here:
Linux Lite 6.6 FINAL Released - Support for 22 Languages Added - See Release Announcement Section



LL no longer booting on HP laptop PLS HELP

Author (Read 4460 times)

0 Members and 1 Guest are viewing this topic.

LL no longer booting on HP laptop PLS HELP
« Reply #1 on: March 03, 2018, 03:39:34 PM »
 

pingball57

  • Occasional Poster
  • **
  • 58
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile
Hi everyone. HELP - I'm in trouble again. About 6 months ago I installed LL 3.4 64bit onto a notebook from fleabay. The model was stated as HP 15-R125NA (intel N3540 quad) but the model No has been (deliberately?) scratched off the lable. So who knows what it is for sure. It's been fine until now. On pressing 'on' button i get CLI straight away with GNU GRUB & 4 options. if i try to load LL from there I get the usual Feather screen which stays for ages then another CLI - Busybox vi.22.1 ....... built-in shell (ash) - and - (initramfs) - with an invitation to type help for a list of commands - most of which i don't know. If i enter exit I get;
/dev/sda1 contains a file with errors

then a long list of stuff ending;
ERROR reading block 28311966 ( attempt to read block from filesystem resulted in short read) while getting next inode from scan
/dev/sda1 : UNEXPECTED INCONSISTENCY ; RUN fsck MANUALLY
fsck exited with status code 4
the root filesystem on /dev/sda1 requires manual fsck

- then the Busybox again

Can anyone tell me what the fsck is going on, how much trouble I'm in & how I get out of it. If some one can tell me how, I can put some pics of the screen if needed. I'm now using my (now back up) Toshy laptop to write this. (LL 3.4 32bit).
 Thanks in advance.

update.
After many hours trawling the web over the last few days I've learned very little but, one article states about initramfs & busybox that 'This can occur when you have installed Ubuntu on an NTFS Windows partition and Windows was incorrectly shutdown' . My laptop isn't dual boot. At least that's not what i thought i set it up as & I've never had an option to boot to windows. I've also learned that running fsck on a mounted partition will most likely screw things up.  I also have no idea what that means other than if i go poking about here without knowing what I'm doing will cause more problems. All the articles talk about how fsck can fix this stuff but don't tell me what to do with it. I don't know what to do here can i please have some help...

update;
this is for anyone else who has the same problem or has been following this. I tried booting to an earlier kernel at the grub 2 stage. (selecting advanced option & highlighting previous kernel - generic & hitting return). No boot & but got the busybox bit again. Having spent yet another evening trying to find a solution on other sites i came across this - https://askubuntu.com/questions/1002047/how-do-i-fix-my-computer-via-busybox
I took a deep breath and ran  - fsck /dev/mapper/ubuntu--vg-root
from the (initramfs) prompt not knowing what i was doing...
i got some sort of error return about file not found does not exist. i ran it again with various spacings on the -'s with the same result. i typed exit at the same prompt & nothing happened... at first. while i was trying to think if i should be using /dev/sda1 instead of the ubuntu bit i got the return 'fsck exited with code 1' (which I've checked means with errors fixed) then things started happening & it booted. I shut down & restarted & it booted again to the previous kernel I'd picked in grub. so it looks fixed. i have no idea how i got the problem or how i fixed it... & i'm disappointed with the lack of help from this support forum which has been so helpful previously. the only thing i can think of is that no one knew how to help.
« Last Edit: March 07, 2018, 05:31:55 PM by pingball57 »
 

 

-->
X Close Ad

Linux Lite 6.6 FINAL Released - Support for 22 Languages Added - See Release Announcement Section