On Sun, 9 Oct 2005, Neil Bothwick wrote:
> On Sat, 8 Oct 2005 09:36:36 +0100 (WEST), Jorge Almeida wrote:
>
> > So, what went wrong? And is there any way to force use of the new table,
> > other than rebooting?
>
> hdparm -z /dev/hda forces the kernel to try to re-read the partition
> table, but
On Sat, 8 Oct 2005 09:36:36 +0100 (WEST), Jorge Almeida wrote:
> So, what went wrong? And is there any way to force use of the new table,
> other than rebooting?
hdparm -z /dev/hda forces the kernel to try to re-read the partition
table, but it may still fail.
--
Neil Bothwick
Midget psychic
Robert Crawford wrote:
> I'm virtually certain re-writing the partition table is going to require a
> reboot.
Just umount everything and re-write the partition table. No reboot needed. I
did it hundred of times.
>
> BTW, over the years I've had several drives with the "over 1024" cylinder
> mess
Sorry to answer myself, but it may be usefull for others...
Knoppix uses any swap partition it finds. Since /dev/hda2 was swap
(which doesn't show in mount, of course), the device was busy.
swapoff /UNIONFS/dev/hda2 did release the drive. I partitioned with
sfdisk, but fdisk -l /dev/hda is consist
On Sat, 8 Oct 2005, Robert Crawford wrote:
> I'm virtually certain re-writing the partition table is going to require a
> reboot.
>
Bummer...
> BTW, over the years I've had several drives with the "over 1024" cylinder
> message, and it has never been a problem with many versions of linux,
>
I'm virtually certain re-writing the partition table is going to require a
reboot.
BTW, over the years I've had several drives with the "over 1024" cylinder
message, and it has never been a problem with many versions of linux,
including Gentoo, so that shouldn't be a problem using any modern d
6 matches
Mail list logo
