fdisk -> core dumped

fdisk -> core dumped

Post by avia.. » Fri, 09 Feb 2001 06:37:36



I just installed a Western Digital 40GB 7200rpm ata100 hard drive in my
server.  needless to say I'm having alot of fun.  or I was until I
tryed to run fdisk...

--------------------------------------------------------------------

Device contains neither a valid DOS partition table, nor Sun, SGI or
OSF disklab
el
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.

Segmentation fault (core dumped)

--------------------------------------------------------------------

Now, fdisk works on my first hard drive a 6.4G Western Digital.  If
anyone can tell me what I did wrong or what's going wrong?  This is a
linux only system and the drive is fresh from the box (never formated
before)  The system specs are as follows...

P200MMX w/128MB ram
hda 6.4G Western digital
hdb 40G Western digital
hdc 24x cd-rom
hdd 8x cd-rom
Linux Mandrake 7.1

thanks,
  Rob

Sent via Deja.com
http://www.deja.com/

 
 
 

fdisk -> core dumped

Post by Tim Moor » Mon, 12 Feb 2001 10:37:23



> Device contains neither a valid DOS partition table, nor Sun, SGI or
> OSF disklab
> el
> Building a new DOS disklabel. Changes will remain in memory only,
> until you decide to write them. After that, of course, the previous
> content won't be recoverable.

> Segmentation fault (core dumped)

try cfdisk or sfdisk

--
timothymoore
   bigfoot
     com

 
 
 

fdisk -> core dumped

Post by Henrik Carlqvis » Sat, 10 Feb 2001 03:40:41




> Device contains neither a valid DOS partition table, nor Sun, SGI or
> OSF disklabel
> Building a new DOS disklabel. Changes will remain in memory only,
> until you decide to write them. After that, of course, the previous
> content won't be recoverable.

> Segmentation fault (core dumped)


I've heard about someone else with the same problem. His solution was to
run gparted which was able to write a DOS partition disklabel. Then he
was able to use fdisk to create partitions.

This is probably a bug in fdisk which seems to be unable to create new
partition tables on big disks.

regards Henrik
--
spammer strikeback:

 
 
 

1. dump core or not dump core

Howdy,

Some of my programs dump core, others don't. I tried
it on RedHat 6.1 and Mandrake 7.0 with kernels 2.2.14
and 2.2.15. I tried tcsh and bash with coredumpsize
set to 1GB. It seems to be application specific.

Is there any other criteria when suppressing apart from
the type of signal and the size limitation?
The application that doesn't dump core contains signal
handlers for some signals, but not for SEGV or ABRT.

Ruppert

 -----------------------------------------------------------------

 Dept of Elec. & Comp. Engr.    http://alpha.ece.ucsb.edu/~ruppert
 University of California       Phone: (805) 893-7788
 Santa Barbara, CA 93106        Fax:   (805) 893-3262
 -----------------------------------------------------------------

2. Linux: "kernel: UNIX: create: can't allocate buffer"

3. core dumps core dumps everywhere...

4. Driver for Apollo?

5. ioctl() returns no disk geo inf, fdisk core dumps, Future Domain 950

6. What's TRSDOS?

7. Knews & libc 5.4.23 -> core dump ?

8. question about design and data storage

9. KDE 1.1 on sparc station 20 : can't start netscape -> core dumped ?

10. installf -f <pkgname> core dumps on Solaris 7

11. Compiling with gcc 2.95 on Solaris 8 --> core dump

12. Missing shared libraries => core dumps - why ?

13. Linux emulation -> core dumped?