Trying To Access Syquest Syjet 1.5gig SCSI Drive Via Parallel Port
I am trying to access the contents of a Syquest Syjet 1.5gb drive that I have connected to the parallel port. The cable allows for connection to the parallel port as well as a scsi device.
I have upgraded from Ubuntu 8.04 to Ubuntu 14.04 LTS and am trying to access the scsi drive based on this post at ubuntuforums.org: How To Get Your External Syquest Drive Working In Ubuntu
I want to access the drive in order to get files off of the drive then I can retire the syquest drive. I also have some Iomega 100 and 2 gig Jaz drives I would like to do the same things with as well.
I followed the instructions in the above mentioned article and created an executable text file that was saved on the desktop that I tried running from both the desktop and from the terminal with no success.
So my question is: what do I need to do in order to be able to access the scsi drive from the parallel port and copy the files off of it?
When I run the script from the desktop, it runs so fast that I don't know if anything actually happens. When I run the script from the terminal, I get errors as well as some commands running ok I think. The whole script as run from the terminal is posted below:
arthur@arthur-T5082:~$ # Start here...
arthur@arthur-T5082:~$ # modprobe parport # Already maybe loaded
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # modprobe parport_pc # Already maybe loaded
arthur@arthur-T5082:~$ modprobe paride
modprobe: ERROR: could not insert 'paride': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The following 2 steps are not necessary on Breezy...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # mkdir /lib/modules/$(LINUX_VERSION)/misc
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # cp /lib/modules/$(LINUX_VERSION)/kernel/drivers/block/paride/epat.o /lib/modules/2.4.20-20.8/misc/epat.o
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "Inserting the necessary modules..."
Inserting the necessary modules...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ modprobe epat # Sparq Protocol
modprobe: ERROR: could not insert 'epat': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ modprobe pd # Sparq Driver
modprobe: ERROR: could not insert 'pd': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ dmesg | grep paride
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # Look for: "paride: epat registered as protocol 0"
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # modprobe pd drive0=0x378,1 drive1=0x3bc,1 # Example syntax
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # To support such a wide range of devices PARIDE, the parallel port IDE subsystem, is actually structured in three parts.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # There is a base paride module which provides a registry and some common methods for accessing the parallel ports.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The second component is a set of high-level drivers for each of the different type of supported device:
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pd IDE disk
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pcd ATAPI CD-ROM
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pf ATAPI disk
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pt ATAPI tape
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pg ATAPI generic devices
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The pg driver exists mainly to support parallel port ATAPI CD-R and CD-RW devices.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ #
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # Run the commands below from a script
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # ================================================== ==================
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "Running commandsmou..."
Running commandsmou...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ test whoami = 'root' || echo "You must be root to execute the commands."
You must be root to execute the commands.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ cdrecord -scanbus > /dev/null
wodim: No such file or directory.
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! (pidof kerneld || test -f "/proc/sys/kernel/modprobe"); then
echo "Neither kerneld nor kmod are running to automatically load modules".
fi
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ report_no_autoload() {
echo "Ensure the module $1 is loaded automatically next time."
}
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if test ! -f "/proc/scsi/scsi"; then
report_no_autoload scsi_mod && modprobe scsi_mod
fi
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ sg_" /proc/ksyms > /dev/null; then
report_no_autoload sg && modprobe sg
fi
grep: /proc/ksyms: No such file or directory
Ensure the module sg is loaded automatically next time.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ sr_" /proc/ksyms > /dev/null; then
report_no_autoload sr_mod && modprobe sr_mod
fi
grep: /proc/ksyms: No such file or directory
Ensure the module sr_mod is loaded automatically next time.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ loop_" /proc/ksyms > /dev/null; then>
report_no_autoload loop && insmod loop
fi
grep: /proc/ksyms: No such file or directory
Ensure the module loop is loaded automatically next time.
insmod: ERROR: could not load module loop: No such file or directory
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep iso9660 /proc/filesystems > /dev/null; then
report_no_autoload iso9660 && modprobe iso9660
fi
Ensure the module iso9660 is loaded automatically next time.
modprobe: ERROR: could not insert 'isofs': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "The following is only needed for IDE/ATAPI CD-writers."
The following is only needed for IDE/ATAPI CD-writers.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep ide-scsi /proc/ide/drivers > /dev/null; then
report_no_autoload ide-scsi && modprobe ide-scsi
fi
grep: /proc/ide/drivers: No such file or directory
Ensure the module ide-scsi is loaded automatically next time.
modprobe: FATAL: Module ide-scsi not found.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # ================================================== ==============
arthur@arthur-T5082:~$ # Now check if it is recognized:
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # cdrecord -scanbus
arthur@arthur-T5082:~$ # Mount to an appropriate location after placing a CD in the drive
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ mkdir /media/Syquest
mkdir: cannot create directory ‘/media/Syquest’: Permission denied
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ mount -t vfat /dev/pda1 /media/Syquest
mount: only root can do that
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ ls -al /media/Syquest # Works !# Start here...
ls: cannot access /media/Syquest: No such file or directory
The script as copied from the terminal shows all the commands that are attempted to be run as well as the responses.
If the script cannot be read, I have the script results in a text file that I can upload and send to anyone who requests it.
Thanks in advance.
14.04 disk scsi
asked Dec 28 '18 at 18:14
Atrain01usAtrain01us
12
add a comment |
I am trying to access the contents of a Syquest Syjet 1.5gb drive that I have connected to the parallel port. The cable allows for connection to the parallel port as well as a scsi device.
I have upgraded from Ubuntu 8.04 to Ubuntu 14.04 LTS and am trying to access the scsi drive based on this post at ubuntuforums.org: How To Get Your External Syquest Drive Working In Ubuntu
I want to access the drive in order to get files off of the drive then I can retire the syquest drive. I also have some Iomega 100 and 2 gig Jaz drives I would like to do the same things with as well.
I followed the instructions in the above mentioned article and created an executable text file that was saved on the desktop that I tried running from both the desktop and from the terminal with no success.
So my question is: what do I need to do in order to be able to access the scsi drive from the parallel port and copy the files off of it?
When I run the script from the desktop, it runs so fast that I don't know if anything actually happens. When I run the script from the terminal, I get errors as well as some commands running ok I think. The whole script as run from the terminal is posted below:
arthur@arthur-T5082:~$ # Start here...
arthur@arthur-T5082:~$ # modprobe parport # Already maybe loaded
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # modprobe parport_pc # Already maybe loaded
arthur@arthur-T5082:~$ modprobe paride
modprobe: ERROR: could not insert 'paride': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The following 2 steps are not necessary on Breezy...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # mkdir /lib/modules/$(LINUX_VERSION)/misc
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # cp /lib/modules/$(LINUX_VERSION)/kernel/drivers/block/paride/epat.o /lib/modules/2.4.20-20.8/misc/epat.o
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "Inserting the necessary modules..."
Inserting the necessary modules...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ modprobe epat # Sparq Protocol
modprobe: ERROR: could not insert 'epat': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ modprobe pd # Sparq Driver
modprobe: ERROR: could not insert 'pd': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ dmesg | grep paride
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # Look for: "paride: epat registered as protocol 0"
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # modprobe pd drive0=0x378,1 drive1=0x3bc,1 # Example syntax
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # To support such a wide range of devices PARIDE, the parallel port IDE subsystem, is actually structured in three parts.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # There is a base paride module which provides a registry and some common methods for accessing the parallel ports.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The second component is a set of high-level drivers for each of the different type of supported device:
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pd IDE disk
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pcd ATAPI CD-ROM
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pf ATAPI disk
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pt ATAPI tape
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pg ATAPI generic devices
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The pg driver exists mainly to support parallel port ATAPI CD-R and CD-RW devices.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ #
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # Run the commands below from a script
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # ================================================== ==================
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "Running commandsmou..."
Running commandsmou...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ test whoami = 'root' || echo "You must be root to execute the commands."
You must be root to execute the commands.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ cdrecord -scanbus > /dev/null
wodim: No such file or directory.
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! (pidof kerneld || test -f "/proc/sys/kernel/modprobe"); then
echo "Neither kerneld nor kmod are running to automatically load modules".
fi
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ report_no_autoload() {
echo "Ensure the module $1 is loaded automatically next time."
}
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if test ! -f "/proc/scsi/scsi"; then
report_no_autoload scsi_mod && modprobe scsi_mod
fi
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ sg_" /proc/ksyms > /dev/null; then
report_no_autoload sg && modprobe sg
fi
grep: /proc/ksyms: No such file or directory
Ensure the module sg is loaded automatically next time.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ sr_" /proc/ksyms > /dev/null; then
report_no_autoload sr_mod && modprobe sr_mod
fi
grep: /proc/ksyms: No such file or directory
Ensure the module sr_mod is loaded automatically next time.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ loop_" /proc/ksyms > /dev/null; then>
report_no_autoload loop && insmod loop
fi
grep: /proc/ksyms: No such file or directory
Ensure the module loop is loaded automatically next time.
insmod: ERROR: could not load module loop: No such file or directory
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep iso9660 /proc/filesystems > /dev/null; then
report_no_autoload iso9660 && modprobe iso9660
fi
Ensure the module iso9660 is loaded automatically next time.
modprobe: ERROR: could not insert 'isofs': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "The following is only needed for IDE/ATAPI CD-writers."
The following is only needed for IDE/ATAPI CD-writers.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep ide-scsi /proc/ide/drivers > /dev/null; then
report_no_autoload ide-scsi && modprobe ide-scsi
fi
grep: /proc/ide/drivers: No such file or directory
Ensure the module ide-scsi is loaded automatically next time.
modprobe: FATAL: Module ide-scsi not found.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # ================================================== ==============
arthur@arthur-T5082:~$ # Now check if it is recognized:
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # cdrecord -scanbus
arthur@arthur-T5082:~$ # Mount to an appropriate location after placing a CD in the drive
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ mkdir /media/Syquest
mkdir: cannot create directory ‘/media/Syquest’: Permission denied
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ mount -t vfat /dev/pda1 /media/Syquest
mount: only root can do that
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ ls -al /media/Syquest # Works !# Start here...
ls: cannot access /media/Syquest: No such file or directory
The script as copied from the terminal shows all the commands that are attempted to be run as well as the responses.
If the script cannot be read, I have the script results in a text file that I can upload and send to anyone who requests it.
Thanks in advance.
14.04 disk scsi
asked Dec 28 '18 at 18:14
Atrain01usAtrain01us
12
amd64refers to x86_64. It works perfectly on Intel X86_64 CPU's so you can almost certainly update to 18.04 or 18.10.
– vidarlo
Dec 28 '18 at 18:41
What happens when you try to run the script? Do you get any error messages? What shows up when you rundmesg | tail -n 20after doingmodprobe paride? Edit your question to include any output from the commands.
– vidarlo
Dec 28 '18 at 18:47
add a comment |
I am trying to access the contents of a Syquest Syjet 1.5gb drive that I have connected to the parallel port. The cable allows for connection to the parallel port as well as a scsi device.
I have upgraded from Ubuntu 8.04 to Ubuntu 14.04 LTS and am trying to access the scsi drive based on this post at ubuntuforums.org: How To Get Your External Syquest Drive Working In Ubuntu
I want to access the drive in order to get files off of the drive then I can retire the syquest drive. I also have some Iomega 100 and 2 gig Jaz drives I would like to do the same things with as well.
I followed the instructions in the above mentioned article and created an executable text file that was saved on the desktop that I tried running from both the desktop and from the terminal with no success.
So my question is: what do I need to do in order to be able to access the scsi drive from the parallel port and copy the files off of it?
When I run the script from the desktop, it runs so fast that I don't know if anything actually happens. When I run the script from the terminal, I get errors as well as some commands running ok I think. The whole script as run from the terminal is posted below:
arthur@arthur-T5082:~$ # Start here...
arthur@arthur-T5082:~$ # modprobe parport # Already maybe loaded
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # modprobe parport_pc # Already maybe loaded
arthur@arthur-T5082:~$ modprobe paride
modprobe: ERROR: could not insert 'paride': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The following 2 steps are not necessary on Breezy...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # mkdir /lib/modules/$(LINUX_VERSION)/misc
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # cp /lib/modules/$(LINUX_VERSION)/kernel/drivers/block/paride/epat.o /lib/modules/2.4.20-20.8/misc/epat.o
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "Inserting the necessary modules..."
Inserting the necessary modules...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ modprobe epat # Sparq Protocol
modprobe: ERROR: could not insert 'epat': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ modprobe pd # Sparq Driver
modprobe: ERROR: could not insert 'pd': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ dmesg | grep paride
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # Look for: "paride: epat registered as protocol 0"
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # modprobe pd drive0=0x378,1 drive1=0x3bc,1 # Example syntax
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # To support such a wide range of devices PARIDE, the parallel port IDE subsystem, is actually structured in three parts.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # There is a base paride module which provides a registry and some common methods for accessing the parallel ports.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The second component is a set of high-level drivers for each of the different type of supported device:
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pd IDE disk
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pcd ATAPI CD-ROM
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pf ATAPI disk
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pt ATAPI tape
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pg ATAPI generic devices
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The pg driver exists mainly to support parallel port ATAPI CD-R and CD-RW devices.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ #
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # Run the commands below from a script
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # ================================================== ==================
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "Running commandsmou..."
Running commandsmou...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ test whoami = 'root' || echo "You must be root to execute the commands."
You must be root to execute the commands.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ cdrecord -scanbus > /dev/null
wodim: No such file or directory.
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! (pidof kerneld || test -f "/proc/sys/kernel/modprobe"); then
echo "Neither kerneld nor kmod are running to automatically load modules".
fi
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ report_no_autoload() {
echo "Ensure the module $1 is loaded automatically next time."
}
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if test ! -f "/proc/scsi/scsi"; then
report_no_autoload scsi_mod && modprobe scsi_mod
fi
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ sg_" /proc/ksyms > /dev/null; then
report_no_autoload sg && modprobe sg
fi
grep: /proc/ksyms: No such file or directory
Ensure the module sg is loaded automatically next time.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ sr_" /proc/ksyms > /dev/null; then
report_no_autoload sr_mod && modprobe sr_mod
fi
grep: /proc/ksyms: No such file or directory
Ensure the module sr_mod is loaded automatically next time.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ loop_" /proc/ksyms > /dev/null; then>
report_no_autoload loop && insmod loop
fi
grep: /proc/ksyms: No such file or directory
Ensure the module loop is loaded automatically next time.
insmod: ERROR: could not load module loop: No such file or directory
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep iso9660 /proc/filesystems > /dev/null; then
report_no_autoload iso9660 && modprobe iso9660
fi
Ensure the module iso9660 is loaded automatically next time.
modprobe: ERROR: could not insert 'isofs': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "The following is only needed for IDE/ATAPI CD-writers."
The following is only needed for IDE/ATAPI CD-writers.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep ide-scsi /proc/ide/drivers > /dev/null; then
report_no_autoload ide-scsi && modprobe ide-scsi
fi
grep: /proc/ide/drivers: No such file or directory
Ensure the module ide-scsi is loaded automatically next time.
modprobe: FATAL: Module ide-scsi not found.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # ================================================== ==============
arthur@arthur-T5082:~$ # Now check if it is recognized:
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # cdrecord -scanbus
arthur@arthur-T5082:~$ # Mount to an appropriate location after placing a CD in the drive
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ mkdir /media/Syquest
mkdir: cannot create directory ‘/media/Syquest’: Permission denied
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ mount -t vfat /dev/pda1 /media/Syquest
mount: only root can do that
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ ls -al /media/Syquest # Works !# Start here...
ls: cannot access /media/Syquest: No such file or directory
The script as copied from the terminal shows all the commands that are attempted to be run as well as the responses.
If the script cannot be read, I have the script results in a text file that I can upload and send to anyone who requests it.
Thanks in advance.
14.04 disk scsi
asked Dec 28 '18 at 18:14
Atrain01usAtrain01us
12
I am trying to access the contents of a Syquest Syjet 1.5gb drive that I have connected to the parallel port. The cable allows for connection to the parallel port as well as a scsi device.
I have upgraded from Ubuntu 8.04 to Ubuntu 14.04 LTS and am trying to access the scsi drive based on this post at ubuntuforums.org: How To Get Your External Syquest Drive Working In Ubuntu
I want to access the drive in order to get files off of the drive then I can retire the syquest drive. I also have some Iomega 100 and 2 gig Jaz drives I would like to do the same things with as well.
I followed the instructions in the above mentioned article and created an executable text file that was saved on the desktop that I tried running from both the desktop and from the terminal with no success.
So my question is: what do I need to do in order to be able to access the scsi drive from the parallel port and copy the files off of it?
When I run the script from the desktop, it runs so fast that I don't know if anything actually happens. When I run the script from the terminal, I get errors as well as some commands running ok I think. The whole script as run from the terminal is posted below:
arthur@arthur-T5082:~$ # Start here...
arthur@arthur-T5082:~$ # modprobe parport # Already maybe loaded
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # modprobe parport_pc # Already maybe loaded
arthur@arthur-T5082:~$ modprobe paride
modprobe: ERROR: could not insert 'paride': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The following 2 steps are not necessary on Breezy...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # mkdir /lib/modules/$(LINUX_VERSION)/misc
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # cp /lib/modules/$(LINUX_VERSION)/kernel/drivers/block/paride/epat.o /lib/modules/2.4.20-20.8/misc/epat.o
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "Inserting the necessary modules..."
Inserting the necessary modules...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ modprobe epat # Sparq Protocol
modprobe: ERROR: could not insert 'epat': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ modprobe pd # Sparq Driver
modprobe: ERROR: could not insert 'pd': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ dmesg | grep paride
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # Look for: "paride: epat registered as protocol 0"
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # modprobe pd drive0=0x378,1 drive1=0x3bc,1 # Example syntax
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # To support such a wide range of devices PARIDE, the parallel port IDE subsystem, is actually structured in three parts.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # There is a base paride module which provides a registry and some common methods for accessing the parallel ports.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The second component is a set of high-level drivers for each of the different type of supported device:
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pd IDE disk
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pcd ATAPI CD-ROM
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pf ATAPI disk
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pt ATAPI tape
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # pg ATAPI generic devices
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # The pg driver exists mainly to support parallel port ATAPI CD-R and CD-RW devices.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ #
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # Run the commands below from a script
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # ================================================== ==================
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "Running commandsmou..."
Running commandsmou...
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ test whoami = 'root' || echo "You must be root to execute the commands."
You must be root to execute the commands.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ cdrecord -scanbus > /dev/null
wodim: No such file or directory.
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! (pidof kerneld || test -f "/proc/sys/kernel/modprobe"); then
echo "Neither kerneld nor kmod are running to automatically load modules".
fi
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ report_no_autoload() {
echo "Ensure the module $1 is loaded automatically next time."
}
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if test ! -f "/proc/scsi/scsi"; then
report_no_autoload scsi_mod && modprobe scsi_mod
fi
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ sg_" /proc/ksyms > /dev/null; then
report_no_autoload sg && modprobe sg
fi
grep: /proc/ksyms: No such file or directory
Ensure the module sg is loaded automatically next time.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ sr_" /proc/ksyms > /dev/null; then
report_no_autoload sr_mod && modprobe sr_mod
fi
grep: /proc/ksyms: No such file or directory
Ensure the module sr_mod is loaded automatically next time.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep "^........ loop_" /proc/ksyms > /dev/null; then>
report_no_autoload loop && insmod loop
fi
grep: /proc/ksyms: No such file or directory
Ensure the module loop is loaded automatically next time.
insmod: ERROR: could not load module loop: No such file or directory
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep iso9660 /proc/filesystems > /dev/null; then
report_no_autoload iso9660 && modprobe iso9660
fi
Ensure the module iso9660 is loaded automatically next time.
modprobe: ERROR: could not insert 'isofs': Operation not permitted
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ echo "The following is only needed for IDE/ATAPI CD-writers."
The following is only needed for IDE/ATAPI CD-writers.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ if ! grep ide-scsi /proc/ide/drivers > /dev/null; then
report_no_autoload ide-scsi && modprobe ide-scsi
fi
grep: /proc/ide/drivers: No such file or directory
Ensure the module ide-scsi is loaded automatically next time.
modprobe: FATAL: Module ide-scsi not found.
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # ================================================== ==============
arthur@arthur-T5082:~$ # Now check if it is recognized:
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ # cdrecord -scanbus
arthur@arthur-T5082:~$ # Mount to an appropriate location after placing a CD in the drive
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ mkdir /media/Syquest
mkdir: cannot create directory ‘/media/Syquest’: Permission denied
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ mount -t vfat /dev/pda1 /media/Syquest
mount: only root can do that
arthur@arthur-T5082:~$
arthur@arthur-T5082:~$ ls -al /media/Syquest # Works !# Start here...
ls: cannot access /media/Syquest: No such file or directory
The script as copied from the terminal shows all the commands that are attempted to be run as well as the responses.
If the script cannot be read, I have the script results in a text file that I can upload and send to anyone who requests it.
Thanks in advance.
14.04 disk scsi
14.04 disk scsi
asked Dec 28 '18 at 18:14
Atrain01usAtrain01us
12
asked Dec 28 '18 at 18:14
Atrain01usAtrain01us
12
edited Jan 2 at 4:06
Atrain01us
asked Dec 28 '18 at 18:14
Atrain01usAtrain01us
12
asked Dec 28 '18 at 18:14
Atrain01usAtrain01us
12
asked Dec 28 '18 at 18:14
Atrain01usAtrain01us
12
12
amd64refers to x86_64. It works perfectly on Intel X86_64 CPU's so you can almost certainly update to 18.04 or 18.10.
– vidarlo
Dec 28 '18 at 18:41
What happens when you try to run the script? Do you get any error messages? What shows up when you rundmesg | tail -n 20after doingmodprobe paride? Edit your question to include any output from the commands.
– vidarlo
Dec 28 '18 at 18:47
add a comment |
amd64refers to x86_64. It works perfectly on Intel X86_64 CPU's so you can almost certainly update to 18.04 or 18.10.
– vidarlo
Dec 28 '18 at 18:41
What happens when you try to run the script? Do you get any error messages? What shows up when you rundmesg | tail -n 20after doingmodprobe paride? Edit your question to include any output from the commands.
– vidarlo
Dec 28 '18 at 18:47
amd64 refers to x86_64. It works perfectly on Intel X86_64 CPU's so you can almost certainly update to 18.04 or 18.10.– vidarlo
Dec 28 '18 at 18:41
amd64 refers to x86_64. It works perfectly on Intel X86_64 CPU's so you can almost certainly update to 18.04 or 18.10.– vidarlo
Dec 28 '18 at 18:41
What happens when you try to run the script? Do you get any error messages? What shows up when you run
dmesg | tail -n 20 after doing modprobe paride? Edit your question to include any output from the commands.– vidarlo
Dec 28 '18 at 18:47
What happens when you try to run the script? Do you get any error messages? What shows up when you run
dmesg | tail -n 20 after doing modprobe paride? Edit your question to include any output from the commands.– vidarlo
Dec 28 '18 at 18:47
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105179%2ftrying-to-access-syquest-syjet-1-5gig-scsi-drive-via-parallel-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105179%2ftrying-to-access-syquest-syjet-1-5gig-scsi-drive-via-parallel-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
amd64refers to x86_64. It works perfectly on Intel X86_64 CPU's so you can almost certainly update to 18.04 or 18.10.– vidarlo
Dec 28 '18 at 18:41
What happens when you try to run the script? Do you get any error messages? What shows up when you run
dmesg | tail -n 20after doingmodprobe paride? Edit your question to include any output from the commands.– vidarlo
Dec 28 '18 at 18:47