On Tuesday 11 November 2003 10:36 am, Vanaclocha Llorenç, Llorenç [INSA] wrote: > I thing yes, if you want a rescue disk you must build another boot floppy. > > A standard boot floppy can help you, also the install cd (with rescue mode) > can help you if your hard disk don't boot, but always it's better if you > change your initrd make a new boot floppy. Since Redhat CD became bootable, I've never actually bothered to create boot floopy, since I thought I can always boot from CD and run linux rescue there, but that's just me :) Ps: could we avoid top post? RDB > Llorens > > -----Mensaje original----- > De: redhat-list-admin@xxxxxxxxxx [mailto:redhat-list-admin@xxxxxxxxxx] En > nombre de martynas@xxxxxxx Enviado el: martes, 11 de noviembre de 2003 > 16:29 > Para: redhat-list@xxxxxxxxxx > Asunto: RE: fsck allways fails after unclean shutdown on redhat 9 - help! > > And I have to build special boot floppy for redhat with ext3 then? Standart > boot floppy from another distribution and ext2 support would not help if > for some reason redhat 9 does not boot form hard disk? > > Martynas > > --- =?iso-8859-1?Q?=22Vanaclocha_Lloren=E7=2C_Lloren=E7_=5BINSA=5D=22?= > > <lvanaclocha@xxxxxxxxxxx> wrote: > > I have 15 machines with ext3 type on root partition. > > > > No problems. Any problem. > > > > I haven't migrate. My systems always have ext3 on root partition. If you > > want migrate this is the solution from RedHat > > > > ######################################################################### > ># The tune2fs program can add a journal to an existing ext2 file system > > without altering the data already on the partition. If the file system is > > already mounted while it is being transitioned, the journal will be > > visible as the file .journal in the root directory of the file system. If > > the file system is not mounted, the journal will be hidden and will not > > appear in the file system at all. > > > > To convert an ext2 file system to ext3, log in as root and type: > > > > /sbin/tune2fs -j /dev/hdbX > > In the above command, replace /dev/hdb with the device name and X with > > the partition number. > > > > After doing this, be certain to change the partition type from ext2 to > > ext3 in /etc/fstab. > > > > If you are transitioning your root file system, you will have to use an > > initrd image (or RAM disk) to boot. To create this, run the mkinitrd > > program. For information on using the mkinitrd command, type man > > mkinitrd. Also make sure your GRUB or LILO configuration loads the > > initrd. > > > > If you fail to make this change, the system will still boot, but the file > > system will be mounted as ext2 instead of ext3. > > ########################################################################### ># > > > Best regards > > > > Llorenç > > > > -----Mensaje original----- > > De: redhat-list-admin@xxxxxxxxxx [mailto:redhat-list-admin@xxxxxxxxxx] En > > nombre de martynas@xxxxxxx > > Enviado el: martes, 11 de noviembre de 2003 15:57 > > Para: redhat-list@xxxxxxxxxx > > Asunto: Re: fsck allways fails after unclean shutdown on redhat 9 - help! > > > > Some, with ext3 type on root partition there is no such problem? Could > > somebody confirm this? Or maybe better, could somebody confirm this, who > > migrated from ext2 to ext3 on root partition and the problem disapeared > > > > regards, > > Martynas > > > > --- Ed Wilts <ewilts@xxxxxxxxxx> wrote: > > > On Tue, Nov 11, 2003 at 03:43:54PM +0200, martynas@xxxxxxx wrote: > > > > yes..the same problem as mine.. I dont want to use ext3 on root > > > > partition > > > > > for > > > > > > > some reasons.. and I use ext3 only on other partitions, so I would > > > > like > > > > to > > > > > > correct this redhat 9 behaviour... it's pain every time to go > > > > somehwere > > > > to > > > > > > check clean FS ( i have systems in serveral places).. maybe it is > > > > worth > > > > to > > > > > > send this as bug? Or maybe somebody knows, how to fix it? > > > > > > I would expect that even if you filed a bug, it's not going to be a > > > high priority for anybody to fix. After all, ext3 is the supported > > > mechanism to prevent this. If you can't run ext3 ("for some reasons" > > > isn't very descriptive), then you may want to file bug/enhancement > > > requests so that you can run ext3. The developers don't have enough > > > time, and they're going to be hitting the bigger issues first. ext2 > > > issues on a dead-end product aren't going to be fixed in a time period > > > that's going to do you any good. > > > > > > -- > > > Ed Wilts, Mounds View, MN, USA > > > mailto:ewilts@xxxxxxxxxx > > > Member #1, Red Hat Community Ambassador Program > > > > > > > > > -- > > > 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 -- Reuben D. Budiardja Department of Physics and Astronomy The University of Tennessee, Knoxville, TN --------------------------------------------------------- "To be a nemesis, you have to actively try to destroy something, don't you? Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." - Linus Torvalds - -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
