Carry Flag

Just taking notes on the experiment Freenas - Storage / pools   - mypool - add zvol     - zvol name myscsizvol     - size 20G - Sharing / Block iscsi - target global configuration   - leave at defaults - basename of iqn.2005-10.org.freenas.ctl - portal - add with defaults - authorized access - add   - group id 1   - user iscsi   - secret secret - targets - add   - name - iscsi-trial   - portal group id 1 - extents - add   - name myextent   - extent type device   - device mypool/myscsizvo - associated targets   - target iscsi-trial   - lun id 0   - extent myextent Proxmox - Datacenter / storage - add iSCSI   - ID iscsi   - portal - IP address of the freenas server   - target  iqn.2005-10.org.freenas.ctl:iscsi-trial   - use luns directly - check that   - node has storage 'iscsi' as "available", not "unknown".   - it's content tab has a disk image listed - create virtual machine   - Hard Disk     - Bus SCSI     -

this is outdated now, updated notes on TrueNAS here:  http://carryflag.blogspot.com/2023/02/create-publicanonymous-windows-network.html After trying to follow a couple of outdated guides, here's my notes on how I figured this out: Storage / pools - create pool mypool - add dataset mydataset  - I used "Share Type" Windows Shell - cd /mnt/ mypool - chown -R nobody:nobody  mydataset Sharing / Windows (SMB) Shares - Add - click on the folder icon to browse to /mnt/ mypool / mydataset - check "Allow Guest Access" - check "Only Allow Guest Access"

For some reason, FreeNAS installation image doesn't seem to have serial console enabled. When googling around for this, folks seem to think this would be impossible because " If you don't have com ports (include disable port), boot process is stopped for waiting the port output is ready " However, pfSense manages to do this just fine. But they do have separate images, which is just fine. Next time I try to do this, I will - use an usb stick with activity led - plug in a usb keyboard - wait until the activity stops - hit "2" on the usb keyboard to select the grub menu item with serial console enabled. Maybe that will then allow me to install FreeNAS without a monitor. Not sure though.

While thinking about which RaspberryPi audio hat to buy next, I grabbed the list of Volumio supported dacs and googled them for you: adafruit-max98357 -  $6 generic i2s dac and class-d amp, not designed for Raspi allo-boss-dac - $65 i2s dac with 2 x RCA audio out allo-digione - $99 board with BNC and RCA SPDIF out piano-dac - $27 i2s dac with 2 x RCA, 3.5mm phone jack piano-dac-plus - not sure what this is applepi-dac - predecessor of $270 PecanPi ? fe-pi-audio - $16 SPI codec with RCA jacks for Line Out and 4 pin screw terminal for Speaker Out. hifiberry-amp - a discontinued board with 2x25W output power hifiberry-dac - a discontinued board? hifiberry-dacplus - $20-$35 dac with 2x RCA hifiberry-digi - 23€  S/PDIF output, TOSLINK + RCA hifiberry-digi-pro - 35€ I2S to S/PDIF output hifibox-dac - $26  3.5mm audio jack iqaudio-dacplus - previous version of NEW Pi-DAC ? iqaudio-digiplus - a sold out / discontinued board? iqaudio-amp - pre

Next time I will run into strange issues with gnu ld, I'll be sure to remember there's an option which leaves a broken executable instead of deleting it. --noinhibit-exec Then, for example readelf -l    may let me have a glimpse on what is actually happening. There was also this --trace option but so far that left me none the wiser.

Installing would have been easier if I had realised earlier that: There's an ' asg' image to be used, not the first on the list 'isg' ISG variant won't fail right away, but at some point aborts because the hardware is not found The disk interface better be Virtio SCSI disk will be a 'hard drive not found' failure of sorts SATA did install but it would not boot for some reason The hard drive needs to be large enough, or strange errors happen Below 10G drive, it will abort complaining it will need at least 10G With a 10G drive, it will fail during installation with the ' RPM Installation Erro r' With 15G drive, it succeeds. Afterwards I see the hardware requirements do specify 60G, but the installer just incorrect limits

Note to self, Set up a serial console for Proxmox VE before accidentally tripping over the network cables the next time:  enable serial-getty@ttyS1.service  start serial-getty@ttyS1.service Then, next time you do, simply   ssh iloc.lan vsp do see what's wrong in there.

Note to self: Ubuntu cloud image depends on serial console being present, which is not the default in Proxmox. While the bug has been reported over two years ago, it still seems to be there in the latest cosmic images. https://bugs.launchpad.net/cloud-images/+bug/1573095 Problem is not very obvious to figure out from the console: Luckily, the workaround is quick and easy: In VM / Hardware, Add Serial port Serial port 0 is the default that works.