similar to: root filesystem problem

Had two scsi hard drives. One went bad. The bad one had lilo in the MBR. Removed the drive. Then used the Mandrake install cd to boot into rescue mode. Was able to mount all filesystems within rescue mode on remaining hard drive (HD went from sdb to sda). Only glitch was that I could not mount root filesystem as type ext3 -- had to mount as ext2. Modified the lilo.conf file and ran lilo with new

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

greetings one and all. when attempting to install centos 6.8 to an i386 mid tower, during setup of hard disk partitions, selection is for /dev/sde. if continued, after reboot, error is displayed after 'welcome to centos'. lines read: Checking filesystem fsck.ext4: no such file or directory while trying to open /dev/sda3 /dev/sda3: The superblock could not be read or does not describe a

Ok, I give up... I have to ask. This is CentOS 5. I switched one of my raid1 disks, and I already thought I had succeeded. But now it seems that something is very wrong with the first partition on the new disk. Luckily my system is fully bootable with the other disk. Here's some info. The new disk is sdb. // I removed all partitions with parted, and created the first one again. // parted

Hi folks, For unknown cause I encounter following mounting problem; # /mnt/hda8 mount: wrong fs type, bad option, bad superblock on /dev/hda8, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg | tail via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000)

Hi all- I corrupted my filesystem by not doing a RTFM first... I got an automated email that the process monitoring the SMART data from my hard drive detected a bad sector. Not thinking (or RTFMing), I did a fsck on my partition- which is the main partition. Now it appears that I've ruined the superblock. I am running Fedora Core 6. I am booting off the Fedora Core 6 Rescue CD in

I am unable to mount an ext3 filesystem on RHEL AS 2.1. This is not the boot or root filesystem. When I try to mount the file system, I get the following error: mount: wrong fs type, bad option, bad superblock on /dev/sdj1, or too many mounted file systems When I try to run e2fsck -vvfy /dev/sdj1 I get the following error: Group descriptors look bad... trying backup blocks...

This is CentOS-6x. I have cloned the HDD of a CentOS-6 system. I booted a host with that drive and received the following error: checking filesystems /dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000 blocks /dev/sda1: clean, 47/120016 files, 80115/512000 blocks /dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks

I have a CentOS-6.8 system which has a suspected HHD failure. I have booted it into rescue mode from a CentOS-6.5 minimal install CD in order to run fsck -c on it. The system hosts several vms. I have activated the lvs associated with these vm using pvscan -s ; vgscan ; vgchange -ay. An lvscan shows the lvs as ACTIVE. None are mounted. When I try to run fsck on any of them I see the

I posted this to the Fedora-list, but thought I might get some additional information here as well. I have a HD that refuses to mount with a 'bad magic number in super-block'. I'm running FedoraCore 6 x86_64. [root at moe ~]# fdisk -l /dev/hdc Disk /dev/hdc: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes

i noticed that the 4.4 upgrade broke LILO on Raid... it gave errors on partitions not on the primary disk along the lines of "/dev/dis: no such device"... even explicitly installing the boot sector on each device in the array, while it allowed the system to boot, gave errors at boot time and did not display the CentOS boot screen anymore... i solved the problem by creating a

On Wed, Feb 18, 2015 at 9:47 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Wed, Feb 18, 2015 at 09:41:52AM -0500, Leonard Basuino wrote: > > On Wed, Feb 18, 2015 at 6:52 AM, Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > On Tue, Feb 17, 2015 at 01:37:55PM -0500, Leonard Basuino wrote: > > > > I get the following debug

Hi All, One of my servers upon a restart today comes up with an error checking filesystems: fsck.ext3: no such file or directory while trying to open /dev/VolGroup-1/Logvol00. /dev/VolGroup-1/LogVol00. The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then

Hi there, For years I've been using the ext3 file system without to think that it can ever gets broken so bad. This was until last week when a box that I have running Linux from a SanDisk CF went down. Since then I am struggling with this CF trying to understand what is happening. The CF is SanDisk ultra II 1GB. On this I have 4 partitions all of them with ext3: boot / swap

steps to reproduce: ./run guestfish -N disk:1536M <<EOF part-init /dev/sda mbr part-add /dev/sda p 1 1048577 part-add /dev/sda p 1048578 2097154 part-add /dev/sda p 2097155 -1 mkfs ext2 /dev/sda1 mkfs ext2 /dev/sda2 mkfs ext2 /dev/sda3 EOF qemu-img create -f raw test2.img 1520M ./run virt-resize --format raw --output-format raw --resize /dev/sda1=-2M --resize /dev/sda2=-8M --shrink

On 09/20/2014 12:07 AM, Andreas Dilger wrote: > On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008@gmail.com> wrote: >> I am reporting this on the advice of the Fedora Users Mailing List Member. >> >> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. >> >> I am reporting this per

Hi, somehow after a power failure i can't mount my ext3 partition :( mount /dev/hdd2 /mnt/gentoo/ mount: you must specify the filesystem type fdisk /dev/hdd The number of cylinders for this disk is set to 484521. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2)

On Wed, Feb 18, 2015 at 10:07:20AM -0500, Leonard Basuino wrote: > > ><rescue> e2fsck -n /dev/sda1 > e2fsck 1.42.9 (28-Dec-2013) > The filesystem size (according to the superblock) is 104388 blocks > The physical size of the device is 103408 blocks > Either the superblock or the partition table is likely to be corrupt! > Abort? no > > /boot contains a file

yup runned it. probably something wrong with my initrd filesystem. can you send me a directory listing of your initrd? and probably a sample linuxrc. if worse comes to worse, i'll probably load my usb and scsi modules in the initrd. i'm probably doing it all wrong. i'm trying to imitate the slackware10usb way of booting up. every driver built in the kernel, patch on the mounting root