no valid volume header@SCSI2SD - Printable Version
+- IRIX Network Forums (//forums.irixnet.org)
+-- Forum: SGI/MIPS (//forums.irixnet.org/forum-3.html)
+--- Forum: Beginners' Questions/Tips (//forums.irixnet.org/forum-6.html)
+--- Thread: no valid volume header@SCSI2SD (/thread-2440.html)
+- IRIX Network Forums (//forums.irixnet.org)
+-- Forum: SGI/MIPS (//forums.irixnet.org/forum-3.html)
+--- Forum: Beginners' Questions/Tips (//forums.irixnet.org/forum-6.html)
+--- Thread: no valid volume header@SCSI2SD (/thread-2440.html)
RE: no valid volume header@SCSI2SD - Soy - 08-30-2022
(08-29-2022, 03:25 PM)robespierre Wrote: See this message by GanjaTron, it may be related:
https://forums.irixnet.org/thread-3666-post-26493.html
Hi, thank you for the info.
I use YAMAHA's drive which is one of SGI-friendly drives.
I want to check sequentially in order to avoid confusion;
1) Check with a new SCSI2 cable,
2) If it still makes the error, buy the new CD-ROM drive,
3) Check with the new Drive (standalone)
Anyway, now Dollar/Yen is about to reach 140Y/$, Yahoo! Japan's Auction Site is reasonable for persons who are on out-of-Japan sites, indeed.
Although now SGI machines are not available at the site (no registered), peripherals are there.
RE: no valid volume header@SCSI2SD - Soy - 12-29-2022
Hi, my progress is;
I bought another CD-ROM drive and checked the recognition by Indy. SCISI bus error still occurred, I understand that SCSI controller on the motherboard has a fail something.
Mmm..., I stop repairing, and I will try again next year, buy Indy.
-
Soy
RE: no valid volume header@SCSI2SD - Soy - 02-05-2023
I try to fix the problem, I bought another Indy and check the machine. It also made bus resetting, so I doubt SCSI termination.
I did by previously are;
Bought XL graphics board
Defect on XS graphics board
Defect on mother board
Bought Indy with XL graphics and R4000
Bought in-house EPROM supporting R5000 and replaced
Last Year:
Bus resetting issue
Bought CDROM drive again
Bought SCSI cable
Doubt SCSI controller failure on mother board
Today:
Bought Indy with XS graphics and R4600
Set mother board and XL graphics board
Not boot
Replace SIMMs
Not boot
Replace XL graphics with XS graphics
Boot but bus resetting issue on sash (see picture).
RE: no valid volume header@SCSI2SD - Soy - 02-17-2023
Hi,
I just purchased another Indy, and checked with same condition.
Error is still happen (SCSI bus resetting), so I think that a terminator for the CD-ROM drive and or its setting have some issue.
I will check it with a drive’s manual in internet for the setting up.
(I completely forget)
Best,
Soy
RE: no valid volume header@SCSI2SD - Irinikus - 02-18-2023
I’ve also been met by failure when trying to install a CD- ROM into an Indy, so you’re not alone.
Maybe try fitting a terminator on the external SCSI socket on the back of the machine, as this may be necessary to get things working properly.
In end I discovered how to share my Tezro’s CD-ROM across a network, allowing me to install IRIX on my machines without CD-ROM’s.
You could also maybe try an external CD-ROM if the termination of the external SCSI port doesn’t work.
RE: no valid volume header@SCSI2SD - Soy - 03-05-2023
(02-18-2023, 04:25 AM)Irinikus Wrote: I’ve also been met by failure when trying to install a CD- ROM into an Indy, so you’re not alone.
Maybe try fitting a terminator on the external SCSI socket on the back of the machine, as this may be necessary to get things working properly.
also maybe try an external CD-ROM if the termination of the external SC
Thank you! I replaced motherboard but still I have some issue out side of Indy’s box. I have two CD-ROM drives, Yamaha’s major ones, and both met same an error, see the picture. The drive has terminator switch on backside, I tried to on/off and attach dedicated terminator, these make same error.What do you think?
RE: no valid volume header@SCSI2SD - robespierre - 03-05-2023
The repeated Unit Not Ready messages are the result of the Indy resetting the SCSI bus and then trying to access the drive before it becomes ready (CD-ROM drives take a long time to become ready).
The real issue is the "Command 0x28 Unexpected info phase 49". Command 0x28 is READ (10). So during a READ command, a bus event (phase 49?) happened that was unexpected by the Indy.
Bus phases are a low-level detail of the SCSI protocol and this should not happen. Possible causes: interference by another device on the bus, or a difference in interpretation of which level of SCSI standard is to be used (asynchronous or synchronous, slow or fast, ....) between the Indy and the drive.
Termination or bus length may possibly be the issue. Do you have the Yamaha drive manual, and what does it say the "Termination" switch does? Does it activate an active termination feature of the drive? Is it in fact, wired to the drive at all?
Does the drive have passive termination (SIP resistor pack: attached image) or the sockets where it can be installed?
Is your external terminator a passive or active type?
On the Indy there is only one SCSI bus, used for both internal and external devices. But there are two SCSI ports, an internal port where a ribbon cable may be attached, and an external port. To make this work, the Indy's SCSI controller or "HBA" (host bus adapter) is connected in between the two ports. This is a special arrangement that means that both the last internal device (such as hard disk or Floptical) and the last external device (such as CDROM), and only these must have terminators or internal termination activated. The HBA itself does not provide any termination, as many other computers do.