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 all the questions. When I exited > | and rebooted, it started - good as new! > > If you're going to answer yes to all the questions you can say > > fsck -y /dev/hda2 > > and it will answer "yes" for you. (And there's no need to use -A if you're > fscking just one filesystem). > > Cheers, > -- > Cameron Simpson <[EMAIL PROTECTED]> DoD#743
Perhaps so Cameron, but I spent a good deal of time Saturday running various combinations of fsck, and e2fsck with various options, (including the option you suggested) and each returned a "superblock" error. It was only today when using the -A switch that it worked. Doesn't make sense to me, but it worked - so I'm not complaining. thanks just the same, regis -- rm <[EMAIL PROTECTED]> -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
