Titanium wows
Philip May (566) 7 posts |
Hi |
Chris Hall (132) 3559 posts |
It also will not read USB sticks unless they are formatted for RiscOs error Disc not understood has it been formatted. This is a consequence of fat32fs not being loaded during the boot process, i.e. either an error aborting the boot process part way through or the HardDisc4 not being visible at boot time. So it is not a separate error. One possibility is your CMOS settings – make sure that your boot drive (:4 or :5) corresponds to the drive number set in CMOS. |
Philip May (566) 7 posts |
I have just loaded Reporter and found a line in the report SCSI:Dismount8 following line Disc Drive not found. |
David J. Ruck (33) 1636 posts |
Sounds like several different issues, the most concerning of which are the disc reporting not understood. It’s worth doing a verify on them, press F12 (not control+F12) and do a verify 4 and *verify 5. Look out of any errors or question marks which means retries. Another issue seem to be the keyboard and mouse, which sound a bit dodgy, have you tried different ones? I think Chris is right on the USB drives.
I dont think that is the cause of any of your problems. Reporter can show up stuff in the boot sequence that looks wrong but doesn’t cause any problems. You really need to become familiar with its output before you get any issues, to be able to see what is actually wrong. |
Philip May (566) 7 posts |
Pressed F12 verify 4 and 5 both drives then ran Discknght,both drives have no errors. The key board is on a USB adapter and the mouse is wireless. It will now read USB flash drives as well. The adapter I have been using for about 9 months with no trouble. |
David J. Ruck (33) 1636 posts |
Please remember DiscKnight only checks a small part of the disc which contains filing system information. Using the Verify command reads every part of the disc, and can show up issues with damaged sectors (on spinning rust), but also indicate if the disc system is unreliable if unproduceable faults are reported. Although some disc not understood failure only occur at boot up due to hardware initialization issues, when the disc is recognised no further problems are observed. |
Colin Ferris (399) 1818 posts |
Is there anyway around Solid HD not being able to be read :-( |
David Pitt (3386) 1248 posts |
The Titanium can be booted from USB SCSI or SDFS. I have, in the past, had Titanium woes that sound similar. With OS5.24, and the earlier part of OS5.27, it was possible for the Titanium not to have found one of its SSDs on start up. IIRC an update to the SATADriver module fixed that. I now run with OS5.28 flashed with OS5.29 dev builds softloaded. That all works just fine. Also in the past I have had USB devices that could totally stop the boot at a very unhelpful black screen. I have not seen this recently so either it got fixed, or I got lucky or I have lost the offending device. Diagnostics to see what is, and what is not, present :- *SATAdevices Ctl Prt PMP Type Description Capacity 0 0 0 ATA Crucial_CT240M500SSD1 224 Gbytes 0 0 1 ATA SanDisk SD8SBAT256G1122 238 Gbytes 0 0 2 ATA SAMSUNG SSD 830 Series 119 Gbytes 0 0 3 ATAPI TSSTcorp CDDVDW SN-208FB 0 0 15 Multiplier * *USBDevices No. Bus Dev Class Description 1 1 0 9/ 0 Synopsys XHCI root hub 2 1 1 9/ 0 SMSC USB 2.0 4-Port Hub 3 1 2 9/ 0 Genesys Logic USB2.0 Hub 4 1 3 0/ 0 SanDisk Ultra 5 2 0 9/ 0 Synopsys XHCI root hub 6 2 1 9/ 0 SMSC USB 2.0 4-Port Hub 7 2 2 0/ 0 SMI Corporation USB DISK 8 2 3 0/ 0 SanDisk Cruzer Glide * *SDIOdevices Bus Slt RCA Fun Description Capacity Vendor Product Rev Date 0 0 E624 0 SDXC card 119 Gbytes SanDisk SL128 8.0 2016-03 * |