Date: Tue, 7 Jan 2014 17:27:16 +0700 From: Olivier Nicole <olivier.nicole@cs.ait.ac.th> To: eras mus <erasmu@gmail.com> Cc: Polytropon <freebsd@edvax.de>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>, =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> Subject: Re: Server hang Message-ID: <CA%2Bg%2BBvj_E82bKGsqh86AZU=r7gMMCT1sA-bd6aALRo5W%2BhTgXQ@mail.gmail.com> In-Reply-To: <CALeO_hPMR9uozBBGU0DYxRfL%2BV-YucPKiin70BRhga4r49feig@mail.gmail.com> References: <CALeO_hPMR9uozBBGU0DYxRfL%2BV-YucPKiin70BRhga4r49feig@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> With reference to my previous mail. > The fsck output is in http://pastebin.com/vch0DbAx . And not in the > previous link. fsck should not take hours, unless your file system is terabytes. It would be nice to know what is this inode 5823; you could try a find /usr -inum 5823 Olivier > > On Tue, Jan 7, 2014 at 3:46 PM, eras mus <erasmu@gmail.com> wrote: > >> Dear List, >> >> With your help able to fix rc.conf. Able to start in normal mode. again >> the server is hanging. No connection from LAN and also from server console >> So in single user mode ran fsck. The fsck commands runs fine util it >> comes for /usr. After giving these messsage http://pastebin.com/jujRwp6g It >> is waiting for more than a hour.No other output. Is it normal phenomena? >> Will it take more time. >> >> Please Note: As some one adviced here for memory check. Out of 4 RAMS >> tried removing RAM one by one and checked whether system is hanging. It >> still hangs . >> >> >> >> On Tue, Jan 7, 2014 at 1:25 PM, Polytropon <freebsd@edvax.de> wrote: >> >>> On Tue, 7 Jan 2014 13:05:00 +0530, eras mus wrote: >>> > Dear List, >>> > >>> > I tried editing /etc/rc.conf file in between server hanged . Now the >>> > rc.conf is incomplete. There is a line with incomplete quotes. >>> > So the machine in starting in single user mode . No editor is working . >>> > when /usr is mounter ee editor is there. But The file could not be >>> edited >>> > and saved since it is read only. >>> > >>> > How to overcome this read only mode and edit the file. >>> >>> This indicates a severe error, as you have correctly observed. >>> Step 1 is to make / writeable: >>> >>> # mount -u / >>> >>> which is a "shortcut" for >>> >>> # mount -u -o rw / >>> >>> You will also need to mount partitions like /usr to make your >>> normal editor working (for example /usr/bin/ee): >>> >>> # mount /usr >>> >>> or even >>> >>> # mount -a >>> >>> In case this step is not _possible_, you can still use an editor >>> present on / (typically /rescue/vi): >>> >>> # /rescue/vi /etc/rc.conf >>> >>> Apply the quotes as required and :wq (write file and quit the >>> editor). Then you should be able to let the system reboot normally. >>> >>> >>> -- >>> Polytropon >>> Magdeburg, Germany >>> Happy FreeBSD user since 4.0 >>> Andra moi ennepe, Mousa, ... >>> >> >> > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bg%2BBvj_E82bKGsqh86AZU=r7gMMCT1sA-bd6aALRo5W%2BhTgXQ>