Install .. attempted upgrade from 3.3 to 3.4.2

[Biker1bob]

As we discussed else where I am having trouble trying to get scsi2pi installed on the supplied bullseye image from piscsi project.

You mentioned I did not have the latest version so I attempted an upgrade? Thinking I could install 3.4.2 over 3.3 it did not succeed. Attached is the output from trying to sudo install scsi2pi_3.4.2_bullseye_armhf-1.deb
pi@piscsi~ $ sudo apt install .scsi.txt

Please advise your idea as to why this failed. I have since removed scsi2pi 3.3 So I could try again?

James

[uweseimet]

The error message appears to be related to a general problem with the debian repository, but not to SCSI2Pi.
I suggest to first ensure that PiSCSI works without issues with your setup.

[Biker1bob]

Yes, piscsi works no issues, I have been using it without scsi2pi for a few weeks, no issues. Web interface is good.

James

[uweseimet]

This looks like a package/OS mismatch to. I've never seen something like that before.

[Biker1bob]

well I know I am using Debian 11 bullseye, I did cat /etc/os-release and it shows that. I am using a PIzero on the piscsi so thats 32bit.

I wget the file from your repository. then run the install script.

James

[Biker1bob]

I am using pi zero 2 - so it is 64bit.. I did sudo apt update and it showed 64bit pkgs.. so I need to download the bullseye pi2scsi for 64.. my issue as I thought I was on 32bit.. sorry for the wasted time.. guess cat /etc/os-release does not say 32 or 64 bit.. :(

[Biker1bob]

So I did it all again.. I updated and upgraded.. downloaded the 64bit scsi2pi.. installed.. all went fine.. added the lines to my .bashrc so I have the path.. try and run.. and this is my journalctl -f output.
pi@piscsi sudo journalctl.txt

[uweseimet]

According to the logfile the SCSI2Pi systemd service does not appear to be running. You should check the service status and the logfiles. Also see https://www.scsi2pi.net/en/target.html. Just use s2pctl instead of the webservice to check whether connecting to the s2p service works. Using s2pctl is the least complex setup for verifying this.
By the way, I don't think it is a good idea to install bullseye instead of the more recent bookworm. In about a year, when the successor of bookworm (trixie) will be released, bullseye support will be dropped by PiSCSI (see the PiSCSI wiki for details) and quite likely also by SCSI2Pi.