On Tue, 2003-06-17 at 01:14, Linux Tard wrote:
> Regis
>
> did you ever try to specify a backup superblock? That
> might have solved it for you. This would have been
> the '-b' option.
>
> lt
>
>
Yup lt, sure did. Even went through archives to find different backup
superblocks. Like I sa
Regis
did you ever try to specify a backup superblock? That
might have solved it for you. This would have been
the '-b' option.
lt
>
> Perhaps so Cameron, but I spent a good deal of time
> Saturday running
> various combinations of fsck, and e2fsck with
> various options,
> (including the
On Mon, 2003-06-16 at 18:25, Cameron Simpson wrote:
> On 12:29 16 Jun 2003, rm <[EMAIL PROTECTED]> wrote:
> | Just to complete this thread. I solved this problem in a much simpler
> | way. After some additional searching on Googly Groups, I tried running
> | fsck -A /dev/hda2 and answered yes to
On 12:29 16 Jun 2003, rm <[EMAIL PROTECTED]> wrote:
| Just to complete this thread. I solved this problem in a much simpler
| way. After some additional searching on Googly Groups, I tried running
| fsck -A /dev/hda2 and answered yes to all the questions. When I exited
| and rebooted, it started
>> Thanks again for your help, any other suggestions?
>>
>> regis
> Try changing in your fstab this lines:
> LABEL=/ / ex2 defaults1 1
> with
> /dev/hda2 / ex2 defaults1 1
> and
> LABEL=/boot /boot ext2def
On Saturday 14 June 2003 23:49, rm wrote:
> Thanks again for your help, any other suggestions?
>
> regis
Try changing in your fstab this lines:
LABEL=/ / ex2 defaults1 1
with
/dev/hda2 / ex2 defaults1 1
and
LABEL=/boot
On Sat, 2003-06-14 at 15:58, achillemiele wrote:
> On Saturday 14 June 2003 22:44, rm wrote:
>
> > This could be a problem. The complete line when I do cat /etc/fstab
> >
> > dev/hda5swapswapdefaults0 0
> >
> > does this mean I'm still fscking with the wrong device?
> >
> > T
On Sat, 14 Jun 2003, achillemiele wrote:
> On Saturday 14 June 2003 22:44, rm wrote:
>
> > This could be a problem. The complete line when I do cat /etc/fstab
> >
> > dev/hda5swapswapdefaults0 0
> >
> > does this mean I'm still fscking with the wrong device?
> >
> > The compl
On Saturday 14 June 2003 22:44, rm wrote:
> This could be a problem. The complete line when I do cat /etc/fstab
>
> dev/hda5 swapswapdefaults0 0
>
> does this mean I'm still fscking with the wrong device?
>
> The complete output looks like this:
>
> LABEL=/ /
On Saturday 14 June 2003 21:24, rm wrote:
> Any ideas on how to correct the corrupt superblock, or otherwise
correct
> this?
>
> thanks in advance,
>
> regis
What's your complete recorf i /etc/fstab?
/dev/hda5 ???
Is it a ext2 or ext3 filesystem?
Achille
Thanks again,
This
On Saturday 14 June 2003 21:24, rm wrote:
> Any ideas on how to correct the corrupt superblock, or otherwise correct
> this?
>
> thanks in advance,
>
> regis
What's your complete recorf i /etc/fstab?
/dev/hda5 ???
Is it a ext2 or ext3 filesystem?
Achille
--
redhat-list mail
On Sat, 2003-06-14 at 13:31, [EMAIL PROTECTED] wrote:
> On Saturday 14 June 2003 19:46, rm wrote:
> > Thanks for the reply. Obviously I'm not so sharp on picking up which
> > drive is which. I ran e2fsck -f -c /dev/hda5
> > and got the following response:
> >
> > "WARNING!!! Running e2fsck on
On Saturday 14 June 2003 19:46, rm wrote:
> Thanks for the reply. Obviously I'm not so sharp on picking up which
> drive is which. I ran e2fsck -f -c /dev/hda5
> and got the following response:
>
> "WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE
> filesystme damage.
>
> Do y
On Sat, 2003-06-14 at 11:08, regis wrote:
On Sat, 2003-06-14 at 10:51, Hal Burgiss wrote:
> On Sat, Jun 14, 2003 at 10:40:09AM -0500, rm wrote:
> >
> > LABEL=/
> > LABEL=/boot
> > /dev/fd0
> > none
> > none
> > /dev/hda5
> > /dev/cdrom
> >
> > Then I did: fsck -y /dev/fd0
> >
> > and it respond
On Sat, Jun 14, 2003 at 10:40:09AM -0500, rm wrote:
>
> LABEL=/
> LABEL=/boot
> /dev/fd0
> none
> none
> /dev/hda5
> /dev/cdrom
>
> Then I did: fsck -y /dev/fd0
>
> and it responded:
>
> fsck 1.26 (3-Feb-2002)
> Could not determine filesystem type for /dev/fd0
> fsck: fsck.auto: not found
> fs
Last night a storm knocked out power for a couple hours, and shut down
two Redhat 7.1 systems on a small network. One booted up fine, the
other, after reaching 93% "forced check" reported: FAILED
and said to: "RUN fsck MANUALLY"
After checking the archives of several Linux l
16 matches
Mail list logo
