Once you have created a new volume in the CLI tool, Linux does not automatically see the disks. To remedy, use the following:

# echo “- – -” > /sys/class/scsi_host/host0/scan

If one of the volumes was still initializing when you did that, it will have been detected by the driver, but not assigned a device node. In that case, performing the above ritual after it has been initialized will not help. You first have to remove the device again, then rescan again:

# dmesg|grep 0:0:
scsi 0:0:0:3: Direct-Access Areca ARC-1260-VOL#03 R001 PQ: 1 ANSI: 3
scsi 0:0:0:3: Attached scsi generic sg4 type 0
# echo “scsi remove-single-device 0:0:0:3” > /proc/scsi/scsi
# echo “- – -” > /sys/class/scsi_host/host0/scan
# dmesg|grep 0:0:
scsi 0:0:0:3: Direct-Access Areca ARC-1260-VOL#03 R001 PQ: 1 ANSI: 3
scsi 0:0:0:3: Attached scsi generic sg4 type 0
scsi 0:0:0:3: Direct-Access Areca ARC-1260-VOL#03 R001 PQ: 0 ANSI: 3
sd 0:0:0:3: Attached scsi disk sdd
sd 0:0:0:3: Attached scsi generic sg4 type 0

If you’re running Hudson from the Debian package, with the built in Winstone servlet server, and want to serve the application on a specific path rather than the web root (when using it in combination with Apache and reverse proxy), edit /etc/default/hudson and add e.g. “–prefix=/hudson” to the commandline parameters.

Yes, they named it prefix.