[SOLVED] Nikon Super Coolscan 4000 ED

Forum rules
Before you post please read this
Post Reply
User avatar
BobL
Level 1
Level 1
Posts: 7
Joined: Fri Mar 02, 2018 11:34 am
Location: Raleigh, NC US

[SOLVED] Nikon Super Coolscan 4000 ED

Post by BobL » Fri Mar 02, 2018 4:24 pm

Running Linux Mint 18.3 Sylvia, Cinnamon 64-bit on Lenovo Thinkpad T520 and trying to get a Nikon Super Coolscan 4000 ED film scanner to work.

While the scanner does seem to show up (in the GUI and in the lsscsi -g command - see example below), neither SANE nor VueScan seem to be able to find it.

Please help me to learn how to troubleshoot and solve problems associated with connecting an old firewire scanner to Linux Mint. Note that I have tried to read and understand many different sources of information (see reference list at the bottom of this post) but may be out of my depth to fully understand and implement their suggestions. Consequently, I would particularly appreciate any specific, prescriptive, suggestions you might have for me to try.

Code: Select all

</s>System:    Host: bob-ThinkPad-T520 Kernel: 4.13.0-36-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.3 Sylvia
Machine:   System: LENOVO (portable) product: 4243D12 v: ThinkPad T520
           Mobo: LENOVO model: 4243D12
           Bios: LENOVO v: 8AET65WW (1.45 ) date: 05/14/2015
CPU:       Dual core Intel Core i5-2520M (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9967
           clock speeds: max: 3200 MHz 1: 2491 MHz 2: 2491 MHz 3: 2491 MHz
           4: 2491 MHz
Graphics:  Card-1: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
           bus-ID: 00:02.0
           Card-2: NVIDIA GF119M [Quadro NVS 4200M] bus-ID: 01:00.0
           Display Server: X.Org 1.18.4 driver: nvidia
           Resolution: 1366x768@60.00hz, 1680x1050@59.95hz
           GLX Renderer: NVS 4200M/PCIe/SSE2
           GLX Version: 4.5.0 NVIDIA 384.111 Direct Rendering: Yes
Audio:     Card-1 Intel 6 Series/C200 Series Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Plantronics driver: USB Audio usb-ID: 002-003
           Sound: Advanced Linux Sound Architecture v: k4.13.0-36-generic
Network:   Card-1: Intel 82579LM Gigabit Network Connection
           driver: e1000e v: 3.2.6-k port: 7080 bus-ID: 00:19.0
           IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
           Card-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter
           driver: rtl8192ce port: 5000 bus-ID: 03:00.0
           IF: wlp3s0 state: down mac: <filter>
Drives:    HDD Total Size: 100.0GB (17.1% used)
           ID-1: /dev/sda model: HTS721010G9SA00 size: 100.0GB
Partition: ID-1: / size: 86G used: 11G (13%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 6.39GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 47.0C mobo: N/A gpu: 0.0:46C
           Fan Speeds (in rpm): cpu: 1977
Info:      Processes: 218 Uptime: 46 min Memory: 1823.3/5843.7MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35 <e>
My goal is to convert nearly 2000 photographs (slides and photo negatives) into my personal digital library. The Nikon Super Coolscan 4000 ED (https://www.imaging-resource.com/PRODS/LS4K/L40A.HTM) is a very-nice slide and film scanner that was sold by Nikon in 2001 (but which they no longer support). The one that I have includes a 50-slide auto feeder, which would significantly reduce the pain involved in such a project. If only I could get it to work...

I cannot rule out the possibility of a hardware problem with such an old scanner; however, I am inclined believe that the hardware is okay because:
  1. I've seen it actually scan a slide in some of my many attempts to get it working (not on Linux), and
  2. When I power it on, now connected to my Linux Mint 18.3 system, it shows up as a connected device (note the "LS-4000 ED" in the listing below)

Code: Select all

bob@bob-ThinkPad-T520 ~ $ lsscsi -g
[0:0:0:0]    disk    ATA      HTS721010G9SA00  C14V  /dev/sda   /dev/sg0 
[1:0:0:0]    cd/dvd  HL-DT-ST DVDRAM GT33N     LT20  /dev/sr0   /dev/sg1 
[6:0:0:0]    disk               LS-4000 ED       1.  /dev/sdb   /dev/sg2
Note, however, the difference between my listing (above) with this similar listing from an Ubuntu forum post (https://ubuntuforums.org/showthread.php ... ED+Scanner) discussing the same scanner:

Code: Select all

19:01 mathieu@vian ~% lsscsi -g     
[0:0:0:0]    disk    ATA      TOSHIBA MK1637GS DL04  /dev/sda  /dev/sg0
[1:0:0:0]    cd/dvd  TSSTcorp DVD+-RW TS-L632D DE04  /dev/sr0  /dev/sg1
[4:0:0:0]    scanner Nikon    LS-4000 ED       1.06  -         /dev/sg2
Clearly, I don't have something right - perhaps something to do with UDEV?

Background: I first attempted to get the scanner to work on Windows 10 because I am a lot more familiar with Windows than Linux. There are no Windows 10 (or even 64-bit) drivers for these scanners and the "home made" ones (hacked) that I could find seemed a little flakey. The best that I could achieve with Windows 10 was that the Device Manager would show the scanner as connected and working properly but neither NikonScan nor VueScan would see the scanner and interact with it consistently. I actually had inexplicable occasions where NikonScan and/or VueScan connected to the scanner and actually ran test scans - only to subsequently stop working. (That is why, as mentioned above, I am hopeful that my problem is not a scanner hardware problem.) Which brings me to Linux.

I have been wanting to learn about Linux anyway, so this scanner project gave me a good push to see what I could do. My perception is that Linux environments are far more open and transparent, giving me greater hope that I could more-easily troubleshoot the problems I am having with this old scanner.

I happened to have an extra hard disk drive for my ThinkPad T520 onto which I installed my Linux Mint 18.3 Sylvia, Cinnamon 64-bit. Over the past few weeks, I have flailed around (embarrassingly) trying this, then that, then the next thing - searching, Googling, reading, watching Linux tutorials, and so on, and so on. On the "good news" side, I have learned a LOT more about Linux. On the "bad news" side, I really do not have much to show for all of my efforts. I have done little to isolate the problem - and cannot even rule out a hardware problem.

At this point, when I power up the scanner, it shows up in Linux, both in the GUI and in the lsscsi command shown above; however, neither SANE nor VueScan can connect to it:

Code: Select all

bob@bob-ThinkPad-T520 ~ $ sudo sane-find-scanner
[sudo] password for bob: 

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
  # No USB scanners found. If you expected something different, make sure that
  # you have loaded a kernel driver for your USB host controller and have setup
  # the USB system correctly. See man sane-usb for details.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.
I will include output from a few other potentially-helpful commands below.

Code: Select all

bob@bob-ThinkPad-T520 ~ $ udevadm info -a -p /sys/class/scsi_generic/sg2

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:1c.4/0000:0d:00.3/fw1/fw1.0/host6/target6:0:0/6:0:0:0/scsi_generic/sg2':
    KERNEL=="sg2"
    SUBSYSTEM=="scsi_generic"
    DRIVER==""

  looking at parent device '/devices/pci0000:00/0000:00:1c.4/0000:0d:00.3/fw1/fw1.0/host6/target6:0:0/6:0:0:0':
    KERNELS=="6:0:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS=="sd"
    ATTRS{device_blocked}=="0"
    ATTRS{device_busy}=="0"
    ATTRS{dh_state}=="detached"
    ATTRS{eh_timeout}=="10"
    ATTRS{evt_capacity_change_reported}=="0"
    ATTRS{evt_inquiry_change_reported}=="0"
    ATTRS{evt_lun_change_reported}=="0"
    ATTRS{evt_media_change}=="0"
    ATTRS{evt_mode_parameter_change_reported}=="0"
    ATTRS{evt_soft_threshold_reached}=="0"
    ATTRS{ieee1394_id}=="0090b54001ffffff:00042c:0000"
    ATTRS{inquiry}==""
    ATTRS{iocounterbits}=="32"
    ATTRS{iodone_cnt}=="0x92"
    ATTRS{ioerr_cnt}=="0x71"
    ATTRS{iorequest_cnt}=="0x92"
    ATTRS{model}=="  LS-4000 ED    "
    ATTRS{queue_depth}=="1"
    ATTRS{queue_type}=="none"
    ATTRS{rev}=="  1."
    ATTRS{scsi_level}=="7"
    ATTRS{state}=="running"
    ATTRS{timeout}=="30"
    ATTRS{type}=="0"
    ATTRS{vendor}=="        "

  looking at parent device '/devices/pci0000:00/0000:00:1c.4/0000:0d:00.3/fw1/fw1.0/host6/target6:0:0':
    KERNELS=="target6:0:0"
    SUBSYSTEMS=="scsi"
    DRIVERS==""

  looking at parent device '/devices/pci0000:00/0000:00:1c.4/0000:0d:00.3/fw1/fw1.0/host6':
    KERNELS=="host6"
    SUBSYSTEMS=="scsi"
    DRIVERS==""

  looking at parent device '/devices/pci0000:00/0000:00:1c.4/0000:0d:00.3/fw1/fw1.0':
    KERNELS=="fw1.0"
    SUBSYSTEMS=="firewire"
    DRIVERS=="firewire_sbp2"
    ATTRS{model}=="0x004001"
    ATTRS{model_name}=="LS-4000 ED"
    ATTRS{rom_index}=="11"
    ATTRS{specifier_id}=="0x00609e"
    ATTRS{version}=="0x010483"

  looking at parent device '/devices/pci0000:00/0000:00:1c.4/0000:0d:00.3/fw1':
    KERNELS=="fw1"
    SUBSYSTEMS=="firewire"
    DRIVERS==""
    ATTRS{guid}=="0x0090b54001ffffff"
    ATTRS{hardware_version}=="0x00500a"
    ATTRS{is_local}=="0"
    ATTRS{units}=="0x00609e:0x010483"
    ATTRS{vendor}=="0x0090b5"
    ATTRS{vendor_name}=="Nikon"

  looking at parent device '/devices/pci0000:00/0000:00:1c.4/0000:0d:00.3':
    KERNELS=="0000:0d:00.3"
    SUBSYSTEMS=="pci"
    DRIVERS=="firewire_ohci"
    ATTRS{broken_parity_status}=="0"
    ATTRS{class}=="0x0c0010"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{current_link_speed}=="2.5 GT/s"
    ATTRS{current_link_width}=="1"
    ATTRS{d3cold_allowed}=="1"
    ATTRS{device}=="0xe832"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{driver_override}=="(null)"
    ATTRS{enable}=="1"
    ATTRS{irq}=="19"
    ATTRS{local_cpulist}=="0-3"
    ATTRS{local_cpus}=="0f"
    ATTRS{max_link_speed}=="2.5 GT/s"
    ATTRS{max_link_width}=="1"
    ATTRS{msi_bus}=="1"
    ATTRS{numa_node}=="-1"
    ATTRS{revision}=="0x04"
    ATTRS{subsystem_device}=="0x21cf"
    ATTRS{subsystem_vendor}=="0x17aa"
    ATTRS{vendor}=="0x1180"

  looking at parent device '/devices/pci0000:00/0000:00:1c.4':
    KERNELS=="0000:00:1c.4"
    SUBSYSTEMS=="pci"
    DRIVERS=="pcieport"
    ATTRS{broken_parity_status}=="0"
    ATTRS{class}=="0x060400"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{current_link_speed}=="2.5 GT/s"
    ATTRS{current_link_width}=="1"
    ATTRS{d3cold_allowed}=="1"
    ATTRS{device}=="0x1c18"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{driver_override}=="(null)"
    ATTRS{enable}=="1"
    ATTRS{irq}=="16"
    ATTRS{local_cpulist}=="0-3"
    ATTRS{local_cpus}=="0f"
    ATTRS{max_link_speed}=="5 GT/s"
    ATTRS{max_link_width}=="1"
    ATTRS{msi_bus}=="1"
    ATTRS{numa_node}=="-1"
    ATTRS{revision}=="0xb4"
    ATTRS{secondary_bus_number}=="13"
    ATTRS{subordinate_bus_number}=="13"
    ATTRS{subsystem_device}=="0x21cf"
    ATTRS{subsystem_vendor}=="0x17aa"
    ATTRS{vendor}=="0x8086"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

Code: Select all

bob@bob-ThinkPad-T520 ~ $ ls -la /dev/sg2
crw-rw---- 1 root disk 21, 2 Mar  2 13:31 /dev/sg2

Code: Select all

bob@bob-ThinkPad-T520 ~ $ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: HTS721010G9SA00  Rev: C14V
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: HL-DT-ST Model: DVDRAM GT33N     Rev: LT20
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi6 Channel: 00 Id: 00 Lun: 00
  Vendor:          Model:   LS-4000 ED     Rev:   1.
  Type:   Direct-Access                    ANSI  SCSI revision: 06
Finally, here is a listing of a few of the places that I have already looked for information (certainly not fully understanding all of the great information that they convey): Thank you, in advance, for any help.

UPDATE: Reading the sane-scsi man page again, I noticed: "A common issue with SCSI scanners is what to do when you booted the system while the scanner was turned off?" So far, I've always booted my Linux with the scanner off and then turned it on. So, this time, I tried leaving the scanner turned on and rebooted my Linux. This did not, however, make sane-find-scanner discover my scanner. But it did, interestingly, change the device assignment from SG2 to SG1:

Code: Select all

bob@bob-ThinkPad-T520 ~ $ lsscsi -g
[0:0:0:0]    disk    ATA      HTS721010G9SA00  C14V  /dev/sda   /dev/sg0 
[1:0:0:0]    cd/dvd  HL-DT-ST DVDRAM GT33N     LT20  /dev/sr0   /dev/sg2 
[6:0:0:0]    disk               LS-4000 ED       1.  -          /dev/sg1 
UPDATE2: One more bit of additional information. I am adding what Syslog shows when I turn on the scanner. I can't help but to think that Linux (perhaps UDEV) seems to think my scanner is a disk drive.

Code: Select all

Mar  3 08:40:23 bob-ThinkPad-T520 kernel: [  205.491290] firewire_core 0000:0d:00.3: phy config: new root=ffc1, gap_count=5
Mar  3 08:40:26 bob-ThinkPad-T520 kernel: [  208.338612] firewire_core 0000:0d:00.3: phy config: new root=ffc1, gap_count=5
Mar  3 08:40:29 bob-ThinkPad-T520 kernel: [  211.190179] firewire_core 0000:0d:00.3: created device fw1: GUID 0090b54001ffffff, S400
Mar  3 08:40:29 bob-ThinkPad-T520 kernel: [  211.219708] scsi host6: SBP-2 IEEE-1394
...  <some irrelevant log entries from the firewall>
Mar  3 08:40:29 bob-ThinkPad-T520 kernel: [  211.423310] firewire_sbp2 fw1.0: logged in to LUN 0000 (0 retries)
Mar  3 08:40:29 bob-ThinkPad-T520 kernel: [  211.429856] scsi host6: scsi scan: INQUIRY result too short (7), using 36
Mar  3 08:40:29 bob-ThinkPad-T520 kernel: [  211.429861] scsi 6:0:0:0: Direct-Access                LS-4000 ED       1. PQ: 0 ANSI: 6
Mar  3 08:40:29 bob-ThinkPad-T520 kernel: [  211.443374] sd 6:0:0:0: Attached scsi generic sg2 type 0
Mar  3 08:40:29 bob-ThinkPad-T520 kernel: [  211.449871] sd 6:0:0:0: [sdb] Spinning up disk...
Mar  3 08:40:31 bob-ThinkPad-T520 kernel: [  212.477743] .
Mar  3 08:40:32 bob-ThinkPad-T520 kernel: [  213.501759] .
Mar  3 08:40:34 bob-ThinkPad-T520 kernel: [  214.525738] .
Mar  3 08:40:35 bob-ThinkPad-T520 kernel: [  215.549708] .
Mar  3 08:40:36 bob-ThinkPad-T520 kernel: [  216.573705] .
Mar  3 08:40:37 bob-ThinkPad-T520 kernel: [  217.597637] .
Mar  3 08:40:38 bob-ThinkPad-T520 kernel: [  218.621635] .
Mar  3 08:40:39 bob-ThinkPad-T520 kernel: [  219.645580] .
Mar  3 08:40:40 bob-ThinkPad-T520 kernel: [  220.669553] .
Mar  3 08:40:41 bob-ThinkPad-T520 kernel: [  221.693428] .
Mar  3 08:40:42 bob-ThinkPad-T520 kernel: [  222.877425] .
Mar  3 08:40:43 bob-ThinkPad-T520 kernel: [  223.965363] .
Mar  3 08:40:44 bob-ThinkPad-T520 kernel: [  224.989330] .
Mar  3 08:40:45 bob-ThinkPad-T520 kernel: [  226.013338] .
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  227.037379] .
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.061353] .
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.063912] ready
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.070400] sd 6:0:0:0: [sdb] Sector size 0 reported, assuming 512.
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.084101] sd 6:0:0:0: [sdb] 1 512-byte logical blocks: (512 B/512 B)
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.084109] sd 6:0:0:0: [sdb] 0-byte physical blocks
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.090900] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.093469] sd 6:0:0:0: [sdb] Cache data unavailable
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.093472] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.113897] sd 6:0:0:0: [sdb] Sector size 0 reported, assuming 512.
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.148483] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.148505] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.148515] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.148525] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.148533] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.148545] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.151265] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.151304] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.151313] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.151324] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.151332] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.151350] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.153670] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.153696] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.153706] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.153716] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.153722] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.153735] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.153762] ldm_validate_partition_table(): Disk read failed.
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.156129] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.156155] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.156164] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.156173] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.156179] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.156187] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.158599] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.158620] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.158627] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.158635] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.158639] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.158647] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.161126] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.161156] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.161164] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.161171] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.161176] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.161183] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.164108] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.164129] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.164137] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.164144] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.164150] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.164157] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.164180] Dev sdb: unable to read RDB block 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.167086] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.167108] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.167116] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.167123] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.167128] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.167136] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.170064] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.170084] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.170092] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.170099] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.170103] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.170111] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.172912] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.172933] sd 6:0:0:0: [sdb] tag#0 Sense Key : Aborted Command [current] 
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.172941] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Data phase error
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.172948] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.172953] print_req_error: I/O error, dev sdb, sector 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.172960] Buffer I/O error on dev sdb, logical block 0, async page read
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.175920]  sdb: unable to read partition table
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.175931] sdb: partition table beyond EOD, enabling native capacity
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.185504] sd 6:0:0:0: [sdb] Sector size 0 reported, assuming 512.
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.226135] ldm_validate_partition_table(): Disk read failed.
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.237201] Dev sdb: unable to read RDB block 0
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.247617]  sdb: unable to read partition table
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.247631] sdb: partition table beyond EOD, truncated
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.265596] sd 6:0:0:0: [sdb] Sector size 0 reported, assuming 512.
Mar  3 08:40:46 bob-ThinkPad-T520 kernel: [  228.309530] sd 6:0:0:0: [sdb] Attached SCSI disk
Last edited by BobL on Fri Apr 13, 2018 10:37 am, edited 4 times in total.
Regards,

BobL

“Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25, 1998]

User avatar
Lanser
Level 4
Level 4
Posts: 261
Joined: Mon Mar 08, 2010 5:12 am
Location: Salzburg Austria

Re: Nikon Super Coolscan 4000 ED

Post by Lanser » Fri Mar 02, 2018 6:01 pm

Hi BobL. I was using a Nikon Coolscan 4000 ED for many years with Mint 17x, 18x and LMDE2. I used VueScan as the front end with excellent results.
My 4000ED was USB but VueScan also supports the Firewire version. As long as you have the firewire interface running, it should just plug and play.

cheers

Lanser
By continuing to breathe, you agree to the following terms and conditions.......

User avatar
BobL
Level 1
Level 1
Posts: 7
Joined: Fri Mar 02, 2018 11:34 am
Location: Raleigh, NC US

Re: Nikon Super Coolscan 4000 ED

Post by BobL » Fri Mar 02, 2018 6:46 pm

Hi Lanser, Thank you for your reply. It is encouraging to know that my scanner has worked with Linux Mint for other people. I know that my firewire (IEEE 1394) interface is working because, when I turn the scanner on, it shows up (both in the GUI and in the lsscsi -g command).

BTW - I thought that the Nikon Super Coolscan 4000 ED supports only a IEEE 1394 connection. It seems, at least, that mine only supports IEEE 1394.

Thanks again.

BobL
Regards,

BobL

“Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25, 1998]

User avatar
Lanser
Level 4
Level 4
Posts: 261
Joined: Mon Mar 08, 2010 5:12 am
Location: Salzburg Austria

Re: Nikon Super Coolscan 4000 ED

Post by Lanser » Fri Mar 02, 2018 10:26 pm

Apologies BobL. You are right... I used my 4000 ED with my PC and the 1394 connection. It was my later 5000 ED that I used with USB.
I used VueScan with both (as well as an Epson Flatbed Scanner). Currently using a Cannon 9000F.

cheers

Lanser
By continuing to breathe, you agree to the following terms and conditions.......

User avatar
absque fenestris
Level 5
Level 5
Posts: 563
Joined: Sat Nov 12, 2016 8:42 pm
Location: Confoederatio Helvetica

Re: Nikon Super Coolscan 4000 ED

Post by absque fenestris » Sat Mar 03, 2018 12:13 am

External ports on your Thinkpad:
...
Four USB ports version 2.0
One eSATA/USB combo port
Ethernet RJ-45
IEEE 1394 FireWire 400

Hello Bobi

I use several FireWire 400 devices on my old 32bit G4-PPC Macs. Most of the time they are very stable.
If not: it's almost something with the FireWire cable. Try connecting your scanner with another cable.

The On-Off question when booting only applies to real SCSI devices - especially connected hard disks.
FireWire is hotplug-capable.

Best regards

P. S. Sometimes cleaning the FireWire-Port with ear sticks and pure gasoline helps...
Linux Mint 18.3 Sylvia (Mate) 32-bit - Acer D250 Netbook (Intel Atom N270, 2 GB RAM, 120 GB SSD)

User avatar
BobL
Level 1
Level 1
Posts: 7
Joined: Fri Mar 02, 2018 11:34 am
Location: Raleigh, NC US

Re: Nikon Super Coolscan 4000 ED

Post by BobL » Sun Mar 04, 2018 12:06 pm

Thank you, Absque.

I don't have another FW cable; however, I did try your suggestion cleaning both the cable ends and the ports on the scanner and computer. Alas, that didn't seem to help.

It seems, from the lsscsi -g commands shown at the top of my first post, that Linux (UDEV) is just not recognizing my scanner as a Nikon Coolscan. It is frustrating to be so close yet so far.

Regards,

BobL
Regards,

BobL

“Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25, 1998]

User avatar
absque fenestris
Level 5
Level 5
Posts: 563
Joined: Sat Nov 12, 2016 8:42 pm
Location: Confoederatio Helvetica

Re: Nikon Super Coolscan 4000 ED

Post by absque fenestris » Mon Mar 12, 2018 11:00 am

BobL wrote:
Sun Mar 04, 2018 12:06 pm
Thank you, Absque.

I don't have another FW cable; however, I did try your suggestion cleaning both the cable ends and the ports on the scanner and computer. Alas, that didn't seem to help.

It seems, from the lsscsi -g commands shown at the top of my first post, that Linux (UDEV) is just not recognizing my scanner as a Nikon Coolscan. It is frustrating to be so close yet so far.

Regards,

BobL
I'm sorry to hear that.
Maybe you have access to an old 32-bit device - e. g. Mac G4? ...I even had the programs
Linux Mint 18.3 Sylvia (Mate) 32-bit - Acer D250 Netbook (Intel Atom N270, 2 GB RAM, 120 GB SSD)

User avatar
BobL
Level 1
Level 1
Posts: 7
Joined: Fri Mar 02, 2018 11:34 am
Location: Raleigh, NC US

Re: Nikon Super Coolscan 4000 ED

Post by BobL » Mon Mar 12, 2018 11:36 am

Dear all,

With all due thanks to Absque and Lanser, who attempted to help, I've been disappointed that no one else attempted to help me to dive deeper - to actually troubleshoot my problem.

My Linux-literate son suggested that it may have been my "Wall of Text" (aka WoT) -- providing so much information in my initial post as to intimidate anyone from wanting to dive in and try to help me. If that was the case, I apologize. But I am not sure what to try next.

I will try to net things out here as succinctly as possible.

First off, I think that this is what my scanner should look like when I do an "lsscsi -g": (copied from "Nikon Coolscan 4000 ED, 10.10, udev.. on the Ubuntu forum, https://ubuntuforums.org/showthread.php ... ED+Scanner)":

Code: Select all

19:01 mathieu@vian ~% lsscsi -g     
[0:0:0:0]    disk    ATA      TOSHIBA MK1637GS DL04  /dev/sda  /dev/sg0
[1:0:0:0]    cd/dvd  TSSTcorp DVD+-RW TS-L632D DE04  /dev/sr0  /dev/sg1
[4:0:0:0]    scanner Nikon    LS-4000 ED       1.06  -         /dev/sg2
Notice that their third line shows "scanner Nikon LS-4000 ED"

Alas, here is what I have been seeing ever since trying to make the scanner work on Linux:

Code: Select all

bob@bob-ThinkPad-T520 ~ $ lsscsi -g
[0:0:0:0]    disk    ATA      HTS721010G9SA00  C14V  /dev/sda   /dev/sg0 
[1:0:0:0]    cd/dvd  HL-DT-ST DVDRAM GT33N     LT20  /dev/sr0   /dev/sg2 
[6:0:0:0]    disk               LS-4000 ED       1.  -          /dev/sg1 
Notice that my third line shows: "disk LS-4000 ED" - which leads me to think that UDEV, for some reason, did not determine that I have connected a Nikon scanner and seems to think it is a disk drive.

And, finally, here's the latest status from my messing with this: Two different people, Lanser and Ed Hamrick (of VueScan fame) both suggested that my problem could be the result of a defective Firewire cable. Hence, I bought one on Amazon (for about $6) and, much to my disappointment, things actually got worse! Here's what I see with the brand-new cable:

Code: Select all

bob@bob-ThinkPad-T520 ~ $ lsscsi -g
[0:0:0:0]    disk    ATA      HTS721010G9SA00  C14V  /dev/sda   /dev/sg0 
[1:0:0:0]    cd/dvd  HL-DT-ST DVDRAM GT33N     LT20  /dev/sr0   /dev/sg1
Nothing. That's right, nothing.

And here's what Syslog shows at the time I turned on the scanner:

Code: Select all

Mar 12 11:20:57 bob-ThinkPad-T520 kernel: [27602.254242] firewire_core 0000:0d:00.3: phy config: new root=ffc1, gap_count=5
Mar 12 11:21:00 bob-ThinkPad-T520 kernel: [27605.102386] firewire_core 0000:0d:00.3: phy config: new root=ffc1, gap_count=5
Mar 12 11:21:30 bob-ThinkPad-T520 kernel: [27635.579743] firewire_core 0000:0d:00.3: giving up on node ffc0: reading config rom failed: no ack
Could it be that I had the misfortune of purchasing a defective Firewire cable? What should I try next?

Just for comparison (and at the risk of creating yet another WoT), here is what Syslog shows when I put my original Firewire cable on and turn the scanner on:

Code: Select all

Mar 12 11:29:09 bob-ThinkPad-T520 kernel: [28094.095084] firewire_core 0000:0d:00.3: created device fw1: GUID 0090b54001ffffff, S400
Mar 12 11:29:09 bob-ThinkPad-T520 kernel: [28094.095091] firewire_core 0000:0d:00.3: phy config: new root=ffc0, gap_count=5
Mar 12 11:29:09 bob-ThinkPad-T520 kernel: [28094.596491] scsi host6: SBP-2 IEEE-1394
Mar 12 11:29:09 bob-ThinkPad-T520 kernel: [28094.799370] firewire_sbp2 fw1.0: logged in to LUN 0000 (0 retries)
Mar 12 11:29:09 bob-ThinkPad-T520 kernel: [28094.806169] scsi host6: scsi scan: INQUIRY result too short (7), using 36
Mar 12 11:29:09 bob-ThinkPad-T520 kernel: [28094.806183] scsi 6:0:0:0: Direct-Access                LS-4000 ED       1. PQ: 0 ANSI: 6
Mar 12 11:29:09 bob-ThinkPad-T520 kernel: [28094.819993] sd 6:0:0:0: Attached scsi generic sg2 type 0
Mar 12 11:29:09 bob-ThinkPad-T520 kernel: [28094.826899] sd 6:0:0:0: [sdb] Spinning up disk...
Mar 12 11:29:10 bob-ThinkPad-T520 kernel: [28095.861776] .
Mar 12 11:29:10 bob-ThinkPad-T520 kernel: [28095.890372] [UFW BLOCK] IN=enp0s25 OUT= MAC= SRC=fe80:0000:0000:0000:3ee2:2afe:0921:5473 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=484943 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
Mar 12 11:29:10 bob-ThinkPad-T520 kernel: [28095.890397] [UFW BLOCK] IN=enp0s25 OUT= MAC= SRC=fe80:0000:0000:0000:3ee2:2afe:0921:5473 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=118791 PROTO=UDP SPT=8612 DPT=8610 LEN=24 
Mar 12 11:29:10 bob-ThinkPad-T520 kernel: [28095.900574] [UFW BLOCK] IN=enp0s25 OUT= MAC= SRC=fe80:0000:0000:0000:3ee2:2afe:0921:5473 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=484943 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
Mar 12 11:29:10 bob-ThinkPad-T520 kernel: [28095.900594] [UFW BLOCK] IN=enp0s25 OUT= MAC= SRC=fe80:0000:0000:0000:3ee2:2afe:0921:5473 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=118791 PROTO=UDP SPT=8612 DPT=8610 LEN=24 
Mar 12 11:29:13 bob-ThinkPad-T520 kernel: [28096.885919] .
Mar 12 11:29:14 bob-ThinkPad-T520 kernel: [28097.909824] .
Mar 12 11:29:15 bob-ThinkPad-T520 kernel: [28098.933795] .
Mar 12 11:29:16 bob-ThinkPad-T520 kernel: [28099.957871] .
Mar 12 11:29:17 bob-ThinkPad-T520 kernel: [28100.981800] .
Mar 12 11:29:18 bob-ThinkPad-T520 kernel: [28102.005789] .
Mar 12 11:29:19 bob-ThinkPad-T520 kernel: [28103.061780] .
Mar 12 11:29:20 bob-ThinkPad-T520 kernel: [28104.117818] .
Mar 12 11:29:21 bob-ThinkPad-T520 kernel: [28105.173773] .
Mar 12 11:29:22 bob-ThinkPad-T520 kernel: [28106.229820] .
Mar 12 11:29:23 bob-ThinkPad-T520 kernel: [28107.509762] .
Mar 12 11:29:24 bob-ThinkPad-T520 kernel: [28108.533753] .
Mar 12 11:29:25 bob-ThinkPad-T520 kernel: [28109.557762] .
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28110.581737] .
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.605794] .
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.615183] sd 6:0:0:0: [sdb] Sector size 0 reported, assuming 512.
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.628801] sd 6:0:0:0: [sdb] 1 512-byte logical blocks: (512 B/512 B)
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.628805] sd 6:0:0:0: [sdb] 0-byte physical blocks
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.635889] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.638488] sd 6:0:0:0: [sdb] Cache data unavailable
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.638490] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.659785] sd 6:0:0:0: [sdb] Sector size 0 reported, assuming 512.
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.689274] ldm_validate_partition_table(): Disk read failed.
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.689294] Dev sdb: unable to read RDB block 0
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.689315]  sdb: unable to read partition table
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.689319] sdb: partition table beyond EOD, enabling native capacity
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.698459] sd 6:0:0:0: [sdb] Sector size 0 reported, assuming 512.
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.730330] ldm_validate_partition_table(): Disk read failed.
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.730393] Dev sdb: unable to read RDB block 0
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.730465]  sdb: unable to read partition table
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.730475] sdb: partition table beyond EOD, truncated
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.742997] sd 6:0:0:0: [sdb] Sector size 0 reported, assuming 512.
Mar 12 11:29:26 bob-ThinkPad-T520 kernel: [28111.772701] sd 6:0:0:0: [sdb] Attached SCSI disk
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.945055] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.945082] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.945088] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.945095] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.945100] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.947422] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.947442] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.947449] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.947457] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.947462] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.947473] Buffer I/O error on dev sdb, logical block 0, async page read
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.949891] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.949910] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.949917] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.949925] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.949930] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.949940] Buffer I/O error on dev sdb, logical block 0, async page read
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.952221] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.952228] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.952233] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.952238] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.952242] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.952249] Buffer I/O error on dev sdb, logical block 0, async page read
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.954507] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.954520] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.954525] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.954531] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.954534] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.954542] Buffer I/O error on dev sdb, logical block 0, async page read
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.956914] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.956923] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.956929] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.956943] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.956946] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.956950] Buffer I/O error on dev sdb, logical block 0, async page read
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.959224] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.959232] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.959238] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.959245] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.959257] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.959263] Buffer I/O error on dev sdb, logical block 0, async page read
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.961595] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.961602] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.961608] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.961615] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.961619] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.961635] Buffer I/O error on dev sdb, logical block 0, async page read
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.963923] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.963937] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.963943] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.963949] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.963953] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.963959] Buffer I/O error on dev sdb, logical block 0, async page read
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.966765] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.966778] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.966784] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Command sequence error
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.966789] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 01 00
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.966793] print_req_error: I/O error, dev sdb, sector 0
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.966799] Buffer I/O error on dev sdb, logical block 0, async page read
Mar 12 11:29:27 bob-ThinkPad-T520 kernel: [28111.969118] Buffer I/O error on dev sdb, logical block 0, async page read
Thanks, in advance, for any suggestions.
Regards,

BobL

“Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25, 1998]

pdc_2
Level 8
Level 8
Posts: 2395
Joined: Mon May 11, 2009 1:21 am

Re: Nikon Super Coolscan 4000 ED

Post by pdc_2 » Mon Mar 12, 2018 6:22 pm

I've been disappointed that no one else attempted to help me to dive deeper - to actually troubleshoot my problem.
we are sorry to hear you are disappointed; sadly, we all have our limits;

sometimes if you post on a more generic forum; eg https://www.linuxquestions.org/question ... rdware-18/

you find that those posting have a common interest in hardware; but come from many, many distros; ...... a wide range ......... just look at the signatures of those posting ... slackware .... fedora ... opensuse ....... ubuntu etc etc

you would have to acknowledge that your needs are a little special; but hopefully the broader range of Linux Questions might land the right fish for you; best of luck there

You have done very well to keep this scanner going so well; well done to you; I see it is about 18yrs old; in them days; linux must have been Red Hat 4 or something ............

User avatar
BobL
Level 1
Level 1
Posts: 7
Joined: Fri Mar 02, 2018 11:34 am
Location: Raleigh, NC US

Re: Nikon Super Coolscan 4000 ED

Post by BobL » Tue Mar 13, 2018 9:32 am

NEWS FLASH!

In "Some notes on failure diagnostics / troubleshooting the Nikon 4000 and 5000 scanners" (http://www.shtengel.com/gleb/Nikon_4000 ... ooting.htm)

I found this description in the Symptom/Problem/Solution table that very-closely matches what I have been seeing: "The scanner passes power-up initialization fine (no fast blinking), and is recognized by a computer (in Windows - Device Manager), BUT - Nikon Scan does NOT see it." The notes say: In every case (that I saw), it was caused by a failed SAA7356HL, with the following additional information: Replace SAA7356HL (http://www.shtengel.com/gleb/Nikon_ls40 ... repair.htm).

Yep, this may have been hardware problem all along. And I have found a very-nice man, with countless happy customers, who will fix it for me: Alex Ketzner (abstudios@live.com).

The basic servicing on an LS-4000 is $190. And he no longer replaces individual chips, so I'd need to replace the whole motherboard for an additional $350.

Needless to say, I am more than a little reluctant to spend $540 (plus shipping costs) on a 17-year-old scanner. :-) It may just be time to pack it all back up in the box and give it back to my brother - expressing all appropriate appreciation for the hours of fun and education that it has given me.

Now, if you've been able to keep up with all of my "WoT", you may recall that one of my key motivations for trying to make this scanner work with Linux was for its presumably greater openness and better diagnostic capabilities. So, PLEASE, someone help me here: If a hardware problem, failing IEEE-1394 (Firewire) controller, is my hypothesis, how can I prove (or disprove) it with Linux?

Is there a UDEV debug mode that I could turn on in order to see exactly what Linux is seeing from the scanner?

BTW - If, as suggested by pdc_2, the lack of response to this post is due to my putting it into the wrong forum, I apologize. Where is the right place and how do I go about moving it?

Thanks.
Regards,

BobL

“Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25, 1998]

User avatar
Pierre
Level 17
Level 17
Posts: 7289
Joined: Fri Sep 05, 2008 5:33 am
Location: Perth, AU.

Re: Nikon Super Coolscan 4000 ED

Post by Pierre » Tue Mar 13, 2018 10:40 am

well - - I've too, spent some amount of hours in scanning in many boxes of slides :o

and initially, that was using a Kaiser Baas scanner, to do that job.
- using win-xp - back then.

later on, I'd found another scanner, that was more stand-alone, but needed a usb, mainly for power,
& that saved the scanned slides to an SD card inserted into a lot on the side of the gadget.
- that worked just as well, and with the bonus of being O/S independent.
8)
Image
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.

pdc_2
Level 8
Level 8
Posts: 2395
Joined: Mon May 11, 2009 1:21 am

Re: Nikon Super Coolscan 4000 ED

Post by pdc_2 » Tue Mar 13, 2018 2:37 pm

the lack of response to this post is due to my putting it into the wrong forum, I apologize. Where is the right place and how do I go about moving it?
that would mean reading my previous post; a right place was suggested there ..... do try them

I used a video camera for several years ...... perhaps 10 or more years ago; it was Firewire connected; all the rpm and debian distros we were evaluating then all connected instantly; Firewire was fine then ..............

User avatar
absque fenestris
Level 5
Level 5
Posts: 563
Joined: Sat Nov 12, 2016 8:42 pm
Location: Confoederatio Helvetica

Re: Nikon Super Coolscan 4000 ED

Post by absque fenestris » Wed Mar 14, 2018 10:19 pm

Hello BobL
I know your problem from my own experience: how can you scan a very large number of slides as efficiently as possible.

18 years ago that was a 4000 dpi slide scanner - if you could afford it...

Tests with the Nikon 4000 ED scanner refer to Mac OS 9.1 - and even OS 9.1 had problems with Firewire. I'm pretty sure that this scanner has never really got a good driver on OSX. My experience.
Windows XP may have been better supported. So much about commercial systems.
Linux could work - or not. Mr. Hamrick has revitalized many devices, but not all. You can not blame him for that.
The charge belongs to the big companies that are very discreet with updates and have never supported Linux.

If I had to process 2000 slides today, I would take my digital Nikon SLR and mount a slide attachment - with my 38 year old macro lens.

Slide scanner with 4000 dpi = 5680 x 3760 pixels per photo
Cheapest Nikon SLR (24 MP) = 6000 x 4000 pixels per photo

And of course - I would be glad if the big players would support Linux directly.
Linux Mint 18.3 Sylvia (Mate) 32-bit - Acer D250 Netbook (Intel Atom N270, 2 GB RAM, 120 GB SSD)

User avatar
Lanser
Level 4
Level 4
Posts: 261
Joined: Mon Mar 08, 2010 5:12 am
Location: Salzburg Austria

Re: Nikon Super Coolscan 4000 ED

Post by Lanser » Thu Mar 15, 2018 10:40 pm

Hi BobL. I think I would try the following before sending the scanner for repair:
Try different Kernels. Older & Newer.
Try connecting to another Linux machine that has firewire.
Test your firewire with a different firewire connected device.
Boot up a different Distro Live Disk (Fedora or Manjaro) and check to see if your 4000ED is recognised.

Hope this helps
Lanser
By continuing to breathe, you agree to the following terms and conditions.......

User avatar
BobL
Level 1
Level 1
Posts: 7
Joined: Fri Mar 02, 2018 11:34 am
Location: Raleigh, NC US

Re: Nikon Super Coolscan 4000 ED

Post by BobL » Wed Apr 04, 2018 4:52 pm

Hello to all who have tried to help - and all who need help with similar problems.

Just to update my post: This past weekend, I dropped the scanner off with a guy who seems very competent at repairing them (the same guy who hosted those very handy web pages showing how to take those Nikon scanners apart and repair them). I feel like I have tried every combination between using the scanner with different computers, trying different Firewire cables, even different operating systems (Win 10 and Linux). All that said, I think that the first thing my repair guy will do is try the scanner with a set up that he knows works. If it works then, I'll know that it is my machine - perhaps the Firewire port (though I am 99% sure that I've tried the scanner with one other machine). I doubt it will work for him either. (I'm still thinking that it is the IEEE1394 controller chip on the mainboard.)

I will update this post when I learn more.

Regards,

BobL
Regards,

BobL

“Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25, 1998]

User avatar
BobL
Level 1
Level 1
Posts: 7
Joined: Fri Mar 02, 2018 11:34 am
Location: Raleigh, NC US

Re: [SOLVED] Nikon Super Coolscan 4000 ED

Post by BobL » Fri Apr 13, 2018 10:42 am

I wanted to go back and mark this thread as "solved" but cannot seem to find any obvious way to do so - so I just edited my original subject and will elaborate here.

Hardware problem after all - IEEE 1394 controller chip

The scanner seemed so close to working that I just couldn't believe it would be a hardware problem. Consequently, I spent a HUGE amount of time chasing down potential software solutions. On the positive side, I used the process to learn a lot more about Linux and now have two different "systems" (really, separate HDDs) - my old Windows 10 system and my new Linux Mint system - which has already saved me when I managed to temporarily mess up my Windows system.

There are a couple of people who will try to fix hardware with these old scanners. I settled in on Gleb Shtengel https://www.janelia.org/people/gleb-shtengel because he seemed very knowledgeable and helpful. He has posted a lot of information on the web (check out his pages http://www.shtengel.com/gleb/index.htm, a very impressive guy.)

Gleb tested the scanner, then disassembled the scanner and fixed the chip, and tested the scanner afterwards to prove that it worked. Then he sent it back to me and I tested it and proved that it works for me.

Thank you Gleb!
Regards,

BobL

“Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25, 1998]

User avatar
absque fenestris
Level 5
Level 5
Posts: 563
Joined: Sat Nov 12, 2016 8:42 pm
Location: Confoederatio Helvetica

Re: [SOLVED] Nikon Super Coolscan 4000 ED

Post by absque fenestris » Tue Apr 24, 2018 8:11 am

Hello BobL

Just out of curiosity: were you able to scan your 2000 photos?
Linux Mint 18.3 Sylvia (Mate) 32-bit - Acer D250 Netbook (Intel Atom N270, 2 GB RAM, 120 GB SSD)

Post Reply

Return to “Printers & Scanners”