Suddenly lots processes exits signal 11 (core dumped)

Devin Teske dteske at vicor.com
Wed Apr 27 23:48:19 UTC 2011


> -----Original Message-----
> From: Chris Hill [mailto:chris at monochrome.org]
> Sent: Wednesday, April 27, 2011 3:36 PM
> To: Devin Teske
> Cc: david.robison at fisglobal.com; freebsd-questions at freebsd.org; 'Teske, Devin'
> Subject: RE: Suddenly lots processes exits signal 11 (core dumped)
> 
> Devin,
> 
> Thanks for the reply. Info inline.
> 
> On Tue, 26 Apr 2011, Devin Teske wrote:
> 
> >> -----Original Message-----
> >> From: Chris Hill [mailto:chris at monochrome.org]
> >> Sent: Tuesday, April 26, 2011 4:51 PM
> >> To: Devin Teske
> >> Cc: david.robison at fisglobal.com; freebsd-questions at freebsd.org;
> >> Teske, Devin
> >> Subject: RE: Suddenly lots processes exits signal 11 (core dumped)
> >>
> >> On Tue, 26 Apr 2011, Devin Teske wrote:
> >>
> >>> Continue on to create a 2nd [visible] partition beyond the primary
> >>> bootable [invisible] partition (allowing you to use the remainder of
> >>> your thumb drive for usable storage)...
> >>>
> >>> 5. Execute: echo "p 2 0x0c * *" | fdisk -f - /dev/da5
> >>> NOTE: again, assuming `da5' is your thumb drive
> >>
> >> tripel# echo "p 2 0x0c * *" | fdisk -f - /dev/da0
> >> ******* Working on device /dev/da0 *******
> >> fdisk: Class not found
> >> tripel#
> >
> > Hmmm. Odd. That's worked for me on FreeBSD-4.11, 6.1, 7.2, and 8.1
> > (both
> > i386 and amd64).
> 
> I "zeroed" the thumb drive as you suggested, but got the same result from
`echo
> "p 2 0x0c * *" | fdisk -f - /dev/da0` as before.
> 
> BTW, that wiping of the thumb drive took over 14 hours! I should have thought
to
> specify a large block size.
> 
> > What's the output of:
> > 	uname -spr
> 
> FreeBSD 8.0-STABLE i386
> 
> > Also, after completing the dd(1) command, what's the output of:
> > 	fdisk -p /dev/da5
> >
> > It should look something like this:
> >
> > 	# /dev/da5
> > 	g c31 h64 s32
> > 	p 1 0x17 1 64259
> > 	a 1
> 
> Here's a sequence of events, after dd'ing the Druid iso:
> 
> tripel# fdisk -p /dev/da0
> # /dev/da0
> g c1945 h255 s63
> p 1 0x17 1 64259
> a 1
> tripel# echo "p 2 0x0c * *" | fdisk -f - /dev/da0
> ******* Working on device /dev/da0 *******
> fdisk: Class not found
> tripel# fdisk -p /dev/da0
> # /dev/da0
> g c1945 h255 s63
> p 1 0x17 1 64259
> a 1
> p 2 0x0c 64260 31182165
> 
> Does this mean the second fdisk succeeded, despite what looked like an error?

It does appear so. That last line is exactly the desired effect (p 2 0x0c 64260
31182165).

So it would seem that the "fdisk: Class not found" output is nothing more than a
warning. Though, I'm with you -- it looks like an error.

I'd be pretty interested to see the output "echo $?" after getting the "Class
not found" message. That is to say, I wonder what the return status of fdisk is
after receiving that message. It may be zero -- indicating success -- in which
case we're reaffirmed that the output is completely spurious and able to be
ignored.
-- 
Devin

> > Something you might also want to try is zapping the disk (wiping all
> > contents) prior to trying again:
> >
> > 	dd if=/dev/zero of=/dev/da5
> 
> --
> Chris Hill               chris at monochrome.org
> **                     [ Busy Expunging </> ]

_____________

The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________


More information about the freebsd-questions mailing list