On Mon, 5 Jul 2010, Steve Franks wrote:
I just did a 'new huge disk' procedure (aka dump 0aLf - | restore -
for each label). I have a script for automating it, and it usually
seems to work, but not today! Silent failures/corruptions do not make
me comfortable, especially coming from my backup tools (yes, no errors
seen in log).
System seems to work, but it won't shutdown! syncher spits out random
numbers for 10 minutes or more then panics. Should I start over? Why
didn't dump/restore unambiguously copy my working disk to my new one?
I didn't see any expicit errors...
Also, X won't start, complaining about inability to write something
for the keymap into /tmp; probably part of the same problem.
Maybe missing permissions on /tmp? In my case, when I don't bother to
copy /tmp, create a new /tmp on the target, then forget to set
permissions on it.
Wouldn't think that would affect sync, but when you image a system odd
things are possible.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
