Castle Robin
Member
In the process of preparing to install MX Linux 19.1 from Wizard From Oz's instructions in another topic, after my computer suddenly restarted yet again, this time I have got more errors during Start Up than ever before, so I'm having to use my spare laptop computer in order to go online.
The following is a fraction but a fair amount of details that I saw on my main (Desktop) computer.
Last week, I had to reinstall MX 17 from my USB stick in order to reactivate access to MX Linux.
Today, not even the MX 17 USB stick is allowing me to regain access to MX Linux, so I can no longer use the Live USB Stick to then click on "Install" and reinstall MX 17 from scratch.
Due to the Corona Virus, no computer engineers are available to visit in person, hoping there is some way of overriding the faults on my desktop computer so I can reaccess MX Linux 17 (preferably the Hard Drive copy to save having to click on "Install" and reinstall from the USB stick) to avoid this computer remaining dormant for the foreseeable future, as the date of the Lockdown being lifted remains unknown.
The following is why I can't use MX Linux 17 (not even via the USB stick) due to computer hardware errors.
Indeed, if there is a way to fix the hardware errors, please advise me what to do:-
0.026569 mce Hardware Error TSC 0 MRC {0120001000000} - The "mce" errors have varied during previous start ups including a reference to "Processor 2"
0.026600 mce Hardware Error Processor 2
Hoards of rows of "Multiply-claimed block(s) in inode"
rootMX17: Multiply-claimed block(s) in inode
rootMX17: {There are 69 inodes containing multiply-claimed blocks}
rootMX17: UNEXPECTED INCONSISTENCY RUN fsck MANUALLY (i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda 1requires a manual fsck
BusyBox v1.22.1 (Debian 1:1 22.0-19+63) built-in shell (ash)
Enter 'help' for a list of built-in commands
{initramfs}
Besides the above being very technical to me, so I don't understand what the above codes are, upon seeing "{initramsfs}", I have no idea what to add to (if possible) regain access to the Hard Drive copy of MX Linux after the "initramsfs" line which waits for commands I don't know what to add.
I also can't even use at least the Live USB Stick copy as a substitute whereby I'd need to click on "Install" and follow the approx 5 minute instruction steps.
The "Memtest" options that would normally appear in the Start Up menu below "MX 17 Horizon" are also inaccessible.
Please advise if or preferably how I can regain access to my desktop computer, and if there is a way to stop further hardware errors, as if I can regain access to MX Linux 17 (preferably the Hard Drive install, as it has the MX 19.1 ISO image installed there, which I'd otherwise have to redownload from the MX "Mirrors" site), I can then follow Wizard's DD instructions and have MX Linux 19.1 added to my USB stick, which I was preparing to do today before the Latest technical faults have prohibited me from proceeding further.
The Hardware Errors may explain why, besides sudden automatic restarts, shut downs, the monitor screen switching off then on again (with web sites/programs intact upon switching back on), picture freezing, Youtube videos becoming mute then playing in slow motion, and error messages during Start Up (likened to the above, plus VGA monitor errors etc), unlike before today, even with the Live USB stick, I can't regain access to MX Linux 17.1.
The following is a fraction but a fair amount of details that I saw on my main (Desktop) computer.
Last week, I had to reinstall MX 17 from my USB stick in order to reactivate access to MX Linux.
Today, not even the MX 17 USB stick is allowing me to regain access to MX Linux, so I can no longer use the Live USB Stick to then click on "Install" and reinstall MX 17 from scratch.
Due to the Corona Virus, no computer engineers are available to visit in person, hoping there is some way of overriding the faults on my desktop computer so I can reaccess MX Linux 17 (preferably the Hard Drive copy to save having to click on "Install" and reinstall from the USB stick) to avoid this computer remaining dormant for the foreseeable future, as the date of the Lockdown being lifted remains unknown.
The following is why I can't use MX Linux 17 (not even via the USB stick) due to computer hardware errors.
Indeed, if there is a way to fix the hardware errors, please advise me what to do:-
0.026569 mce Hardware Error TSC 0 MRC {0120001000000} - The "mce" errors have varied during previous start ups including a reference to "Processor 2"
0.026600 mce Hardware Error Processor 2
Hoards of rows of "Multiply-claimed block(s) in inode"
rootMX17: Multiply-claimed block(s) in inode
rootMX17: {There are 69 inodes containing multiply-claimed blocks}
rootMX17: UNEXPECTED INCONSISTENCY RUN fsck MANUALLY (i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda 1requires a manual fsck
BusyBox v1.22.1 (Debian 1:1 22.0-19+63) built-in shell (ash)
Enter 'help' for a list of built-in commands
{initramfs}
Besides the above being very technical to me, so I don't understand what the above codes are, upon seeing "{initramsfs}", I have no idea what to add to (if possible) regain access to the Hard Drive copy of MX Linux after the "initramsfs" line which waits for commands I don't know what to add.
I also can't even use at least the Live USB Stick copy as a substitute whereby I'd need to click on "Install" and follow the approx 5 minute instruction steps.
The "Memtest" options that would normally appear in the Start Up menu below "MX 17 Horizon" are also inaccessible.
Please advise if or preferably how I can regain access to my desktop computer, and if there is a way to stop further hardware errors, as if I can regain access to MX Linux 17 (preferably the Hard Drive install, as it has the MX 19.1 ISO image installed there, which I'd otherwise have to redownload from the MX "Mirrors" site), I can then follow Wizard's DD instructions and have MX Linux 19.1 added to my USB stick, which I was preparing to do today before the Latest technical faults have prohibited me from proceeding further.
The Hardware Errors may explain why, besides sudden automatic restarts, shut downs, the monitor screen switching off then on again (with web sites/programs intact upon switching back on), picture freezing, Youtube videos becoming mute then playing in slow motion, and error messages during Start Up (likened to the above, plus VGA monitor errors etc), unlike before today, even with the Live USB stick, I can't regain access to MX Linux 17.1.
Last edited: