Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
my disk has three parts, but one of these can't be mounted. Is the main one, which used to be root.
Quote:
Error mounting /dev/sda3 at /media/znt/162aab85-3bce-4235-8c4b-cee4ec5da114: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sda3" "/media/znt/162aab85-3bce-4235-8c4b-cee4ec5da114"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sda3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
(udisks-error-quark, 0)
The syslog as follows:
Quote:
May 26 18:23:56 znt-Infoway kernel: [ 3064.902224] JBD2: Unrecognised features on journal
May 26 18:23:56 znt-Infoway kernel: [ 3064.902231] EXT4-fs (sda3): error loading journal
Around the web I collected some information about the procced that would to be. People made mention about tune2fs command and "has_journal" feature, in order to solve that. However, the partition can't be tuned either, according to this:
Quote:
tune2fs 1.42.5 (29-Jul-2012)
tune2fs: Filesystem has unsupported read-only feature(s) while trying to open /dev/sda3
Couldn't find valid filesystem superblock.
would be nice to post
1. more details, like what OS / version is it (including kernel)
2. what [related] software is installed/used
3. the exact commands you executed.
4. did it work before? What did happen ?
no, ubuntu 13.04 is not supported at all. It is discontinued long time ago. https://en.wikipedia.org/wiki/Ubuntu...aring_Ringtail)
Upgrading is probably possible, but you need to step one by one, 13.04 -> 14.04 -> ...... 22.04, more than 10 steps. I would rather try to reinstall the whole os in one (which is actually much faster). Just make a backup first. But probably you can just try a new live cd without installing anything.
I think this problem is already solved long time ago, just you need to use a more recent kernel (and os). https://www.reddit.com/r/linuxquesti...d_features_on/
Could you suggest a distro? i386
How is the right way to make a LiveUSB?
The partition issue is related with kernel version?
I tried to boot a ISO from grub, with loopback command.
Quote:
loopback loop /img.iso
I load the kernel and intrd right, but i got the message
Quote:
[End Kernel panic Not syncing: No working init found. Try to pass init=option to kernel
Your dd command looks okay. Keep in mind that you need sudo privileges and that the paths be correct.
As far as the hardware, based on the RAM, I recommend an XFCE desktop as it uses less RAM, with MX Linux being a good lightweight distribution, even though I think it is not suitable for beginners. Another one that is lightweight is Bodhi Linux. If it is a Core 2 Duo CPU you should be quite okay.
For your original problem I am a bit lost. Did you actually try to mount a root partition through a different (or live USB) operating system? Otherwise I do not see why you should try and mount a root partition at /media.
Your dd command looks okay. Keep in mind that you need sudo privileges and that the paths be correct.
As far as the hardware, based on the RAM, I recommend an XFCE desktop as it uses less RAM, with MX Linux being a good lightweight distribution, even though I think it is not suitable for beginners. Another one that is lightweight is Bodhi Linux. If it is a Core 2 Duo CPU you should be quite okay.
For your original problem I am a bit lost. Did you actually try to mount a root partition through a different (or live USB) operating system? Otherwise I do not see why you should try and mount a root partition at /media.
Thanks, i will check it out.
About the original problem: in fact, I'm trying to recover the partition, that was used to as root, but for now is just a chunk of umounted blocks.
I thinks installing a OS using it, without formating it, could I review it someway, if all other methods were useless.
Thanks for replying.
had established a system with the DebianEdu distribution, which crashed. My disk is divided into 3 parts, and one of them contains some files and materials that I don't want to lose.
Through an ubuntu Live CD, I noticed that the partition in question was not mounted. I tried manually, without success. I installed ubuntu on the disk with the same orders (boot, root and swap in the relevant partitions) without formatting, but for whatever reason GRUB didn't load the kernel, leading me to the "GRUB rescue" prompt, in DOS apparently. I installed the system on a flash drive and now I can load it normally, but its use is compromised for obvious reasons. Actually, the intention was to set up the system to do the necessary searches to recover the partition that is not being mounted, but I can't load the web pages or install the packages. Ubuntu is old and it is not possible to update for some reason.
I downloaded Kali because it was the only "channel" with which the connection could be established. I intend to install it on the disk (not on the pendrive), using the partition in question, without formatting it, in order to recover the files. How should I configure this installation?, please and, if it is not recommended, either for innocuity or any other reason, I wait for someone to say. In case there is (and of course there is) an "ideal" way to recover this partition and someone is willing to share the knowledge, I'm here for it. For reasons of practicality I thought of doing it in such a way.
I use open-source: MuseScore to compose music, graphic software, IDEs... I develop applications, I know Apache and I program in PHP. I liked Debian I must say, he that introduce to MuseScore. Technically or apparently there was no reason for the system to crash.
Once the material is recovered, I can format the disk and, free of the boot problem, install any other system. Please, I'm hoping for some advice or possibly support to resolve this issue. I don't use pentest or forensic programs, I just want to recover the files.
Summarizing, i lay the issues ..
To install kali, I need to boot it from USB (where my current OS is running) trhough the GRUB, with loopback command, or from another one, that's empty. I tried the first already, I might load the kernel and initrd right, but it breaks with the message
Quote:
End Kernel panic Not syncing: No working init found. Try passing init=option to kernel
So, which would be this init related argument to pass for?
About the second, it's just a create a bootable disk question... Tried with 'dd' command, but the copy wasn't made wright. Can't find out the reason. There's a proper way to execute it? I tried more than one.
Ubuntu offers a Sratup Disk Creator, a tiny GUI program to create the bootable, but this embbed a boot has noting to do with the iso file.
Nevertheless, I hope for a way to recover the partition, which is manly reason. Below is the kernel log when i try to mount it out
Quote:
May 27 08:31:37 znt-Infoway kernel: [17270.587704] JBD2: Unrecognised features on journal
May 27 08:31:37 znt-Infoway kernel: [17270.587713] EXT4-fs (sda3): error loading journal
Around the web people made mention about the 'tune2fs' command, in order to solve that. Can't make it either
Quote:
znt@znt-Infoway:~$ sudo tune2fs -O ^has_journal /dev/sda3
[sudo] password for znt:
tune2fs 1.42.5 (29-Jul-2012)
tune2fs: Filesystem has unsupported read-only feature(s) while trying to open /dev/sda3
Couldn't find valid filesystem superblock.
I thinks installing a OS using it, without formating it, could I review it someway,
No.
Quote:
bad superblock on /dev/sda3,
It appears the filesystem is corrupted. fsck should be able to repair it but I would suggest cloning the partition first. Looks like everything is on your root partition.
It appears the filesystem is corrupted. fsck should be able to repair it but I would suggest cloning the partition first. Is there data you need to recover? Does the /root partition also contain home? Which partition contains the data you want to recover?
For cloning I would need to space? In this case couldn't.
How to repair it?
Thanks in advance.
I installed ubuntu on the disk with the same orders (boot, root and swap in the relevant partitions) without formatting, but for whatever reason GRUB didn't load the kernel, leading me to the "GRUB rescue" prompt, in DOS apparently.
If I understand your post, you tried to install Ubuntu on the same disk as your debian? I would of expected a whole bunch of errors since your root partition is corrupted. I am not sure if you overwrote the filesystem or not. Is your only tool the Ubuntu Live USB?
If I understand your post, you tried to install Ubuntu on the same disk as your debian? I would of expected a whole bunch of errors since your root partition is corrupted. I am not sure if you overwrote the filesystem or not. Is your only tool the Ubuntu Live USB?
Yes, is the only. I've Hiren's Boot too, not so experiencied with.
I installed Ubuntu in the same disk, the only error came across was the mentined, that leads me to the grub rescue out.
However, you throw a light.. How could I repair the partition?
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.