Date: Fri, 17 Jul 1998 22:59:01 -0700 (PDT) From: Ian Kallen <ian@gamespot.com> To: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: rc can't fsck Message-ID: <Pine.BSF.3.95q.980717224439.5239B-100000@mail.gamespot.com>
next in thread | raw e-mail | index | archive | help
I migrated a machine that includes a big ass seagate drive from 2.2.5 to
2.2.6 and it won't fsck it at boot time! I can fsck it fine manually but
check out rc croaking on fsck'ing it:
(ahc0:5:0): "SEAGATE ST423451W 0013" type 0 fixed SCSI 2
sd2(ahc0:5:0): Direct-Access 22130MB (45322644 512 byte sectors)
...
cannot alloc 5314561 bytes for typemap
/dev/rsd2s1: CAN'T CHECK FILE SYSTEM.
/dev/rsd2s1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Automatic file system check failed... help!
Enter full pathname of shell or RETURN for /bin/sh:
I can fsck it then (or control-d out of single-user) w/o any complaint. I
modified login.conf like this to give rc the same limits as root:
# Settings used by /etc/rc
#
daemon:\
:coredumpsize=infinity:\
:datasize=infinity:\
:maxproc=infinity:\
:memoryuse=infinity:\
:memorylocked=infinity:\
:openfiles=infinity:\
:stacksize=infinity:\
:tc=default:
but no joy. I can hack up rc to skip fsck'ing it just to make it
rebootable but, damn, I really don't want to do that. So um, what to do
next?
-Ian
--
I play the harmonica. the only way I can play is if I get my car going
really fast, and stick it out the window.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.980717224439.5239B-100000>