Re: 4.5-STABLE crash and burn
On Wed, 13 Aug 2003 18:40:27 -0700 Kris Kennaway [EMAIL PROTECTED] wrote: On Wed, Aug 13, 2003 at 03:46:37PM -0600, [EMAIL PROTECTED] wrote: I actually just fsck'ed it. Looks like I lost the /sbin directory but it still boots into sysinstall. What to do now? There's not much for it apart from reinstalling the system, restoring from a backup, or trying to replace enough of the missing files from another system (e.g. the 4.5 live filesystem CD) that you can run 'make world' to do a full rebuild. Yep. That has become clear to me over the last few hours. :-) Oh well, thanks for the help! -- Anthony Chavez http://www.anthonychavez.org/ mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED] #secure method=pgpmime mode=sign ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
4.5-STABLE crash and burn
Friends: I've got a serious situation here. I've got a 4.5-STABLE machine that boots with the following messages: Mounting root from ufs:/dev/ar0s1a WARNING: / was not properly dismounted exec /sbin/init: error 20 exec /sbin/oinit: error 20 exec /sbin/init.bak: error 20 /stand/sysinstall running as init on vty0 As you can see it dumps me into sysinstall, which pops up with Cannot mount /tmp/.doc: read-only filesystem. So I start a holographic shell: # /sbin/mount -fuw / /sbin/mount: not found # ls /sbin ls: /sbin: Bad file descriptor So I start in single-user mode, which just dumps me back into sysinstall again. This is ~not~ good. Pretty much the heart of the business (database, DHCP, DNS and other important services) lives on this machine. So I would very much appreciate any help that anyone could offer, and of course, the sooner the better! -- Anthony Chavez http://www.anthonychavez.org/ mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: 4.5-STABLE crash and burn
On Wed, 13 Aug 2003 23:41:00 +0200 Grzegorz Czaplinski [EMAIL PROTECTED] wrote: #secure method=pgpmime mode=sign On Wed, Aug 13, 2003 at 03:24:21PM -0600, [EMAIL PROTECTED] wrote: Hi! This looks very bad. Have you tried to take the drive off and work on it from another system? Try to run fsck on it, but I would not encourage you to use -y switch. I saw once a similar message on Solaris 8. My friend booted the system from a cd, went to single user mode and run fsck -y. After that, we finished with the whole / (there was only one file system) in /lost+found dir. That was the end. I actually just fsck'ed it. Looks like I lost the /sbin directory but it still boots into sysinstall. What to do now? -- Anthony Chavez http://www.anthonychavez.org/ mailto:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.5-STABLE crash and burn
On Wed, Aug 13, 2003 at 03:24:21PM -0600, [EMAIL PROTECTED] wrote: Friends: I've got a serious situation here. I've got a 4.5-STABLE machine that boots with the following messages: Mounting root from ufs:/dev/ar0s1a WARNING: / was not properly dismounted exec /sbin/init: error 20 exec /sbin/oinit: error 20 exec /sbin/init.bak: error 20 /stand/sysinstall running as init on vty0 As you can see it dumps me into sysinstall, which pops up with Cannot mount /tmp/.doc: read-only filesystem. So I start a holographic shell: # /sbin/mount -fuw / /sbin/mount: not found # ls /sbin ls: /sbin: Bad file descriptor So I start in single-user mode, which just dumps me back into sysinstall again. This is ~not~ good. Pretty much the heart of the business (database, DHCP, DNS and other important services) lives on this machine. So I would very much appreciate any help that anyone could offer, and of course, the sooner the better! Hi! This looks very bad. Have you tried to take the drive off and work on it from another system? Try to run fsck on it, but I would not encourage you to use -y switch. I saw once a similar message on Solaris 8. My friend booted the system from a cd, went to single user mode and run fsck -y. After that, we finished with the whole / (there was only one file system) in /lost+found dir. That was the end. Cheers, gregory -- Grzegorz Czaplinski gregory at prioris.mini.pw.edu.pl The Power to Serve, Right for the Power Users! - http://www.FreeBSD.org/ Fingerprint: EB77 E19D CFA2 5736 810F 847C A70F A275 2489 469F pgp0.pgp Description: PGP signature
