You are not logged in.
Hello,
I am new on this and not very knowledgeable in computer science.
For a few years now I have been working very well with Q4OS (Scorpion LTS) on an old Acer Aspire 5715Z laptop (Intel dual core processor T2370, 2GB RAM, 120GB HDD).
A few days ago I suffered an unforeseen shutdown due to a power failure and since then I have not been able to get my equipment up and running again.
When trying to start it, it indicates to me the following:
"Loading Q4OS operating system ...
Loading initial ramdisk ...
/dev/sda1: Note: if several inodd or block bitmap blocks or part of the inode table require relocation, you may wish to try running
e2fsck with the '-b 32768' option first. the problem may lie only with the primary block group descriptors, and the backupblock group
descriptors may be OK.
/dev/sda1: Block bitmap for group 664 is not in group. (block 4050074143)
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e, without -a or -p options)
fsck exited with status code 4
the root filesystem on /dev/sda1 requires a manual fsck
BusyBox v1.22.1 (Debian 1:1.22.0-19+deb9u2) built-in shell (ash)
Enter 'help' for a list of built in commands."
I enter 'help' and the screnn shows the following:
"Built-in commands:
-----------------
. : [ [[ alias bg break cd chdir command continue echo eval exec
exit export false fg getopts hash help history jobs kill let
local printf pwd read readonlyreturn set shift source test times
trap true type ulimit unask unalias unset wait"
I can't figure out what to do ... What instructions should I write and how....
I appreciate in advance the help that anyone can give me to rescue the operation of my equipment.
Thank you very much.
Regards,
Martín
Offline
You need to boot from live media and scan and fix the drive /dev/sda1 . Boot a live media and run in terminal:
$ sudo fsck -f /dev/sda1
That should fix the disk, if possible. Reboot and check the system.
Offline
Thank you very much for your quick help.
I´ll do it as soon as possible and let you know.
Kind regards,
Martín
Offline
Hello friends,
SOLVED!
Initially I did it by booting it to live media, but it scared me to see that by any of the boot methods that were offered to me, I was told that I would lose the data from the hard disk (Perhaps due to my little knowledge I misinterpreted something ... I understood that using live media, this would not happen ....). Either way, this worried me and I preferred to back down to clarify and better inform myself before continuing.
However, in the middle of my "withdrawal", it suddenly occurred to me to try what you indicated, but doing it directly on the screen where my computer always crashed, that is, after:
"..... BusyBox v1.22.1 (Debian 1: 1.22.0-19 + deb9u2) built-in shell (ash)
Enter 'help' for a list of built in commands. "
and so I did: I typed fsck -f / dev / sda1,
and with this the repair / recovery process began and finally the successful boot of the system.
Thank you very much for your help.
I am very happy and very grateful!
I explained what I did in case it could be useful to others facing a similar case.
Kind regards,
Martín
Offline