Yes, this is actually the autoboot fsck thats breaking, the one that is
called from /etc/rc (via /etc/rc.d/). I can physically take the box down
and do an offline fsck of it and that works fine, it's just when it's in
multi-user mode thats the problem.
-- Jonathan
Franco Bruno Borghesi wrote:
For fsck to work (to actually correct any problems you may have),
partitions should be umounted first. Are you sure you have umounted
/dev/twedXXXX before running fsck?
2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>:
Hello,
I have an interesting question, I have a Pentium 4 2.4Ghz (No HT
Enabled),
2x80GB SATA Hard Drives in RAID 1. The box boots, works, etc. However,
whenever you try and do an fsck -y, it says:
[EMAIL PROTECTED] (~)% fsck -y
** /dev/twed0s1a (NO WRITE)
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
2821 files, 31805 used, 474682 free (322 frags, 59295 blocks, 0.1%
fragmentation)
** /dev/twed0s1g (NO WRITE)
** Last Mounted on /home
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
82057 files, 557735 used, 12912399 free (2343 frags, 1613757 blocks,
0.0%
fragmentation)
** /dev/twed0s1d (NO WRITE)
** Last Mounted on /tmp
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
30 files, 1787 used, 504700 free (20 frags, 63085 blocks, 0.0%
fragmentation)
** /dev/twed0s1e (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
251160 files, 1318908 used, 13912410 free (73346 frags, 1729883 blocks,
0.5% fragmentation)
** /dev/twed0s1f (NO WRITE)
** Last Mounted on /var
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
4424 files, 63321 used, 7042830 free (2462 frags, 880046 blocks, 0.0%
fragmentation)
The drives are Seagate SATA's (7200RPM) with a 3Ware SATA RAID
Controller
(8006-2LP) using the twe kernel driver. The drives themselves allow data
to be read to/written from them, but fsck will not work (and is hanging
things on boot).
Anyone got any ideas? I looked at www.3ware.com
<http://www.3ware.com> earlier and it says that
the 8006-2LP's support FreeBSD 4.x, but not 5.x - could this be a result
of that, seeing as otherwise the drives/RAID work fine (AFAIK, it could
not be and I'm just not sure how to test it).
TIA,
-- Jonathan
_______________________________________________
freebsd-questions@freebsd.org <mailto:freebsd-questions@freebsd.org>
mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "
[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>"
--
Jonathan M. Slivko - [EMAIL PROTECTED]
"Linux: The Choice for the GNU Generation"
- http://www.linux.org/ -
Don't fear the penguin.
.^.
/V\
/( )\
^^-^^
He's here to help.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
