Search results for query: *

It is not ID 6, it is ID 0, I had the client verify it. It was only ID 6 when I had both scsi drives connected so I could ghost the old drive. Sorry about that confusion.

Ok I DONT want to reinstall. I want to ghost/duplicate the old drive onto the new drive, and get SCO Unix to work on the new drive (which it does not, Error 19). The reason I want to format the new drive first is because it hasnt been formatted, so only the first few gigs which norton ghost...

Also according to the drive specs, if no jumpers are installed, it should default to ID 0. So I think I only saw ID 6 when I had the two drives installed and I was doing the ghost. Afterwards when I only had the new drive hooked up it SHOULD have been ID 0.

Ok the old and new drive, neither has any jumpers installed, so I thought it was normal for the new drive on its own to get whatever ID the scsi controller assigned to it. Why it wouldnt assign it ID 0 is beyond me since it is the only SCSI device in the system. Assuming I dont want to short...

Ok its on ID 6. Do I have to change it on the drive with jumpers or will the motherboard have an onboard scsi bios I can access to change the ID? And once I get this changed (monday), what will I need to do with SCO Unix regarding formatting the drive (if I need to do so), and mounting it properly?

No the SCSI Adapter (onboard the motherboard actually) was not changed. No other hardware was changed other than me adding the new SCSI drive. The old drive is a 9gig, the new one is a 36gig.

I have installed a new SCSI hard drive into a server where its old SCSI is slowly dieing. It is running SCO Unix (what version I dont know, 1997 is the date). Anyhow, I know nothing about unix, I only have some knowledge of linux. Do I need to format/condition the drive first within SCO Unix...