It does not appear to be in a LVM. Mount just shows /dev/md0 on /home type ext3 (rw) the fstab shows the same thing. If I try to run e2fsck -cc or e2fsck -f I receive the same error message. On Mon, Oct 13, 2008 at 3:31 PM, Andrey Meganov <a.meganov@xxxxxxxxx> wrote: > Raid and lvm devices dont needspecific services to run, just the device > mapper drivers, which are loaded in the maintenance mode. > > BR, > Andrey > > Sent from my iPhone as I am away from office > > > On 13.10.2008, at 18:40, "Jason Brown" <ninjazjb@xxxxxxxxx> wrote: > > Ok, didn't think about that sorry. >> >> On Mon, Oct 13, 2008 at 11:01 AM, Chet Nichols III >> <chet.nichols@xxxxxxxxx>wrote: >> >> I know services dont run in maintenance mode, and that's why I'm asking. >>> My >>> thought was, without the md driver loaded, the OS isn't going to be able >>> to >>> understand how to work with /dev/md0, so you may need to load the driver >>> first before fsck will be able to read the device. >>> >>> On Mon, Oct 13, 2008 at 10:46 AM, Jason Brown <ninjazjb@xxxxxxxxx> >>> wrote: >>> >>> I believe its LVM over RAID, but I will have to look and get back with >>>> >>> you. >>> >>>> When I created the RAID array, I assigned all the disks the software >>>> RAID >>>> and then created the RAID 5 during the installation. I did not go >>>> >>> through >>> >>>> and split the partitions afterwards. >>>> >>>> When I run fsck I get this error... >>>> >>>> fsck.ext3: Invalid argument while trying to open /dev/md0 >>>> /dev/md0: >>>> 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 the superblock >>>> is corrupt, and you might try running e2fsck with an alternative >>>> superblock: >>>> e2fsck -b 8193 <device> >>>> >>>> I then try e2fsck -b 8193 /dev/md0 and get the same error message. >>>> >>>> >>>> >>>> On Mon, Oct 13, 2008 at 10:38 AM, Jason Brown <ninjazjb@xxxxxxxxx> >>>> >>> wrote: >>> >>>> >>>> >>>>> I don't use software RAID, but I would probably want to do this in >>>>>> >>>>> rescue >>>> >>>>> mode off of disc 1. What RAID level are you using? >>>>> 5. >>>>> >>>>> >>>>> I know this is a silly question, but is the md driver loaded and are >>>>>> >>>>> the >>> >>>> md >>>>> services running? >>>>> >>>>> Services are not loaded when in maintenance mode. The server does not >>>>> >>>> even >>>> >>>>> mount the file systems because you cannot run FSCK on a mounted device. >>>>> >>>>> >>>>> >>>>> On Mon, Oct 13, 2008 at 9:39 AM, Chet Nichols III < >>>>> >>>> chet.nichols@xxxxxxxxx>wrote: >>>> >>>>> >>>>> I know this is a silly question, but is the md driver loaded and are >>>>>> >>>>> the >>> >>>> md >>>>>> services running? >>>>>> Chet >>>>>> >>>>>> On Mon, Oct 13, 2008 at 9:15 AM, Barry Brimer <lists@xxxxxxxxxx> >>>>>> >>>>> wrote: >>> >>>> >>>>>> I don't use software RAID, but I would probably want to do this in >>>>>>> >>>>>> rescue >>>>>> >>>>>>> mode off of disc 1. What RAID level are you using? >>>>>>> >>>>>>> >>>>>>> On Mon, 13 Oct 2008, Jason Brown wrote: >>>>>>> >>>>>>> When I tried booting it into single user mode the server would >>>>>>> >>>>>> still >>> >>>> go >>>> >>>>> to >>>>>> >>>>>>> maintenance mode. I was able to get at it another way by passing >>>>>>>> "init=/bin/bash" which got me to a command prompt. Then remounted >>>>>>>> >>>>>>> the >>>> >>>>> drive >>>>>>>> with rw since it was in ro mode, and then changed the password. >>>>>>>> >>>>>>> Now >>> >>>> I >>>> >>>>> have >>>>>>>> it in maintenance mode again, I just need to figure out how to do >>>>>>>> >>>>>>> an >>> >>>> fsck >>>>>> >>>>>>> on >>>>>>>> a raid system. When I try fsck /dev/md0 I got a bad super block >>>>>>>> >>>>>>> error >>>> >>>>> and >>>>>> >>>>>>> to run e2fsck -b 8192 which gives me the same error message. >>>>>>>> Any ideas would be appreciated. >>>>>>>> Thanks. >>>>>>>> >>>>>>>> On Sun, Oct 12, 2008 at 10:57 PM, Barry Brimer <lists@xxxxxxxxxx> >>>>>>>> >>>>>>> wrote: >>>>>> >>>>>>> >>>>>>>> My file server locked up and I had to reboot it, when it came up >>>>>>>> >>>>>>> its >>> >>>> stuck >>>>>>>>> >>>>>>>>> in the FSCK maintenance. Is there a way that I can run this >>>>>>>>>> >>>>>>>>> without >>>> >>>>> a >>>>>> >>>>>>> root >>>>>>>>>> password or reset the password? The file system is an ext3 in a >>>>>>>>>> >>>>>>>>> raid >>>> >>>>> 5 >>>>>> >>>>>>> configuration. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I would be very cautious about interrupting an fsck. If you >>>>>>>>> >>>>>>>> reboot >>> >>>> your >>>>>> >>>>>>> machine and press a key to bring up the grub menu, then type 'e' >>>>>>>>> >>>>>>>> to >>> >>>> edit >>>>>> >>>>>>> that kernel entry, move to the kernel line, hit 'a' to append .. >>>>>>>>> >>>>>>>> place >>>> >>>>> an >>>>>> >>>>>>> 's' at the end of the line and hit enter and then 'b' to boot you >>>>>>>>> >>>>>>>> will >>>> >>>>> boot >>>>>>>>> without the root password into single user mode. >>>>>>>>> >>>>>>>>> Barry >>>>>>>>> >>>>>>>>> -- >>>>>>>>> redhat-list mailing list >>>>>>>>> unsubscribe mailto:redhat-list-request@xxxxxxxxxx >>>>>>>>> >>>>>>>> ?subject=unsubscribe >>>> >>>>> https://www.redhat.com/mailman/listinfo/redhat-list >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>> redhat-list mailing list >>>>>>>> unsubscribe mailto:redhat-list-request@xxxxxxxxxx >>>>>>>> >>>>>>> ?subject=unsubscribe >>>> >>>>> https://www.redhat.com/mailman/listinfo/redhat-list >>>>>>>> >>>>>>>> !DSPAM:48f32bb0112171984720347! >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> redhat-list mailing list >>>>>>> unsubscribe mailto:redhat-list-request@xxxxxxxxxx >>>>>>> >>>>>> ?subject=unsubscribe >>> >>>> https://www.redhat.com/mailman/listinfo/redhat-list >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ---------------------------------------- >>>>>> chet nichols III >>>>>> chet.nichols@xxxxxxxxx >>>>>> aim: chet / twitter: chet >>>>>> http://chetnichols.org >>>>>> ---------------------------------------- >>>>>> -- >>>>>> redhat-list mailing list >>>>>> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >>>>>> https://www.redhat.com/mailman/listinfo/redhat-list >>>>>> >>>>>> >>>>> >>>>> -- >>>> redhat-list mailing list >>>> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >>>> https://www.redhat.com/mailman/listinfo/redhat-list >>>> >>>> >>> >>> >>> -- >>> ---------------------------------------- >>> chet nichols III >>> chet.nichols@xxxxxxxxx >>> aim: chet / twitter: chet >>> http://chetnichols.org >>> ---------------------------------------- >>> -- >>> redhat-list mailing list >>> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >>> https://www.redhat.com/mailman/listinfo/redhat-list >>> >>> -- >> redhat-list mailing list >> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >> https://www.redhat.com/mailman/listinfo/redhat-list >> > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
