David O'Brien wrote:
> On Fri, Oct 27, 2000 at 01:10:56PM +0200, Robert Nordier wrote:
> > Just doing the disklabel -w -r followed by the disklabel -B is creating
> > a dangerously dedicated disk,
>
> Actually this is a "fully dedicated" disk. (made to look like a 50MB or
> so disk to M$ produ
On Fri, Oct 27, 2000 at 01:10:56PM +0200, Robert Nordier wrote:
> Just doing the disklabel -w -r followed by the disklabel -B is creating
> a dangerously dedicated disk,
Actually this is a "fully dedicated" disk. (made to look like a 50MB or
so disk to M$ products)
Sysinstall is used to create
Cool idea. I will add a -z option to the disklabel code and submit it to the
author if thats OK with everyone else?
--
Jamie Heckford
Chief Network Engineer
Psi-Domain - Innovative Linux Solutions. Ask Us How.
===
email: [EMAIL PROTECTED]
web: http://www
:Danny Braniss ([EMAIL PROTECTED]) wrote:
:> In message <[EMAIL PROTECTED]>you write:
:> }This is really weird. I have two valinux rackmount boxes, duel cpu's.
:> }
:> }I was testing the PXE stuff and booting one of the boxes regularly.
:> }All of a sudden every time I reboot I get:
Matt Dillon wrote:
>
> :
> :> Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
> :
> :If you added "auto" after the "disklabel -B", that may be your problem.
> :
> :--
> :Robert Nordier
>
> type-o. No auto for the -B still blows up the dos partition
> table.
:
:> Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
:
:If you added "auto" after the "disklabel -B", that may be your problem.
:
:--
:Robert Nordier
type-o. No auto for the -B still blows up the dos partition
table.
-Ma
Matt Dillon wrote:
> Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
If you added "auto" after the "disklabel -B", that may be your problem.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
On Fri, Oct 27, 2000 at 12:46:05AM -0700, Matt Dillon wrote:
> This is really weird. I have two valinux rackmount boxes, duel cpu's.
>
> I was testing the PXE stuff and booting one of the boxes regularly.
> All of a sudden every time I reboot I get:
>
> ...
> BIOS drive A: is disk
Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
00f0 66 8b 46 08 52 66 0f b6 d9 66 31 d2 66 f7 f3 88 |f.F.Rf...f1.f...|
0100 eb 88 d5 43 30 d2 66 f7 f3 88 d7 5a 66 3d ff 03 |...C0.fZf=..|
0110 00 00 fb 77 44 86 c4 c0 c8 02 08 e8 40 91 88 fe |...wD
:>
:> :I'm just curious. How many disks are in this box? We saw something
:> :similar here at work and it turned out that there were multiple disklabels
:> :on the other disks and for somereason it was confusing the loader.
:> :We dd'd the bad sections off and everything worked.
:
:Are you sure
> I was testing the PXE stuff and booting one of the boxes regularly.
> All of a sudden every time I reboot I get:
>
> ...
> BIOS drive A: is disk0
>
> int= err= efl=00030246 eip=1d29
> eax= ebs=0390 ecx= edx=
> esi=8db7 edi=1c09
Mike Smith ([EMAIL PROTECTED]) wrote:
> >
> > :I'm just curious. How many disks are in this box? We saw something
> > :similar here at work and it turned out that there were multiple disklabels
> > :on the other disks and for somereason it was confusing the loader.
> > :We dd'd the bad sections
>
> :I'm just curious. How many disks are in this box? We saw something
> :similar here at work and it turned out that there were multiple disklabels
> :on the other disks and for somereason it was confusing the loader.
> :We dd'd the bad sections off and everything worked.
Are you sure it's c
:I'm just curious. How many disks are in this box? We saw something
:similar here at work and it turned out that there were multiple disklabels
:on the other disks and for somereason it was confusing the loader.
:We dd'd the bad sections off and everything worked.
:
:paul
I've got one IDE
14 matches
Mail list logo
