[PC-BSD Testing] BETA1 - 'ufs2 + journaling'
A-Koziol at neiu.edu
Tue Mar 17 11:16:18 PST 2009
>it's exactly the same problem which was with 7.0.2, then was removed in
>alpha1, and now it is in beta1.
>ps: it's my old description of the problem:
>when i use 'UFS + journaling' option during instalation, system was
>working only to the first crash (you can press reset button to simulate
>this); after rebooting, system halt with that message:
>trying to mount root from ufs:/dev/ad0s1a.journal
>WARNING: / was nor properly dismounted
>loading configuration files.
>kernel dumps on /dev/ad0s1b
>entropy harvesting: interrupts ethernet point_to_point kickstart.
>swapon:adding /dev/ad0s1b as swap device
>starting file system checks:
>/dev/ad0s1a.journal: CANNOT READ BLK: 62850944
>/dev/ad0s1a.journal: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
>File system preen filed, trying fsck -y.
>CANNOT READ BLK: 62850944
>THE FALLOWING DISK SECTORS COULD NOT BE READ: 62850944, 62850945,
>/dev/ad0s1a.journal:CANNOT FIGURE OUT FILE SYSTEM PARTITION
>WARNING: R/W mount of / denied. Filesystem is not clean - run fsck
>mount: :Operation not permitted
>Mounting root filesystem rw failed, startup aborted
>ERROR: ABORTING BOOT (sending SIGTERM to parent)!
>DEC: 28 21:12:30 init: /bin/sh on /etc/rc terminated abnorlanally, going
>to single user mode
>Enter full pathname of shell or RETURN for /bin/sh:
>that error occours on many disks (instalation with option 'ufs + soft
>updates' works fine)
I think it's probably been said a lot of times but the Journaling
option shouldn't be used
since I believe it is still experimental in terms of ZFS.
More information about the Testing