asked on

filesystem r/o after new install solaris 6

I have a spark/IPX system, the internal disk is target 3.
I have an external disk target 2.
When I install Solaris 6 (base level) after the reboot I get messages:

mount /dev/dsk/c0t3d0s0 is not this fstype
drvconfig: /etc/path_to_inst.42: Read-only file system

And of course nothing works since everything is r/o. I will look for later rev of install disk and try to look at fstable after booting cdrom in single user mode and mounting that slice, but I'm not sure either will succeed.

Notes:
1. When I change the disk jumpers to what I think s/b target 0, it is not recognized.
2. The IDPROM battery is dead, I have to reset its contents when I power it on, the first 13 bytes or so (up to checksum), does anything else need to be set?
3. same thing happened when I installed on external disk.
4. I boot with command something like (its not handy now)
boot /sbus?/esp@0,800000/???2,0:c

irisex

This line:
mount /dev/dsk/c0t3d0s0 is not this fstype
shows that the system expected a different filesystem type.
Maybe:
1. The filesystem is not formatted properly. Search for a command like mkfs
2. The device is wrong /dev/dsk/c0t3d0s0. Try running mknod.
3. The filesystem specified in /etc/fstab does not match the filesystem created.
I look forward your feedback!
JM

SqrFolkDnc

ASKER

I can boot cdrom -s and do fsck (clean) or mount it r/w. This is the first reboot after having done a gui install of the O/S. This is the root filesystem, so it should be mounted automatically, but I still tried updating vfstab to say "yes" instead of "no" to mount at boot, that did not help.

chris_calabrese

As a side note.... Why in Heck are you installing Solaris 2.6 rather than Solaris 9 (or at least 8)?!?

SqrFolkDnc

ASKER

IPX is an OLD system (that's why it has a battery-ram instead of eeprom) that doesn't support solaris 8, 9 and I think not 7 either, but did not check. I am installing the 5/98 version of Solaris 6, I will see if that helps. If not, I have ordered some newer hardware.

SqrFolkDnc

ASKER

I figured out my problem. It is indirectly IDPROM related. The first few times I installed solaris, I had not yet found the FAQ on what to do with a failed battery in an IDPROM, so the idprom contents were invalid. Consequently, the install didn't set the environment variable to boot from the disk I installed on (since it wasn't target 0). Therefore, I had to put in the whole string on the boot command to boot from target 2 or 3. What did I use? I used the target supplied by the default for cdrom (target 6) and just changed the number to 2 or 3. Since I did not know the format of those strings, I did not realize that the ":c" at the end (see original question) forced a read-only condition. After I had fixed the IDPROM contents and reinstalled, the environment variable was set correctly, and the system booted, using a string without the ":c", and came up fine.

How can I close this without accepting any of the incorrect answers above?

SqrFolkDnc

ASKER

Bottom Line: Make sure your eeprom/IDPROM is correct before installing Solaris. Here is the FAQ on IDPROMs from Sun BigAdmin:

http://www.sun.com/bigadmin/descAll/nvram.html

ASKER CERTIFIED SOLUTION

SpideyMod

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial