[101884] in RedHat Linux List
RE: fdisk/partition hassles
daemon@ATHENA.MIT.EDU (Lance Cummings)
Mon Nov 30 08:23:22 1998
From: "Lance Cummings" <lance@tky3.3web.ne.jp>
To: redhat-list@redhat.com
Date: Mon, 30 Nov 1998 22:21:50 +0900
Reply-to: lance@tky3.3web.ne.jp
In-reply-to: <XFMail.981130043817.kcsmart@microlink.net>
Resent-From: redhat-list@redhat.com
On 30 Nov 98, at 4:38, Frank N. Stein wrote:
> On 30-Nov-98 Lance Cummings complained about fdisk/partition hassles: >
> Savvy Listonians, > > I have a 9.1 gb SCIS I'm using as drive 3 . . .
> . . . after the reboot, the partition is changed from
> type Linux > swap to type 'unknown.' While I get the same error message
> creating > a > Linux native partition, the partition appears to be valid
> after a > reboot. > Only swap is changed.
You said: (man, your mail client does some unusual things to text,
including making it impossible for me to show who said what) ;-))
> Make sure it's listed in fstab and is shown as swap, then try mkswap on it
> to see if it works.
Didn't think it was worth the effort to do that, because I couldn't get the
file type to stick. It continued to revert from swap to unknown after
exiting fdisk. Oddly, the same partition re-typed to Linux native would
stick.
But I encountered some strange things will playing around. For starters,
the extended ends at cylinder 997. So I started the partition at 998. But
every primary I created with Linux fdisk at that point ended up not
passing Linux fdisk validation. Partition overlap, which as I suppose you
know is a very serious error. So I nuked the Linux primaries, rebooted
into the Doze and had a lick with it using Partition Magic 4. No
problems, although I gave up on the idea of moving the swap out there
and just moved one of my partitions. But no overlap now reported by
Linux fdisk. My theory: PM created the extended, so it must use some
method that requires it to also create adjacent partitions without an
overlap error. Strange, though, that one.
> As for the error, I get one repeatedly (at boot) on a Seagate I have
> and I've been getting it since it was installed. If it only happens
> when you try making the swap with fdisk, and then afterward on at boot, I
> wouldn't be too worried about it. I'm beginning to think it's related to
> timing at boot and doesn't harm anything otherwise.
I don't understand at all. What error do you get at boot? I don't get any
boot errors at all. And the drive is only about 3 months old. Usually they
fail immediately or go for a long time. I think the drive is fine.
> But, if you get it repeatedly afterward, be concerned about the drive
> going out, even if it's new.
Like I say, PM seemed to make everything happy -- including Linux
fdisk. I'm not too happy that a Windows app apparently does a cleaner
job of partition creation that Linux' own fdisk. But as I say, it may be
because PM created the extended in front of that primary.
Lance
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
