Hi
I have an Otiplex 780 series Dell desktop with Linux running Linux CNC
In the startup menu the following is listed
GNU GRUB version 1.99-27+deb7u3
Debian GNU/Linux, with Linux 3.4-9-rtai-686-pae
Some time ago, when I went to boot up the computer and cut, I just got a long long error message.
Basically at the bottom of pages of errors it says.
Unexpected inconsistency run fsck manually
fsck died with exit status 4
failed code 4
Automatic file system check failed. Manual fsck must be performed then system restarted
Fsck should be performed in maintenence mode with the root filesystem munted in read only mode
root account is in read only mode. maintenance shell will now be started
su login root account is locked, starting shell
root user#
I have no clue what this all means, and the guy that set up this system originally does not know how to fix this all means either.
Appreciate any help
thanks
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
root user number
-
FreewheelinFrank
- Global Moderator
- Posts: 2117
- Joined: 2010-06-07 16:59
- Has thanked: 38 times
- Been thanked: 232 times
Re: root user number
It means there are errors on the HD that cannot be corrected automatically. The system cannot boot because the errors are on the system partition and it cannot be mounted.
As you seem to have a root prompt, the obvious next step would be to do what is asked and type fsck after the prompt and hit enter.
If there is a specific partition mentioned in error messages previous to the posted output, use that. It would be something like /dev/sd<letter><number>.
fsck (file system check) by itself will ask you if it should correct errors found, to which you have to hit "y" for yes. You can add a -y flag to the command to get fsck to automatically correct errors found.
https://www.tecmint.com/fsck-repair-fil ... -in-linux/
The errors suggest hard disk failure or corruption. It may be that the HD is failing. But try running fsck and rebooting.
As you seem to have a root prompt, the obvious next step would be to do what is asked and type fsck after the prompt and hit enter.
If there is a specific partition mentioned in error messages previous to the posted output, use that. It would be something like /dev/sd<letter><number>.
fsck (file system check) by itself will ask you if it should correct errors found, to which you have to hit "y" for yes. You can add a -y flag to the command to get fsck to automatically correct errors found.
https://www.tecmint.com/fsck-repair-fil ... -in-linux/
The errors suggest hard disk failure or corruption. It may be that the HD is failing. But try running fsck and rebooting.
-
steve_v
- df -h | grep > 20TiB
- Posts: 1418
- Joined: 2012-10-06 05:31
- Location: /dev/chair
- Has thanked: 80 times
- Been thanked: 191 times
Re: root user number
99% of the time, errors like that indicate a hardware (disk) problem. The message tells you what to do to attempt filesystem repair, if you have a root prompt (which is what the '#' indicates), you should run 'fsck' on the partition in question (probably /dev/sda1), accept any proposed fixes, and hope. A simple websearch for "fsck error 4" yields many detailed explanations on how to go about this.
Even if a manual fsck does get the system to boot, I'd consider replacing the disk a priority for continued reliability. At the very least you should pull the SMART data to see what's going on.
If this is a production machine, you should have a backup image or clone to restore to a new disk. If you don't, whoever set it up is a twat and you should make one as soon as you get the machine running.
If a manual fsck does not get the system bootable, chances are sufficient filesystem damage has already been done that a restore from backup or reinstall and (attempting) recovery of CNC data is the best (or only) solution. The latter is probably beyond what someone can talk you through on a forum though, especially one catering to current Debian rather than LinuxCNC specifically. Kernel 3.4 is ancient, and LinuxCNC differs significantly from vanilla Debian.
Even if a manual fsck does get the system to boot, I'd consider replacing the disk a priority for continued reliability. At the very least you should pull the SMART data to see what's going on.
If this is a production machine, you should have a backup image or clone to restore to a new disk. If you don't, whoever set it up is a twat and you should make one as soon as you get the machine running.
If a manual fsck does not get the system bootable, chances are sufficient filesystem damage has already been done that a restore from backup or reinstall and (attempting) recovery of CNC data is the best (or only) solution. The latter is probably beyond what someone can talk you through on a forum though, especially one catering to current Debian rather than LinuxCNC specifically. Kernel 3.4 is ancient, and LinuxCNC differs significantly from vanilla Debian.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
Re: root user number
Hi
I tried fsck and said yes to fix error, but it didn't do anything
I tried ctrl d and tried to start it in recovery mode and now its going through a list of something like this
0-1/input0
1188.5840431 usb disconnect device number 20 this number keeps going up
bunch of numbers new low speed usb device number 21 using uhci_hcd
bunch of numbers new usb device found
new usb device strings
product optical mouse
manufacturer pixart
what does all this mean? The device number keeps going up with a slight variation of the message, but mostly the same.
what would cause the drive to fail, as this was not a high use machine
we quit the business and I used it of and on
Thanks
I tried fsck and said yes to fix error, but it didn't do anything
I tried ctrl d and tried to start it in recovery mode and now its going through a list of something like this
0-1/input0
1188.5840431 usb disconnect device number 20 this number keeps going up
bunch of numbers new low speed usb device number 21 using uhci_hcd
bunch of numbers new usb device found
new usb device strings
product optical mouse
manufacturer pixart
what does all this mean? The device number keeps going up with a slight variation of the message, but mostly the same.
what would cause the drive to fail, as this was not a high use machine
we quit the business and I used it of and on
Thanks
Re: root user number
it seems like whatever it was going through was fix mode, because it seems to work
Is it possible that this could have happened because the computer was on but not being used, and somehow developed all the errors?
Either way, thanks everyone for your help
Is it possible that this could have happened because the computer was on but not being used, and somehow developed all the errors?
Either way, thanks everyone for your help
-
steve_v
- df -h | grep > 20TiB
- Posts: 1418
- Joined: 2012-10-06 05:31
- Location: /dev/chair
- Has thanked: 80 times
- Been thanked: 191 times
Re: root user number
Good to hear, if fsck prompted you to say yes at some point then it likely did repair some filesystem corruption.
Could have been some transient event or even a loose cable, hard to say. Or it could be that your disk is failing, as they are wont to do at random, and in any case you should still make that backup.
Could have been some transient event or even a loose cable, hard to say. Or it could be that your disk is failing, as they are wont to do at random, and in any case you should still make that backup.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
-
pbear
- Posts: 329
- Joined: 2023-08-27 15:05
- Location: San Francisco
- Has thanked: 1 time
- Been thanked: 57 times
Re: root user number
The most common scenario is the opposite: system freeze, power failure, or shutting down the computer with the power button rather than using the operating system procedure. File system corruption when the computer is powered up but not doing anything almost would have to be hardware failure, but sometimes things just happen.
Research how to boot a live session of Linux. One of the current versions of Debian will be fine, but there are other options. Once booted, you will have a full-featured desktop with which to look at files on the old system and copy to USB drive those you want/need to keep. You also could use the live session to install Debian, but that's not necessary to access and/or copy files.