A client has an SCO OpenServer Server 6.0, that is running on an HP ProLiant Box and they lost the root password.
Its equipped with a Doal-Core Intel Pentium Processor. They don't have any media or emergency disk anymore.
I tried to boot with the CD Rom, then "Tools", then exit to a shell, but I can't mount the HD or the RAID, because the root fs is on a LSI Logic Raid controller MPT SAS1064E.
I found an LSIL driver for SCO OS 5.0.7 that I can load at boot time, but this version does not support this SAS RAID controller card.
Is there a driver for OS Server 5.07 for this LSIL SAS1064E RAID controller?
Or, is there a driver for OS 6.0 or for another version for SAS1064E and where can I find a boot load driver disk?
(Since it is installed and running on that box, there must be a driver somewhere!)
What device will the root filesystem be available, mounted to? (On regular startup it is at /dev/rroot)
To answer your second question as far as I recall the hard disk root filesystem is /dev/root (with one r) BUT if you are mounting the hard disk root filesystem having booted from removable media (DVD/CD or floppy) to a mount point (e.g. /mnt) then it is /dev/hd0root .
Thank you for that tip.
I managed to download the OpenServer 6.0 enterprise server installation media and the MPT driver and install it.
This new installation is bootable from a 3rd hard disk connected to the same LSIL SAS1064E RAID controller, as the old installation.
I can now boot on that new hard disk and log in with root. The new root file system is mounted from /dev/root (I think).
The other two disks are configured as a RAID 1 in the board's configuration, in slot 3 and 4.
What would be the device name /dev/?? that I should mount to see and edit the files from the old installation on that RAID ?
Again, the RAID controller is LSIL SAS1064E . The driver is MPT 8.1.0 .
Do I have to create the device first? command?
Since there is no entry in fstab , what would be the correct mount command?
Phew! It's been a long time since I did this but AFAIR it goes like this for a configuration like you are trying to achieve (boot from add-in disk in order to see data on an old controller).
So you have installed the RAID controller driver???? How did you do that?? What command did you use?
From memory, I think it must be either.......
# custom
or
# scoadmin
or
# mkdev hd <- This one might work in any case.
Now, to build such a configuration you would install SCO O/S on the new disk (which you have done) and then insert the RAID controller (okay it's already in there). You would then need to:
Run one of the above commands to add the RAID controller driver to the kernel.
Relink the kernel, say 'Y' to rebuild the boot environment, and reboot.
Run the same command AGAIN to add the disk(s) attached to the RAID controller into the kernel configuration. This will ask for stuff like bus# and unit# (like you would for a SCSI controller - unit# being SCSI ID, etc).
Relink the kernel AGAIN, say 'Y' to rebuild the boot environment AGAIN, and reboot AGAIN.
Now the device node (/dev/<whatever> should be there and the mount command is no different to any other disk.
If you configure the disk(s) wrongly you can run the command yet again to unconfigure, relink, and reboot. Then do it correctly.
I hope that helps. Perhaps you have installed the RAID driver, stopped there and not configured any disk(s)??????
As I said, this is all from memory. Another member, expert at SCO (jgt) might chip in and confirm whether I'm right or wrong.
OSR6 has automatic device configuration. It should have found the second disk by itself . Did you run the bios raid configurator and change the raid1 pair to be system drive 1 instead of 0.
Yes, I now have installed a second SCO 6 instance on a 3rd hard disk in the same system and the same controller. I can now boot on that new instance and have root acceess there.
It runs in an intel Compaq box with an LSI Logic Corp MPT SAS RAID board SAS1064E-IR.
There are 3 disks.
In slot 4 is an ATA SATA disk that I boot from.
In slot 1 and 2 are SAS drives. They are configured to be in a RAID configuration.
SLOT ID LUN Product
4 0 0 ATA (this is the new boot root disk)
4 1 0 LSILOGIC Volume (this is the RAID)
The new root device is /dev/root which is the ATA drive.
The LSILOGIC Volume is the old RAID volume that also contains an SCO 6 installation.
Now I need to get access to that old installation, but I can't seem to find the correct /dev/?? to mount.
Which one would be the correct device(s) for the LSILOGIC Volume?
If it is not there, how do I create it? mkdev...?.
And how do I mount it? Currently �mount /dev/sdxx /mnt/test� throws errors about not being a DOS drive or not being a correct device.
sdiconfig-l is
bash-3.00# sdiconfig -l
0:0,112,0: HBA : (mpt,1)LSI Logic 1064E 10414
0,0,0: DISK : ATA WDC WD5000AAKX-61H18
0,1,0: DISK : LSILOGICLogical Volume 3000
1:0,2,0: HBA : (ide,1) Generic IDE/ATAPI
0,0,0: CDROM : PIONEER DVD-RW DVR-118L1.02
bash-3.00#
Make sure you do not format the disk or change any sizes.
In divvy, you have to rename the root partition from hd0root to something else that is not currently used on any hard drive.
Be very careful to not mark this partition as new, as it will be formatted if you do.
Once this is done, you can mount the partition to /oldroot, or some other name.
You must refer to files in the old root file system by their full name, in the case of /etc/shadow , this will be /oldroot/var/opt/SCO/.Unix.6.0.0Ni/etc/shadow.
If you do not, simply referring to /oldroot/etc/shadow , will be linked to /var/opt ... in the booted root file system.