Date: Fri, 30 Mar 2001 13:09:49 -0800 From: Crist Clark <cjclark@alum.mit.edu> To: Jon Molin <jon.molin@resfeber.se> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Adding a new drive Message-ID: <3AC4F61D.AA89E26F@alum.mit.edu> References: <200103290938.f2T9c1l00499@bluebox.naken.cc> <3AC347D6.1ED5F0A2@resfeber.se> <20010329165129.A60101@pcwin002.win.tue.nl> <3AC34FC7.F53209CC@resfeber.se> <3AC386CA.157C141B@alum.mit.edu> <3AC4301F.3AD7B9D0@resfeber.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Jon Molin wrote: > > > > > Here is what you need to do: > > > > 1) Write a valid slice (PC partition) table. Make sure it is a valid > > table, i.e. you don't get that error above. > > I guess that writing a valid slice is my problem, have you got any tips on how > to create a valid table? > Here's what i've tried (all taken from > http://www.freebsd.org/handbook/disks-adding.html): > > # dd if=/dev/zero of=/dev/ad3 bs=1k count=1 > 1+0 records in > 1+0 records out > 1024 bytes transferred in 0.001281 secs (799436 bytes/sec) > jmo# fdisk -BI ad3 > ******* Working on device /dev/ad3 ******* > fdisk: invalid fdisk partition table found > # That should do it. After you zeroed the label in the first step, fdisk(8) generates that error as it tries to read the table before doing the write. But it should be doing the write. After you do the 'fdisk -BI ad3', what do you see if you do another 'fdisk ad3'? You should be able to reboot at that point and then continue with disklabeling. I just tested the procedure using a afd(4) drive. It worked (except you do not need the reboot for removable media, last I knew you still did for ad(4)). -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AC4F61D.AA89E26F>