Running FreeBSD 9.0 BETA1 (AMD64) on a Dell PowerEdge SC430.
I am mostly a Windows guy turned FreeBSD newb, but have had success updating the source, building world, customizing, compiling and installing the kernel (to remove debugger stuff and devices that don't apply to my system), installing world, importing ZFS raidz pool from previous FreeBSD system, installing Samba, Xorg, KDE4, and TightVNC. In fact, I just got everything working the way I wanted, was about to do a portupgrade -a, but thought to take a backup while everything was working so great...
So I started to do a dump of the system slices--backing them up one at a time onto my large ZFS raidz. I only got as far as the root fs, using the following command:
- Code: Select all
#dump -0aLuf /mnt/ZFSstore/more.paths/full-root /
This first attempt was actually working--I saw corresponding hard drive activity on my raidz hard drives enclosure (i.e., the destination drives). But then I stupidly tried to interrupt the process..hitting Ctrl+C repeatedly to try to get it to stop, and when the process did not terminate and the system seemingly froze, I gave up and hard reset the machine.
On reboot, fsck detected errors in the filesystems, and appeared to correct them. I've also since booted to single user mode and ran fsck on all the system partitions. fsck reported that it fixed the errors.
The problem is that each time since that first forced restart, running the dump command has failed. Absolutely no machine activity follows from the command, and the computer becomes largely unresponsive, though strictly speaking it's not "frozen". For example, my Ctrl+C entries appear on the screen, but have no effect--the process does not terminate and I am not returned to the command line and cursor. If I press Alt+F2 I can indeed get to another console, but upon typing "root" at the login prompt the username very sluggishly appears on character at a time, and then that console becomes largely unresponsive as well--the password prompt never appears.
This unresponsiveness does not end prettily--as each time I am obliged to hard reset the machine again, after which fsck reports and repairs more filesystem errors on boot up. This has gone on 4 or 5 times like this with the same result, and now I come here for your assistance.
Any guidance would be appreciated, and please let me know if you require further details. Thanks in advance.