MX Linux Now Inaccessible due to Hardware Errors

Castle Robin

Member
Credits
870
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.
 
Last edited:


arochester

Moderator
Staff member
Gold Supporter
Credits
317
fsck exited with status code 4
Try the -y option.

From fsck manual:

-y For some filesystem-specific checkers, the -y option will cause the fs-specific fsck to always attempt to fix any detected filesystem corruption automatically. Some- times an expert may be able to do better driving the fsck manually. Note that not all filesystem-specific checkers implement this option. In particular fsck.minix(8) and fsck.cramfs(8) does not support the -y option as of this writing.
Source - https://unix.stackexchange.com/questions/107876/fsck-died-with-status-code-4
 

Castle Robin

Member
Credits
870
Thanks for your information and link.

Another fault that occurs is whereby the Monitor text size occasionally changes from standard to quite small but legible upon starting up or restarting my computer (all prior to the above faults). Hopefully, this issue will also be fixed.

I had a brainwave within minutes of posting my new topic - After switching my Desktop computer back on, this time I had the original MX-17 created USB Stick inserted after which I quickly kept pressing "F12" which is the key for my particular computer to access the Boot menu. In my case "USB-HDD" is the setting required to run Linux.

The first time, errors (but less of them than on the physical hard drive) appeared preventing me from using the USB stick.

The second time, success!, as I am replying to you from the very computer that I couldn't use earlier.

However, I will follow the instructions you've given me which will hopefully enable me to reaccess my physical hard drive, as the MX 19.1 ISO image I re-downloaded on 1 May is there, and if all works as hoped, I will be able to have MX 19.1 installed onto my other USB stick then installed on the hard drive shortly.
 

sp331yi

Active Member
Credits
1,057
For starters, use 19.1.

Recommend starting over with live boot to something like System Rescue CD and doing an fdisk, wiping everything and creating a new GPT table with only one partition.

Gparted to format single partiton to ext2, to overwrite everyting with an non-journaling file system.

cfdisk to create paritions desired, then Gparted again to format as desired.

Install MX 19.1
 

Castle Robin

Member
Credits
870
For starters, use 19.1.

Recommend starting over with live boot to something like System Rescue CD and doing an fdisk, wiping everything and creating a new GPT table with only one partition.

Gparted to format single partiton to ext2, to overwrite everyting with an non-journaling file system.

cfdisk to create paritions desired, then Gparted again to format as desired.

Install MX 19.1
If I can, I'll use 19.1 which would be best via a USB stick to initially use System Rescue in conjunction with, as it's 50/50 as to whether, even if my computer holds out long enough to download 19.1 to the USB stick (and not cut off, which would mean me having to re-download it, yet again), whether 19.1 on a USB stick would install onto My computer's hard drive given the obstacles I'm facing.

Even then, if I did manage to get MX 19.1 installed to my hard drive, if the same faults exist that block access to MX 17 on my hard drive, I'd be back to square one and wouldn't be able to run System Rescue on the hard drive.

As of now, the instructions Arochester gave me have sadly amounted to nothing, as the instructions he quoted haven't corrected the faults.

Also, System Rescue's download Failed. I just can't believe how much bad luck I'm having with one thing after another in Linux. It's clearly not Linux that's the source of the problem, but my computer, but I want an end to the problems asap so I can have MX 19.1 up and running (which will initiate Libre Office to work properly, as it doesn't in MX 17) on my Hard Drive and hopefully all faults including hardware eliminated, but it depends on what can be done.

I will attempt to re-download System Rescue in a moment, as the web site was hanging in Pale Moon and I've now switched to Firefox.

If it still doesn't download, I'll have to abandon this computer for the foreseeable unless there is another option.

If it does download second time around, I'll then re-download MX Linux 19.1 via the MX 17 USB stick then re-follow Wizard's instructions with DD to install MX 19.1 to a USB stick (as the Gparted partitions are now stuck in the hard drive due to the hardware faults) and use another stick for System Rescue.

Whether any or all of the above will work, given my bad luck, depends on how things progress, but if I can't get System Rescue to work, I'll have to inquire from you and/or other forum members if there is an alternative means to eliminate these faults so I can use my computer for the purpose it's intended for.
 

Castle Robin

Member
Credits
870
At present, I can only run Linux on This computer as MX 17 via the USB stick.

If all works out (as I'm re-downloading System Rescue as I speak, hoping it downloads this time), once I've re-downloaded MX 19.1 from the MX "Mirrors" UK (London) link, recreated the command lines that Wizard from Oz gave me that are lost within the hard drive faults (which should enable MX 19.1 to work from the USB stick), I can then use System Rescue from there.

Otherwise, if I try to install MX 19.1 to my hard drive (at this stage, due to the hardware faults), I may end up experiencing a lack of access to by then MX 19.1 and be back to square one.

I have tried to download System Rescue twice from their official site link. The download has failed both times. Likewise via the Sourceforge link and to equivalents of System Rescue.

I want to get MX 19.1 created on my USB stick then onto my hard drive asap, plus some System Rescue program, but with all these obstacles, I am unavoidably stuck at MX 17 at present, until if/when this computer stays stable long enough to download the MX 19.1 ISO, after which I would still need time to recreate Wizard's instructions.
 
Last edited:

Castle Robin

Member
Credits
870
Absolutely nothing is downloading, so I can't run any form of System Rescue (the literal name software or equivalents) nor MX Linux 19.1.

This must be due to the hardware faults in my computer, as I was able to download programs via MX Linux 17 before today.

This may be my only option, but even then, whether paid (as in this case) or a free download, I can't see it will make any difference, as this computer is acting more erratic than ever today, so I can't use MX 19.1 until the other problems are resolved first:

 

captain-sensible

Well-Known Member
Credits
864
if its a hardware problem then what ever you do is going to be a problem.

There are people on here that know a lot more about hard ware than i do , but try to narrow it down.

On hard disk you can run programs like badblocks, testdisk also if there is data on your main Desktop that you need you can get that off to somewhere else there is ddrescue ;knoppix 8.6 by the way (i checked my kmoppix 8.6 on usb) has all those programs and we can guide

So that would address if it hard drive.

Then there is old time things like temperature increase due cpu paste lacking or going old between cpu and cooller block. Loose wiring connections mole and all those can also cause intermittent issues i've even had a loose wire hitting the cpu fan causing me a problem. i'm sure others will give you things to check psu unit falining etc.

Stack exchange and mention of blocks might mean fsck needs help. it can fail but if the metadata of the file system can be found in one of the copies of the superblocks you can feed that into fsck. I always say make sure you either have knoppix or an alternative ( i've got most tools on a slackware current on a usb stick )
 
Last edited:

sp331yi

Active Member
Credits
1,057
Tough luck, man! To me, troubles point to a hard drive. So, if a spare is available, replace present one and try again, is all I can say at this point. Know that the spare is good, however!

This should eliminate the hdd as an issue, at least. If no-go after trying another good hdd, things don't look good, IMHO.
___________________
Looking ahead:
If USB is working fine, do you have a wireless USB adapter, in case troubles may include a bad NIC?
 
Last edited:

Castle Robin

Member
Credits
870
if its a hardware problem then what ever you do is going to be a problem.

There are people on here that know a lot more about hard ware than i do , but try to narrow it down.

On hard disk you can run programs like badblocks, testdisk also if there is data on your main Desktop that you need you can get that off to somewhere else there is ddrescue ;knoppix 8.6 by the way (i checked my kmoppix 8.6 on usb) has all those programs and we can guide

So that would address if it hard drive.

Then there is old time things like temperature increase due cpu paste lacking or going old between cpu and cooller block. Loose wiring connections mole and all those can also cause intermittent issues i've even had a loose wire hitting the cpu fan causing me a problem. i'm sure others will give you things to check psu unit falining etc.

Stack exchange and mention of blocks might mean fsck needs help. it can fail but if the metadata of the file system can be found in one of the copies of the superblocks you can feed that into fsck. I always say make sure you either have knoppix or an alternative ( i've got most tools on a slackware current on a usb stick )
Sadly this is what I suspected, and with the pandemic, like others in the same boat, I'll have to wait until the Lockdown is lifted before I can get my hard drive repaired or replaced as computer engineers are off work due to the above, but anything that can improve things will reduce my distractions and increase my enjoyment of computing.

By pure fluke, within a matter of time of my previous post, I managed to regain access to MX 17 on this very computer (the one with the hardware faults) which was blocking me access to completing start up due to a repetition of errors being listed.

Everything happened very quickly so I unfortunately can't list every step that I did, but this command was the start of regaining access:

fsck.ext4 -pvf /dv/sda1

I was then faced with additional questions, not anticipating a positive outcome.

No idea what to do, I clicked on "y" for Yes then held the Enter button down which said Yes to everything else.

Then, within a matter of time, to my complete surprise, I saw MX 17 Horizon starting up.

What I can't figure out is whether I'm in SystemD or non-SystemD mode (I prefer without SystemD), as certain changes were made to the system, so I don't know if the default non-SystemD was changed.

The Orage clock (which was 1 hour behind the correct time) now matches the Conky clock time, but the Orage clock now lists the time in 24 hour mode (with the addition of Seconds).

I have used the Terminal for Badblocks, but it's stuck as in the attachment.

I'll close it in about 15 minutes if still nothing happens and switch to Testdisk.

The errors I've encountered are either visual (automatic Shut Downs, Restarting; Monitor freezing the screen then turning the screen off then on again, but with everything intact) or in Error messages that are too quick to log during the Start Up.

Hopefully a single program or series of programs can detect the full extent of Error messages and eliminate the errors (where possible, depending on if the Hard Drive, and if the hard drive pends a repair or replacement).

Due to me regaining access to MX 17 Horizon (pending me, hopefully later today, switching to MX 19.1, if all works fine upon Wizard From Oz's instructions), Downloads are now working again, so I successfully downloaded System Rescue CD, but will use the USB stick version once I have MX 19.1 up and running so that the System Rescue program relates to the 19.1 version.

I will make a note of DD Rescue and other programs/facilities you've quoted.

Any programs/command lines that you and other members can recommend will be most invaluable, as if any errors Are repairable (unless Hard Drive related), I will have less errors to contend with.

From your information, the technical faults on my computer could be caused by one or more sources, depending on where the faults derive from, so any tests (initially with MX 17 then asap MX 19.1) will help detect them, and wherever possible, eliminate them.
 

Castle Robin

Member
Credits
870
if i do go your -y option use it with -v flag as well also to see whats going on. basically -y means fix with no questions asked . So the feeling is a bit like in the old days of Windows- plug and pray, but in this case pray it doesn't fix something you didn't want fixed!
Badblocks has frozen as displayed below for some reason, so I'll try the other test program in a moment to see if that can detect all or at least some faults.

Even if only a fraction of faults can be corrected (depending on the source of the faults), this would increase the reliability of the computer:

Badblocks - Checking blocks, but only this is displayed after 5 minutes.png


I'll have to further study the various Linux codes including "-v flag", as although I first used Linux (Mint Cinnamon) in 2016, I'm a new user to Linux since March 2020, so -v flags are a new concept to me, but like the other information you and others provide in this and/or other topics, this is very useful.

As time goes on, my use of Linux will become increasingly second nature.

I enjoyed using Micro$oft Windows 7 and other preceding Windows operating systems, but since Windows 7 expired, later than planned, I started exploring MX 17 regularly from March, and hopefully later today, I'll have MX 19.1 up and running, so I have the most up-to-date version, and will be able to concentrate on investigating faults with your/other members' help in MX 19.1. :)
 

captain-sensible

Well-Known Member
Credits
864
if you want to run some tests we can do that and see what info comes up. if nothing else it might at least be educational . Almost everything you need is on Knoppix if you have any download facility we can go through how you are going to get a knoppix on a usb
 

captain-sensible

Well-Known Member
Credits
864
if you can have a live OS on a usb with persistence even better. I rate slackware current 64 bit courtesy of Alien Bob using his iso2usb script on a par with knoppix 8.6
 

Castle Robin

Member
Credits
870
Test Disk

As there are various command lines to put in, but it's very thorough, I've just entered a few due to me preparing for MX 19.1, but once I have the updated MX 19.1 installed, I'll re-do the TestDisk command lines (plus those I haven't yet gone through) so that any errors displaying will relate to MX's latest version.

TestDisk Check

TestDisk check.png


TestDisk Installation

TestDisk check.png
TestDisk installation.png


Test Disk - List 1

TestDisk List 1.png


Test Disk - Finalized

TestDisk List - Finalized.png
 

Castle Robin

Member
Credits
870
Tough luck, man! To me, troubles point to a hard drive. So, if a spare is available, replace present one and try again, is all I can say at this point. Know that the spare is good, however!

This should eliminate the hdd as an issue, at least. If no-go after trying another good hdd, things don't look good, IMHO.
___________________
Looking ahead:
If USB is working fine, do you have a wireless USB adapter, in case troubles may include a bad NIC?
I agree.

During start up, I see listings of "VGA" (monitor) errors (maybe this is why the monitor can appear, go blank then reappear (with everything intact)), a Processor 2 error (so Processor 1 must be unaffected) and other error messages are listed, but they are too quick to note in most cases so hopefully the tools quoted in this topic will help pinpoint the full extent of errors and which ones can be corrected.

I have a spare drive, but as part of a laptop, so sadly no spare hard drives in this particular computer to switch to. It's got to be the HDD on This computer.

The laptop has a wireless connection, but I have no wireless USB adapter with either computer.
 

Castle Robin

Member
Credits
870
if you want to run some tests we can do that and see what info comes up. if nothing else it might at least be educational . Almost everything you need is on Knoppix if you have any download facility we can go through how you are going to get a knoppix on a usb
I'll keep this in mind.

I've never used Knoppix, but I have System Rescue CD in my Downloads folder (after I regained access to MX 17 during Start Up), but as I'll be using MX 19.1 soon (hopefully later, if everything goes to plan), but asap, I'll get that installed and then proceed with Hardware related advice once 19.1 is installed.


Some of the Start Up errors that appear (information ascertained before the screen changed so I could only note a fraction of the information) include:-

0.023569 mce Hardware Error TSC 0

012000001000000

0.023600 Processor 2 Error 600f20 Socket

Not Starting NFS Kernel Daemon No exports


You and the others have posted invaluable information between each of you that will help determine precisely what the errors are, where they are, and if/how they can be corrected. :)
 
Last edited:


Staff online

Members online


Latest posts

Top