By native build I mean installing from RedHat CDs. When I try to build the new machine I build a floppy via the SystemImage software and use it to boot the new machine. And yes it is preventing the retrieved image from being installed on another machine. The SystemImage script tries to use parted against c0d0 and all it can see is disc0 so it aborts. There may be a way around this but it is not obvious from the documentation.
I agree that it may be a driver issue. But I also wondered if this might be the way Debian would present the disk. I have never installed Debian so it I am not aware if there are differences in the presentation name.
-----Original Message-----
From: Ari Jort [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 13, 2003 7:24 PM
To: Berkeley F Bernard
Cc: [EMAIL PROTECTED]
Subject: Re: [Sisuite-users] Not recognizing disk as same device name...
Berkeley,
On Wed, Aug 13, 2003 at 11:35:43AM -0400, Berkeley F Bernard wrote:
> I have a pair of HP/Compaq DL380s. I installed RH8 on the first one from
> CD. I attempted to then image the second one from it. The native
> install sees /dev/cciss/c0d0 while the SystemImager install sees the
> disc as /dev/cciss/disc0. Natively installing on the second presents
> /dev/cciss/c0d0, so I believe it is a SystemImager issue. Why is
> SystemImager presenting the disk as disc0 instead of c0d0?
This discrepancy sounds like an artifact of how devfsd presents devices
on your hardware. Or it could be a slight difference between the cciss
driver on the systemimager install image and the one on the native install.
Btw, when you say "native install", what is that exactly?
You could still successfully install to the disk using that device.
Is this problem preventing a machine build for you? What error
do you get? What method are you using to build your system?
ari
--
Ari Jort
[EMAIL PROTECTED]
