My Viper-150 auto-detects fine; however, the first attempt to read a tape fails after a boot due to an “illegal SCSI command”. What could be the problem?
I assume that the driver is trying to use some SCSI-2 command to set the default density — but after that, the drive is perfectly happy to do the tedious density check and off it goes. I’ve read all three densities on the drive. Once the drive is set up and the driver realizes there is no density command, it just brute forces the drive density and off it goes. 5.4.17 : Why haven’t we changed the defaults in rdump and rrestore to something that makes sense? I was trying to dump a filesystem to a remote tape and ran into an error complaining about being unable to execute /etc/rmt. Of course, if you get this error, this program doesn’t exist. This information comes from ../src/sbin/dump/pathnames.h. The reason we still use /etc/rmt and /dev/rmt8 is because the rdump and rrestore protocol call for those names. This problem usually won’t show up unless the original installation of the system was done before NetBSD 0.9 *AND* the etc.tar.gz distribution was never done. This distribution fixe
Related Questions
- My Viper-150 auto-detects fine; however, the first attempt to read a tape fails after a boot due to an "illegal SCSI command". What could be the problem?
- If the installation fails, was there a prior installation attempt? Was the MS$FG8 folder removed before attempting to install again?
- My Electric Cart runs fine on level ground, but seems to lose power on inclines. What is the Problem?
