A4091 and Zulu SCSI log error messages

[Lamaman71]

Hi Folks,

My Zulu SCSI log is throwing out some error/warning messages and I want to know what they mean and how to clear them. If anyone can help or has seen this before Id appreciate any advice.

Thanks

[12ms] Platform: ZuluSCSI RP2040
[12ms] FW Version: 24.03.07-release Mar 7 2024 20:03:17
[13ms] DIP switch settings: debug log 0, termination 1
[13ms] SCSI termination is enabled
[14ms] Flash chip size: 2048 kB
[14ms] SCSI target/disk mode selected by DIP switch, acting as a SCSI disk
[144ms] SD card detected, FAT64 volume size: 121921 MB
[145ms] SD MID: 0x03, OID: 0x53 0x44
[145ms] SD Name: SN128
[145ms] SD Date: 11/2023
[145ms] SD Serial: 0xF206C4D0
[230ms] Config file zuluscsi.ini not found, using defaults
[310ms] Active configuration:
[310ms] -- SelectionDelay = 255
[311ms] -- EnableUnitAttention = No
[311ms] -- EnableSCSI2 = Yes
[311ms] -- EnableSelLatch = No
[312ms] -- MapLunsToIDs = No
[312ms] -- EnableParity = Yes
[882ms] Finding images in directory /:
[934ms] -- Opening /hd0A4091.hda for id:0 lun:0
[937ms] ---- WARNING: file /hd0A4091.hda is not contiguous. This will increase read latency.
[938ms] ---- Configuring as disk drive drive
[939ms] ---- Read prefetch enabled: 8192 bytes
[990ms] -- Opening /hd1.hda for id:1 lun:0
[996ms] ---- Configuring as disk drive drive
[996ms] ---- Read prefetch enabled: 8192 bytes
[1047ms] -- Opening /hd2.hda for id:2 lun:0
[1052ms] ---- WARNING: file /hd2.hda is not contiguous. This will increase read latency.
[1053ms] ---- Configuring as disk drive drive
[1054ms] ---- Read prefetch enabled: 8192 bytes
[1104ms] -- Opening /hd3.hda for id:3 lun:0
[1110ms] ---- Configuring as disk drive drive
[1110ms] ---- Read prefetch enabled: 8192 bytes
[1161ms] -- Opening /hd4mac.hda for id:4 lun:0
[1167ms] ---- Configuring as disk drive drive
[1167ms] ---- Read prefetch enabled: 8192 bytes
[1193ms] -- Platform supports ROM drive up to 1692 kB
[1193ms] ---- ROM drive image not detected
[1194ms] SCSI ID: 0, BlockSize: 512, Type: 0, Quirks: 0, Size: 7831152kB
[1194ms] SCSI ID: 1, BlockSize: 512, Type: 0, Quirks: 0, Size: 16777216kB
[1195ms] SCSI ID: 2, BlockSize: 512, Type: 0, Quirks: 0, Size: 16777216kB
[1196ms] SCSI ID: 3, BlockSize: 512, Type: 0, Quirks: 0, Size: 16777216kB
[1197ms] SCSI ID: 4, BlockSize: 512, Type: 0, Quirks: 0, Size: 2097152kB
[1297ms] Initialization complete!
[9889ms] SCSI ID 0 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
[9905ms] SCSI ID 1 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
[9917ms] SCSI ID 2 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
[9926ms] SCSI ID 3 negotiated synchronous mode 10 MB/s (period 4x25 ns, offset 8 bytes)
[10097ms] WARNING: Host used command 0x1A which is affected by drive geometry. Current settings are 63 sectors x 255 heads = 16065 but image size of 15662304 sectors is not divisible. This can cause error messages in diagnostics tools.
[11567ms] WARNING: Host used command 0x1A which is affected by drive geometry. Current settings are 63 sectors x 255 heads = 16065 but image size of 33554432 sectors is not divisible. This can cause error messages in diagnostics tools.
[11894ms] WARNING: Host used command 0x1A which is affected by drive geometry. Current settings are 63 sectors x 255 heads = 16065 but image size of 33554432 sectors is not divisible. This can cause error messages in diagnostics tools.
[12909ms] WARNING: Host used command 0x1A which is affected by drive geometry. Current settings are 63 sectors x 255 heads = 16065 but image size of 33554432 sectors is not divisible. This can cause error messages in diagnostics tools.

[thomas]

File is not contiguous means just that. The file is split into two or more fragments. Probably the CF card was not completely empty when you created it, so it took the free space it found because a contiguous chunk was not available for the whole file.

Command 1A is MODE SENSE. It can be used to ask the device for various parameters. Among them is the geometry a.k.a. cylinders, heads, sectors. Normally a drive is made up by a whole number of cylinders. But the size of the files you created is not divisible by the size of a cylinder.

This is nothing to worry about. Geometry has no real meaning in AmigaOS. It's just HDToolbox trying to find a useful default. There are no "diagnostic tools" which could throw error messages. You might just waste a few sectors at the end of each virtual drive.