RusDyr said:. It's excessive, doesn't neccesary for quick installation and obviusly can be done later. This zfs partitioning way is in almost all howtos. Does anybody think the sense of it? I get Code:. Strangely the first line does not give me error now for this machine. Now I destroyed both ada0 and ada1 successfully. Last time ada1 was not connected properly power cable messup. It does not seem to affect things though.
I am trying to create partitions now. When I tried to do Code:. I am giving up on AMD Got another error with Code:. I started from scratch using the i disk DVD. Still got the same error when I tried to Code:. The errors which happened from p2 to p5 did not seem to affect other things, but now after finishing my network does not work. Yesterday the i 9. It appears the MB's ethernet card is gone while I was installing it.
Put another PCI card in, not working. Another one, still not working. Having bad luck today. It may not display this or other websites correctly.
You should upgrade or use an alternative browser. Thread starter vand Start date Jan 21, I'll show how to install FreeBSD 9. I'll use the following logical layout: Code:.
Reserved 1. Reserved 2. Reserved 3. Reserved 4. Click to expand RusDyr Member Reaction score: 15 Messages: It's excessive, doesn't neccesary for quick installation and obviusly can be done later. This zfs partitioning way is in almost all howtos. Does anybody think the sense of it? I reinstalled the openindiana boot drives and ran the scrub from there--it fixed a few checksum errors but panics still occur when switching back to FreeBSD.
This is compounded by a possibly unrelated issue causing the server to hang on panic instead of rebooting automatically. I disabled debug in sysctl. Rebooting via the shutdown command works so I don't think reboot functionality is otherwise broken. The kernel panics wouldn't be a huge issue if the autoreboot worked it's a remote server.
Anyone have any ideas on the panic or at least how to ensure the server reboots if it occurs -- do I need to disable tracing as well? Thanks, Will M. Please, post more technical information about faulty machine. Especially: zpool version , ram size, zpool size, disk count, disk type etc. Maybe there are some errors in syslog realted to this issue? If so, you could post it too. Sorry, I'll try to be more verbose. Unfortunately, I have switched the faulty server back the the openindiana boot disks so I won't be able to gather debug info easily--I had taken a picture of the trace earlier, but I seem to have lost it.
I forgot to mention in the first post that both servers have kern. It does appear to be related to disk activity scrub will trigger it, and my unison sync scripts manage to do so as well. One thing I did find interesting: if I force a panic manually on 2 kill -6 1 , the automatic reboot works correctly.
0コメント