I have an old system working with linux, suddenly i have faced that issue that the system can not be booted again
im afraid to lose data so i still did not do anything with it
Tried to ls the logs in side /var/log but im able to ls only the main root folder if i tried to go to inside /var folder for example im not able
The message that are repeatedly appear start with "The superblock could not be read or does not describe a correct etx2 filesystem … ends with try to use alternative superblock " i did not tried it yet cause im not have that experience that make me know what is the next step that i will faced it and im afraid to lose the data
You choose OTHER VERSION for the first and most important information to provide when asking for help. You describe your system as “old system working with linux”. That is not very helpful. Please tell which version you use so that others can at least try to imagine your environment.
When the superblock of a file system is damaged, it means that either it is corrupted (overwritten) by other software, or the hardware of the device (the disk) is damaged. As the superblock is the most important starting point for interpreting a file system’s structure, it is a very severe situation. The only thing you can do is trying an fsck as the message says. It seems not to be your root file system, because the system is running (albeith in recovery mode).
Your picture does not show which partition this is about. The most I can see is /dev/sd…
So take a note what /dev/sdXN it is and then run
e2fsck /dev/sdXN
As the message says, when this does not help, you can try
e2fsck -b 8193 /dev/sdXN
When this is all in vain, I am afraid you have lost your file system.
A check on the disk hardware is then the first thing to do. When the disk still seems usable, then a new file system can be created (and the data restored from your backup), else the disk is for the dustbin.
Do you mean that you do not even know what Linux (distribution and version of it) you are running? You only show that kernel 2.2.16 is used, but the date is not complete (the year seems to start with 20, which can be as many as 17 years back).
Why are you doing things with /dev/, /dev/sd, and who knows what all before you settle for /dev/sda2? You should use the file that is mentioned in the original error message and nothing else. Do you want to destroy things? What is the correct device file as mentioned in the error message. I still do not know that.
In the error message in your picture there is a suggestion to use the alternative superblock and in my suggestion repeats that:
e2fsck -**b** .........
Why do you use then
e2fsck -**d** ......
Again, making such typos in such a situation can destroy more then you ever can repair.
And when after that typing eroor, the tool tells you that -d isn’t correct and shows you waht options are available, you still do not do the correct thing.
I do not understand the last picture, There is only some output, but no information about the command that was given.
You are doing all sorts of commands I did not suggest. I am sorry to say, but seeing what you did until now, if I were you, I would be very careful in typing commands I do not thoroughly understand.
yes i do not know the distribution and version
and i used uname comaaned to let you see what im seeing if i tried to figure it.
Why are you doing things with /dev/, /dev/sd, and who knows what all before you settle for /dev/sda2? You should use the file that is mentioned in the original error message and nothing else. Do you want to destroy things? What is the correct device file as mentioned in the error message. I still do not know that.
im trying to let you see the system status, and how can i make sure where is the system device located ?
In the error message in your picture there is a suggestion to use the alternative superblock and in my suggestion repeats that:
e2fsck -**b** .........
Why do you use then
e2fsck -**d** ......
Again, making such typos in such a situation can destroy more then you ever can repair.
And when after that typing eroor, the tool tells you that -d isn’t correct and shows you waht options are available, you still do not do the correct thing.
sorry it seems i mixed between b and d
I do not understand the last picture, There is only some output, but no information about the command that was given.
forgot to tell
the last picture, it is the output of the command “dmesg”
You are doing all sorts of commands I did not suggest. I am sorry to say, but seeing what you did until now, if I were you, I would be very careful in typing commands I do not thoroughly understand.
so could you please guide me through everything that you need and how to do it ?
ill do what ever you need to provide and exacly the steps that you telling.
And please take care to type this without any typing errors!.
No, that is not what Malcolm said. He said to POWER DOWN. Not to reboot.
He said “power down” to prevent more damage done. And he then advised you to contact any Linux people in your neighbourhood that can help you by visiting you and the system (or you taking the system to her/him/club).
That will be much more effective then this conversation where you show pictures with characters lost and type d instead of b without even noticing.
/dev/sda2 was already OK as shown in pictures. Kernel messages show problem with /dev/sda6 (device 08:06). To say anything at all, one needs to know expected layout (at least /etc/fstab from this system) and current partition table.
I have checked it put and figure that /dev/sda2 was someone brfore me trying to use it so it appears in that picture
so we are back to the first point
how can i know the right device
I have used this command and got “ can not open /prod/partitions
I feel you and i feel that you don’t have mutch to help with, so im trying my best to understand that old system but i do not get it here from any one and no one can here can help with it.
![http://a.up-00.com/2017/12/151349792636991.jpeg[/FONT]](http://a.up-00.com/2017/12/151349792636991.jpeg%5B/FONT%5D){kind=link}
![http://a.up-00.com/2017/12/151349792758692.jpeg[/FONT]](http://a.up-00.com/2017/12/151349792758692.jpeg%5B/FONT%5D){kind=link}
![http://a.up-00.com/2017/12/15134979285583.jpeg[/FONT]](http://a.up-00.com/2017/12/15134979285583.jpeg%5B/FONT%5D){kind=link}
