[PC-BSD Testing] ad0sx vs ad0px ???
doverosx at gmail.com
Mon Mar 22 13:28:32 PDT 2010
Right, I remember USB devices getting new naming schemes. Is this related?
On Mon, Mar 22, 2010 at 3:06 PM, Walt Pawley <walt at wump.org> wrote:
> At 11:04 AM -0400 3/22/10, Kris Moore wrote:
> >On 03/21/2010 13:38, Walt Pawley wrote:
> >>>> (much replicated verbiage removed)
> >> I have a suspicion that it's related to recent fdisk behavior.
> >> During the drive setup, the installer dd's a bunch of zeros
> >> over the partition map area - but only the primary partition
> >> map. If the drive had a GPT partition map already, the
> >> secondary partition map would still be there. It's presence
> >> might be bollixing process.
> >> FWIW: I've switched gears, reinstalled PC-BSD 7 and am on my
> >> way to getting back to work I need to get done. But I did set
> >> up a USB drive to work on this on the side if anyone cares to
> >> kibitz.
> >This does indeed sound like some weird GPT partition is failing to get
> >removed properly. Can you get the output of "gpart show" on that system?
> That specific data is:
> => 34 60036413 da0 GPT (29G)
> 34 128 1 freebsd-boot (64K)
> 162 8388608 2 freebsd-ufs (4.0G)
> 8388770 4164304 3 freebsd-swap (2.0G)
> 12553074 8388608 4 freebsd-ufs (4.0G)
> 20941682 39094765 5 freebsd-ufs (19G)
> which looks pretty much like I'd expect it to look. I booted
> the PC-BSD 8 x86 DVD into its "live" mode and used the install
> desktop icon at the upper left of the screen to run the
> installer. I chose to let virtually everything default. The
> resultant /dev contents for the layout listed above were:
> crw-r----- 1 root operator 0, 108 Mar 22 11:20 /dev/da0
> crw-r----- 1 root operator 0, 123 Mar 22 11:20 /dev/da0p1
> crw-r----- 1 root operator 0, 127 Mar 22 11:20 /dev/da0p2
> crw-r----- 1 root operator 0, 128 Mar 22 11:20 /dev/da0p3
> crw-r----- 1 root operator 0, 129 Mar 22 11:20 /dev/da0p4
> crw-r----- 1 root operator 0, 130 Mar 22 11:20 /dev/da0p5
> After the failure, the contents of
> /tmp/.pc-sysinstall.log/pc-sysinstall.log were:
> Running: find-update-parts
> kern.geom.debugflags: 0 -> 16
> Cleaning up da0
> Running: dd if=/dev/zero of=/dev/da0 count=2048
> 2048+0 records in
> 2048+0 records out
> 1048576 bytes transferred in 1.031584 secs (1016472 bytes/sec)
> Running fdisk on da0
> Running: fdisk -I /dev/da0
> fdisk: invalid fdisk partition table found
> fdisk: Class not found
> ******* Working on device /dev/da0 *******
> Stamping boot sector on da0
> Running: gpart bootcode -b /boot/boot0 da0
> da0 has bootcode
> ERROR: The slice da0s1 doesn't exist! FDISK Failure
> Running: umount /cdmnt-install
> umount: /cdmnt-install: statfs: No such file or directory
> umount: /cdmnt-install: unknown file system
> It looks as though it partitions the drive reasonably and then
> expects to find things like "da0sx" instead of "da0px."
> NOTE: this is not using the drive I started with, which still
> mounted internally and now running PC-BSD 7. It failed the same
> way when trying to install 8.
> Walter M. Pawley <walt at wump.org>
> Wump Research & Company
> 676 River Bend Road, Roseburg, OR 97471
> Testing mailing list
> Testing at lists.pcbsd.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Testing