Not sure why it happened in the first place, but the failure to re-establish the journal using tunefs was a result of "su root" and not "su - root"
On 05/28/12 14:34, Gary Aitken wrote: > I mounted a previous system disk, > cleaned everything off it using rm, > then stuck a bunch of files on it. > > Used it for a day or so, > including at least one > shutdown -r > then halted the system to swap a CD. > > Upon reboot, the system refuses to mount the drive: > > mount -o rw -t ufs /dev/ada0p2 /hd1 > Failed to find journal. Use newfs to create one > Failed to start journal: 2 > mount: /dev/ada0p2 : No such file or directory > > Doing > mount -o ro -t ufs /dev/ada0p2 /hd1 > succeeds. > > tunefs -p /hd1 > shows > soft updates enabled > soft update journaling enabled > gjournal disabled > > tunefs -p / > shows the same > > The error looks like it's expecting gjournal to be enabled, > but the tunefs output shows it should not be. > > Any hints? > > Thanks, _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
