Add support for MODE SELECT, do not report all pages as unsupported #618
Comments
|
The requested sub-page for page code $15 (EXTENDED), according to the CDB from the log, is $00. |
uweseimet
changed the title
|
@xelalexv IMO support for MODE SELECT is not very likely. RaSCSI would have to store the modified configuration data somewhere, maybe even permanently, but is currently not prepared for storing that kind of device state, not even temporarily. In addition, in your case one would need to know which data sub-page 0 contains, in order at least to store something temporarily (unitl the next restart). In case you have any information about these data, please add them to this ticket. |
|
@xelalexv There is a temporary branch fix_mode_sense_2 now, which does nothing when MODE SELECT is received, i.e. it just reports success instead of an error. Would be interesting to know how your Sun reacts on this. Can you test this branch (with the -b 512 setting), please? |
|
@uweseimet I tested this, but still no boot. I had no time to properly check the RaSCSI logs, but may have found a workaround: Just for the heck of it, I attached the Solaris installer ISO at ID 2 as a hard disk instead of CD-ROM drive, and with that it boots up 😆 At least I get to the main menu of the installer. Whether it will go through I don't know yet, may try out later. |
|
@xelalexv Interesting work-around, indeed :). |
|
I did a few more tests with the workaround described above, and with the RaSCSI on the SPARCstation IPC in general. I can confirm that attaching a CD-ROM ISO as a hard disk in RaSCSI allows you to boot from it without any problems. With this, I could successfully do the following:
I can pretty much do now what I intended to do with RaSCSI and my IPC, that is back up the original installation and then play around with different versions of Solaris using virtual disks. Pretty cool! Should any of this info maybe go into the supported systems section of the wiki? |
|
@xelalexv Would be good, indeed, if you added information to the Wiki. Maybe it's even woth a separate section, because for an item in the compatiblity list there might be too much text. |
|
@uweseimet @rdmark I've validated the workaround also with a SPARCstation IPX. Everything works, so closing this ticket. |
|
I have started to clear enough space to try to get Nextstep installed on a HP715/100 using RaSCSI alone and a SPARCstation 10. The HP is running already with another modern SCSI solution, for that I successfully used Jaz drive with an image of the install media. Don't think the HP is fussed about the identify of the device, more its capabilities. So far lock up once the installer gets to really in to going when it normally would with a CDROM drive it does not like. I don't have enough experience yet with the RaSCSI but is this something you would be interested in me following up. The RaSCSI works fine inside Nextstep as a CDROM emulator. Not tried to boot from an installed OS yet though but so fits in with your notes that it is working. |
|
Hi folks - I'm just wondering if some more information on this method of booting Sun4c machines can be made available here or somewhere, as I haven't been able to make this workaround work using multiple Sun-4c machines (SS2, SSIPX, etc). If I try to mount a Solaris image on SCSI ID 2 as an HD image, I just get "The file loaded does not appear to be executable". I get the same error no matter what version Solaris ISO I use (2.3, 2.4, 2.5.1, etc). The command I've used to mount the image is
I'm using software version 22.05.2, and my RaSCSI hardware is 2.4a. I have almost all the Sun-4c (except the ELC/SLC) so am happy to test anything out if that would help. |
|
I checked my notes, and this was the command I used to mount the installer ISO: So, pretty much like yours, but I didn't use the |
|
Thanks @xelalexv for the quick response. It turns out that part of this was PEBCAK, and part of it is compatibility of this method with newer Solaris versions/ISO images. Your command does indeed work; the correct corresponding Sun boot command for Sun-4c machines with older (v1.x) boot PROMs is: Where The correct Sun boot command for Sun-4c machines with newer (v2.x) boot PROMs is: Where The issue I was having here is that I was forgetting to tell the OBP (Open Boot PROM) to boot from slice 2. This is automatic in OBP when you use SCSI ID 6, but not when you use any other SCSI ID. Using the SPARCstation 1+ (ROM v1.3) - boot using
SPARCstation 2 (ROM v2.9) - boot using
In all cases, SunOS/Solaris complains about the CD image/disk having corrupt label/bad geometry and a label/drive size mismatch, but for the cases where it works, it just continues without any issues. However, for the Solaris 2.6 and 7 images which fail above, there is a workaround:
Also, for simplicity's sake, for Sun-4c machines running v2.x of OBP where there is an automatic alias between Slice 2 of SCSI ID 6 and the alias On RaSCSI: On the v2.x OBP Sun-4c machine: Thank you for your help! |
|
Awesome! Great detailed info! I never went higher than Solaris 2.3 on my IPC & IPX (and probably never will), but great reference should I ever change my mind. |
Info
Describe the issue
I'm attaching a Solaris 2.3 install CD-ROM ISO at id 6. This essentially works, and I can mount the CD from within SunOS. However, when I try booting from the CD, the boot process starts, but after a short while errors out and triggers a reboot from the internal HDD. This was initially caused by a problem with
MODE SENSE(see issue #614). After applying the provided patch for this, a second issue withMODE SELECThas come up, and boot still aborts as before. When this happens, the rascsi logs have this to say:Apparently,
MODE SELECTis currently not supported, so seeing support for this added would be terrific!The text was updated successfully, but these errors were encountered: