Robert Simmons rsimmo...@gmail.com wrote:
How do I wipe the whole thing in one go so that I can start
afresh?
gpart destroy ad4 ??
Yes, but first you must delete all of the slices/partitions.
Think of it this way: you must go backwards down the path you
just came with a delete for
On Sun, Jun 5, 2011 at 3:35 AM, per...@pluto.rain.com wrote:
Robert Simmons rsimmo...@gmail.com wrote:
How do I wipe the whole thing in one go so that I can start
afresh?
gpart destroy ad4 ??
Yes, but first you must delete all of the slices/partitions.
Think of it this way: you must
On 5/6/11 7:03 AM, Robert Simmons wrote:
On Sunday, June 05, 2011 12:40:22 AM Matthias Apitz wrote:
# gpart create -s mbr ad4 # Init the disk with an MBR
# gpart add -t freebsd ad4# Create a BSD container
# gpart create -s bsd ad4s1 # Init with a
Hi again.
Thanks for the reply.
Re the old disk drives. I have several 10 year or older IDE drives here,
from 2G to 40G in 24/7 use, and (so far!) they are happy. I also have a
few much newer SATA drives that fail to even spin up.
Like anything, there is a Bath Tub curve re hardware failure
well you have 2x disks dont you. Break the mirrors and then you have a free
drive. Setup the pool how you want on this then rsync all your os build over
onto it. Make any zfs root tweaks you want then boot onto the drive.
If all is good then copy across the partition table from the zfs drive
On Sat, 4 Jun 2011, Robert Simmons wrote:
On Sat, Jun 4, 2011 at 10:43 PM, Warren Block wbl...@wonkity.com wrote:
There's a sample in the second half of my disk setup article:
http://www.wonkity.com/~wblock/docs/html/disksetup.html
Looks good. I have a few critiques:
1) Linux and FreeBSD
On 06/05/2011 03:48 AM, per...@pluto.rain.com wrote:
Kaya Samankayasa...@gmail.com wrote:
Did you apply any updates shortly before it started to fail?
No updates! I did however, install unrar through ports.
Intuitively, that seems unlikely to have triggered the problem.
On 06/05/2011 01:29 PM, Dave wrote:
Hi again.
Thanks for the reply.
Re the old disk drives. I have several 10 year or older IDE drives here,
from 2G to 40G in 24/7 use, and (so far!) they are happy. I also have a
few much newer SATA drives that fail to even spin up.
Like anything, there is
per...@pluto.rain.com wrote:
[snip]
Power supplies do fail occasionally, and not always in obvious
ways such as failing to turn on at all. The output voltages may
be a little too high or too low, or they may be correct but with
excessive ripple or electrical noise; or the supply may be just
I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my installed
ports in order and updated and installed/updated kde4-4.6.3 and all its
dependancies. Xorg works ( i can run twm successfully), but trying to start kde
bombs out. It looks like kded is barfing trying to get a a
Mathew,
On Sun, Jun 5, 2011 at 3:53 PM, Matthew Navarre mnava...@cox.net wrote:
I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my
installed ports in order and updated and installed/updated kde4-4.6.3 and all
its dependancies. Xorg works ( i can run twm successfully), but
On Jun 5, 2011, at 3:17 PM, Antonio Olivares wrote:
Mathew,
On Sun, Jun 5, 2011 at 3:53 PM, Matthew Navarre mnava...@cox.net wrote:
I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my
installed ports in order and updated and installed/updated kde4-4.6.3 and
all its
I created a new user with an empty $HOME, added the startkde line to
.xinitrc and had the same problem. I did notice that drkonqi is crashing and
writing out a .core file, so I'll see if gdb can tell me anything.
Thanks,
mnavarre
Read about something called kchildlock :
kchildlock
on an
13 matches
Mail list logo
