Im trying to fix a disk which is inaccessible.
Its using LVM2
From a rescue disk I can scan and see the LVM device fine.
When I try to mount it fails.
When I run e2fsck it says "recovering journal" and then fails with "unable to set superblock flags"
I have tried running e2fsck -b 32768 (and other backup blocks) and it just says "recovering journal" and then fails with "unable to set superblock flags"
I decided I needed to expand my openSUSE partition because I was running out of room. There was some unallocated space following my /home and swap partitions that I wanted to assign to my / partition.
So after taking note that bad things could happen (as I've read everywhere), I got myself a copy of GParted (since Yast! partitioner doesn't move partitions, does it?) to start getting the thing to work. Well, actually, I got PartedMagic which has GParted (I realize it could be a problem NOW if they didn't have the latest version).
So the first step was to move the swap partition. I decided to do it one step at a time and only moved the swap partition to the end. That turned out fine...no problems whatsoever.
The next step is where the problem came in. It was moving the /home partition. It took a while to move but once it got to the end, it showed a message that was similar in nature to "error detected" without giving a long list of error messages. If it did, I probably would have copied it down. There wasn't anything in the "logs" either in GParted besides what it showed. Looking back, I probably should've went into /vars/logs to get additional log information but I guess I wasn't smart enough to do so (provided that GParted does leave log messages there which I think it does).
After that, it refreshed the drive and it ended up showing no partitions with an error and saying the only thing it can do is create a new partition table. After that, openSUSE wouldn't boot. After loading, (both normal and failsafe modes) it gives me the message in the link at the bottom. I can still access those partitions fine. Nothing's corrupted. Windows also boots up fine (it's on a different drive though) and reads the affected drive fine. Linux-based LiveCDs (including openSUSE 11.3) reads the partitions fine too.
I've tried using e2fsck on my ext4 partitions with commands I found during a search and they seemed to "fix" those partitions but it still won't boot and gives me the same message. Looking at it carefully, it seems the reason it can't find a superblock is because it can't find part8 of whatever that thing under /dev/disk/by-id/ is.
I would very much prefer a failsafe (or at least mostly failsafe) solution that won't (or is unlikely) to result in requiring the restoration of a backup but I do understand that there is always the chance of something going wrong that will kill everything. Considering that I can still access the data on that drive, I don't believe the data is corrupted. Maybe the drive itself (as in whatever signatures it may leave) but not the filesystems.
This is what I end up with trying to boot into openSUSE (sorry, I don't know how to get the log when it doesn't put it in logs directory: https://docs.google.com/leaf?id=0B3A...ut=list&num=50
One of my raid disks (was a software raid5 with 4 drives) failured. I wanted to buy a new 1.5TB harddisk anyway so i i copied all the Raid data onto the new disk and disconnected the old ones. But then the new Disc crashed right before i could mirror it with another 1.5TB disk. So i need to reassemble my old Raid 5 now. I connected the drives in the former order except the first one, because this was the failed disk. The problem is, mdadm can't find the raid, no superblocks. Fdisk doesnt show mdraid superblocks, too. But fdisk has never showed superblocks. The thing is, this raid was crypted, but i crypted the /dev/md0, so this doesn't affect anything here, or?
some infos:
Code:
server:~# mdadm --misc -d /dev/sda
mdadm: option -d not valid in misc mode
server:~# mdadm --misc -t /dev/sda
[code]....
Disk /dev/sdc doesn't contain a valid partition table But fdisk always said there is no valid partition table and the raid was working.
I have a x64 OpenSUSE server with two hard drivers installed. The first one is used for the / and /home partitions and the other is for backups. Ironically enough it is the backup hard drive I am having trouble with. I was having trouble writting to the drive and unmounted it to preform a fchsk, however now when ever I try to mount it I get the following error:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Does anyone know who I can repair the drive and retrive data?
After several crashes during videos it seemed like a good idea to fsck root. Downloaded the latest systemrescuecd and ran it at boot. The error message was 'bad magic number, corrupt superblock' with a suggested command to try another superblock. That failed with the same message. Tried tune2fs to force fsck at boot and got the same message. The drive is less than 6 months old and the installed system is working more or less ok. The command I used was 'fsck.ext4 /dev/sdc2'. What am I doing wrong?
View 9 Replies View RelatedI recently decided to build up a Linux computer with the following configuration:
- Motherboard : MSI KT4 Ultra
- CPU : Athlon XP 2000+
- RAM : Kingston ValueRAM (2 DIMMs, I put them in all possible arrangements)
I doubt other compoment details are relevant, but if you do think so, feel free to ask.
I installed Debian 5.05 on that machine ; it worked all fine.
However, given that my mobo would not support wake on lan (and that I needed it given that my goal was to build some sort of server), I searched for a new one that did, I then installed an ASRock K7S41GX.
Since doing so, I have not been able to boot Linux ; after doing some fixing on my part, I have come to the point where I have the very same error repeating times and times again every time I try to boot ; here's the error message I get and how I get to it.
GRUB loads like a charm, then Linux starts booting and stuff happens :
Checks filestystem, initrd and stuff (I actually don't understand that part, but it seems to work OK).
Where "########" stands for a series of eight hexa chars (I assme these might be memory adresses ?).
A few more details :
- The ########'s are NOT the same on each attempt to boot.
- When I try to reinstall Linux, I also got various error messages (Mosty "PANIC: attempted to kill init" or "PANIC: attempted to kill the idle task")
- Rescue mode fails the same way re-install does.
- For some reason I just can't explain I ONCE happened to manage to start the installer process, which unfortunately ended up hanging on "Detecting Network hardware". (I attempted to disable the onboard network device to no avail).
I am unable to boot my server and it is erroring with the message "Kernel panic - not syncing: Attempted to kill init!". Here are the details:
I have a brand new Dell PowerEdge T110 server with Quad-Core Xeon CPU and 2GB 1333MHz RAM. I have installed a hard disk (SATA, 7.2rpm) on this machine that I removed from another Dell PowerEdge T100 server with Dual-Core Xeon CPU that was running software RAID 1.
Now when I boot the new T110 server, it displays the following error messages code...
I am running CentOs v5.5 x86-64. If I put the hard disk back into T100, it boots fine. I do not know why it is not working with T110 server.
I have an mdadm linear array of 4 500GB drives. One of them had a few bad sectors, so I've dd'ed it to a new one (conv=noerror), and tried to start my array. Mdadm refuses, saying, "mdadm: /dev/md4 assembled from 3 drives - not enough to start the array."I had diffed different samples from different positions on the source and the mirror drive and confirmed they were identical. Checking the superblocks confirms three old drives still having their superblocks as expected, while the newly mirrored one has,
daniel@lnxsrv:~$ sudo mdadm --misc --examine /dev/sdf1
mdadm: No md superblock detected on /dev/sdf1.
- and,
daniel@lnxsrv:~$ sudo blkid /dev/sdf1
[code]....
As before. The mirror apparently has no uuid, but the original does. To confirm my sanity, I did,
daniel@lnxsrv:~$ sudo dd bs=1M count=50 if=/dev/sdc of=./sdc && sudo dd bs=1M count=50 if=/dev/sdd of=./sdd && sudo diff -s sdc sdd
50+0 records in
[code]...
How can the uuid not be the same when bit-for-bit from the very first byte of the drive, covering MFT etc., these two drives are identical according to diff?
I got a CentOS server + KDE from a server (which I had no contact until now), he had 2 HD's one for the system and another for files.
I brought the HD system home to try to make it run on a virual machine (VMware) so I can do some testing before you put in practice.
But already converted the VMware HD to the system, it tries to start but it shows some errors and in a message "kernel panic - not syncing: attemped to kill init"
I think the drivers are correct, has edited the file "/ etc / modprobe.conf" edited these entries equal to another I installed CentOS on VMware.
alias scsi_hostadapter mptbase
alias scsi_hostadapter1 mptspi
ata_piix alias scsi_hostadapter2
Look at the picture attached the full error.
Link to large image
Link to large image
OS: Debian unstable 32bit, kernel 2.6.32-2, grub 1.98 from late january 2010 (only have working net-access from work now, so I am grabbing information from memory). EXT3 and EXT4 support is compiled into the kernel along with chipset/scsi/sata support (not as modules), and I have tested to boot ext3 with it before proceeding. Prereq: my old disk started to have too much S.M.A.R.T errors, so I bought another one, put in a USB cabinet, added swap and ext4 partition/filesystem to it, and copied over all data from the old system to the new that was mounted at /dest using the command "find ./ -xdev -print0 | cpio -paV0 /dest". Swiched disks, so I now have the ext4 disk sitting at /dev/sda (partitions: sda1 => ext4, sda2 => swap), and booted into rescue-mode from cdrom, using /dev/sda1 as root with a shell on. After doing this, I performed the following commands:
mount --bind /dev /dest/dev
chroot /dest
modified the /etc/default/grub to instruct the kernel to boot using ext4, ran grub-install --recheck /dev/sda
ran update-grub to modify /boot/grub/grub.cfg (which looks as it should) After doing this, grub finds my partition and mounts it. It however stalls with the message: "warning: unable to open an initial console" and does nothing after this point. I have no ramdisk, but my old kernel booted fine from ext3 (and still does if I copy it to a ext3 partition), and since the ext4 support is compiled into the kernel - should I really need a ramdisk?
I'm trying to get some data off of an external harddrive. I get a few errors:Unable to mountError mounting: mount: /dev/sdb1: can't read superblock.I then tried to run a read disk benchmark on disk utility and that seemed okay.I then tried
Code:
ubuntu@ubuntu:~$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 320.1 GB, 320072933376 bytes
[code]....
This computer that I got as a gift runs windows just fine but being as I am a linux fan I would really like to run linux on it.I tried installing Ubuntu on the PC but it just caused some very very strange problems. (Text placed randomly on the screen + strange sounds coming from the computer).I tried installing Gentoo (my favorite distro) on the PC and it can't find the superblock on the drive. (Error during bootup)I low level formatted the drive and repartitioned it before installing gentoo.
View 14 Replies View RelatedI have come across a problem on my Scientific Linux, I have searched the forum but couldn't find what I am looking for, so I decided to post my question here.well, here what I did: under the Terminal I got Cramfs-1.1.tar.gz installed, and then i used the "make" command to build the cramfsck and mkcramfs and it was all successful.so now I have an image I called it "backup.img", and I tried following command:./cramfsck -x ./output backup.imgbut unfortunetly I got the following message:./cramfsck: superblock magic not foundSo I kept on thinking what is this Superblock magic thingy? I did a google search but I kind of got lost and didn't end up finding anything useful, but I am just thinking it could be some kind of package which I need to install? I tried the following command:apt-get install magicbut it seems there is not such package exists with that name.
View 6 Replies View RelatedI need to restore a superblock on a RAID5 software array. But I'm not sure if I'm meant to restore it from MD0 or a device such as SDA1? From what I read, superblocks are stored on each drive, but I'm not sure if this is changed when a software raid is in use.
View 1 Replies View RelatedI want to populate an array of string by files exists in directory on mounting of file system. I got an entry point for file system mount. I can use either do_mount function or fill_superblock function. But I am not clear about how to call readdir from there itself. I need inputs for calling readdir from fill_superblock function.
View 2 Replies View RelatedI'm logged into a server through the CLI and did a df -T and confirmed all my volumes are ext3. but when I do a tune2fs -l /dev/sde it tells me
tune2fs 1.39 (29-May-2006)
tune2fs: Permission denied while trying to open /dev/sde
Couldn't find valid filesystem superblock.
I don't have root access on the server, but is that why it's complaining, or is my syntax incorrect?
I have a problem in my ubuntu 10.01 that it can't load a drive/volume in ubuntu. When I tried, it said: "Unable to mount location Error mounting: mount: /dev/sda1: can't read superblock". And when I boot my pc with 'Windows', it said : "UNMOUNTABLE_BOOT_VOLUME" under a blue screen. What can I do to solve this problem?
View 9 Replies View RelatedI am having a rather strange issue. I have windows 98 installed into a disk image that I use bochs to boot it with. I want to transfer some files to the image but now I am unable to mount it. I will attach the drive to the loopback device but when I go to mount I get wrong fs type bad option ... etc.
The command I used to mount was
Code:
#mount -t vfat /dev/loop0 /media/loopdisk
cfdisk shows it ok as does fdisk. shows as a fat16 file system. When I attempt to check it for errors using fsck.msdos I get
Code:
# dosfsck 3.0.6 04 Oct 2009, FAT32, LFN
# Logical sector size (64543) is not a multiple of the physical sector size.
When I boot into windows 98 in bochs and check the disk it tells me there is no problems.
I had very recently installed a new hard drive on my laptop. After installation, I tried to install linux from the CD and followed the instructions. I did not create a partition in the hard drive and carried out the installation procedure. After installation, i tried to start but it would not start...and shows error. I am not sure what I should do ...please instruct me in a step by step procedure to solve the problem
View 1 Replies View RelatedI have a NAS from WD that runs some stripped down flavor of linux. The NAS has one USB port at the back which can be used to expand the storage. If I plug in an external disk formated in either NTFS or HFS+ then the system automatically mounts the disk and shares it over samba. If I plug in a disk that is formated in ext3, the disk is recognized but that's about it. It doesn't mount or get shared or anything. I have tried asking WD about this and I have tried asking google. But after two days of searching I am turning here for some more expert advice.
Here is what I've managed to figure out so far.
If I check dmesg before and after plugging in the ext3 usb disk I have found out that these lines are added to the log:
Code:
I have tried googleing those last two lines but I haven't found any info that I can make any sense of.
If I run the command "mount -a" I get the following messages from the shell: "mount: Cannot read /etc/fstab: No such file or directory"
Hover I am able to mount the ext3 disk manually. First I get this info from fdisk
Code:
And then I run these two commands:
Code:
This makes the usb disk visible in the shell, but since this is a NAS, it is kinda useless as long as it doesn't show up in samba.
Since I'm pretty new to linux I don't know what to try next so I'm hoping for some advice as to what I can do to make the ext3 usb disk automount.
After completing the installation of Fedora-FEL edition, I cant boot from my hard disk. "No bootable device found " error appears.
I have one Windows XP & 2 Linux installation in my disk.
I tried to restore grub using "setup (...)" command.but same error repeats.
Even I cant restore Windows XP using "fxmbr" command in... recovery console .
But I can boot from that drive by "chainloader" command in grub. code...
Running above command in grub terminal boots my hard disk ("hd1" is my "unbootable disk")
My laptop's been locking up in Linux (Ubuntu, Backtrack, Puppy) periodically for a while now. When it locked up, it was always immune to the magic of SysRq, which I thought might indicate a hardware problem. It became so bad that I had to stop using the laptop.
Today, when I turned it on and tried to boot into Fedora 12, I got the following error (just once, it just locked up at various points during the splash screen after this once):
double fault: 0000 [#1] SMP
last sysfs file:
CPU 0
odules linked in:
Pid: 1, co m: swapper Not ta nted 2.6.32.11-99.fc 2.x86_64 #VGN-T 250N
RIP: 0010:[<ff
All the seemingly missing letters were really missing, not my typos.
As you can see, kernel version is 2.6.32.11-99.fc12.x86_64 and my laptop is a Sony Vaio TZ 250N (Core 2 Duo ULV 1.2GHZ). Note that with the other remaining kernels from the updates, nothing ever happened other than the locking up. The core temperatures hover pretty high, about 55-60C peak but this is still below the critical temp. Memtest came up clean when the problem first started happening.
i am trying to create an image of Slackware OS but vmware is not able to detect the disk. it gives me below error, "Unable to detect disks or volumes on the source machine. Make sure that the source is a supported linux distribution." can some one tell me what do i need to do to create the image.
View 2 Replies View Relatedi used to have ubuntu 9.i decided to move to sabayon so i used the live cd to install it ,resize the ubuntu partition and use the remaining space for sabayon.while the resizing procedure i got an error(i dont have a copy of the error log file but i know it has something to do with an anaconda process).i aborted the installation and the result was an filesystem that couldnt be mounted.when i try to mount the hdd i get this:
Code: Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so and this is what i get from fsck: Code: $ sudo fsck -f /dev/sdb1
code....
What different between Segmentation fault and aborted
When I read about dbg I make different reason from the tutorial ....with the same code
Example in tutorial the gdb Display a message like this
Code:
And in my computer I have
Code:
I want to know what the different between them
I have a problem with a directory which contains my music collection. It can't be opened; all other directories work fine. I can cd into my ~/Music directory, but ls gives segfault and KDE programs hang when trying to open this directory. The problem probably has appeared after the rename of subdirectory under the Windows (don't remember particular ext3 driver; can check tomorrow).fsck says that the partition is fine. The whole disk is mounted on the single partition. Windows is located on another physical disk.Is there any way to recover my directory?
View 4 Replies View RelatedI have been trying for like 2wks to figure out why I keep getting seg faults in Viper WM from slackbuilds.I have it on 6 diff versions of slack, 12.2-current and also in debian and arch.In all of them VWM crashes with seg fault?!I really like it alot and need to figure out what the issue is?
View 2 Replies View RelatedI am using RHEL, and trying to execute a c program.I'm able to compile properly and execute until i reach a function getHandle, where the program gives a segmentation fault. Segmentation fault occurs in getHandle().
Here is the code:
My system is running with powerpc and linux, i am facing some kernel crash problem.
I have pasted the trace and log
(1) Display the backtrace for the thread that crashed.
(2) Display argument parameters and local variables for the thread.
I got segmentation fault error when I execute "procinfo -a" but not a problem when I just execute procinfo.
View 3 Replies View Related