lalaw

Quick update here, I was running some benchmarks today.  Off the top of my head:
 
1. local SSD was getting something like 1200 MB/s write and 1500 MB/s read
2. USB connected HDD was getting ~175 MB/s write and 175 MB/s read
3. NAS (not helios) connected at 1 Gbps was getting ~100 MB/s read/write
4. Helios in DAS mode and on Raid 10 was getting approximately 170 write and 250 read.
5. Helios in DAS mode on a single drive was getting 190 write and 220 read. 
 
For the capture 1 use case, I think a solid contender.  Unfortunately, as I described in the other thread, I can't get my whole array presented in DAS mode (it wants to give me 200GB for a 18TB array).
 
 
Updated: also ran on a single drive instead of the array.  Slightly better write numbers with slightly worse read numbers.  Also, frustratingly, drive capacity was off -- this time showing 1.2 TB instead of 10.

Quick update here, I was running some benchmarks today.  Off the top of my head:
 
1. local SSD was getting something like 1200 MB/s write and 1500 MB/s read
2. USB connected HDD was getting ~175 MB/s write and 175 MB/s read
3. NAS (not helios) connected at 1 Gbps was getting ~100 MB/s read/write
4. Helios in DAS mode and on Raid 10 was getting approximately 170 write and 250 read.
5. Helios in DAS mode on a single drive was getting 190 write and 220 read. 
 
For the capture 1 use case, I think a solid contender.  Unfortunately, as I described in the other thread, I can't get my whole array presented in DAS mode (it wants to give me 200GB for a 18TB array).
 
 
Updated: also ran on a single drive instead of the array.  Slightly better write numbers with slightly worse read numbers.  Also, frustratingly, drive capacity was off -- this time showing 1.2 TB instead of 10.

Quick update here, I was running some benchmarks today.  Off the top of my head:
 
1. local SSD was getting something like 1200 MB/s write and 1500 MB/s read
2. USB connected HDD was getting ~175 MB/s write and 175 MB/s read
3. NAS (not helios) connected at 1 Gbps was getting ~100 MB/s read/write
4. Helios in DAS mode and on Raid 10 was getting approximately 170 write and 250 read.
5. Helios in DAS mode on a single drive was getting 190 write and 220 read. 
 
For the capture 1 use case, I think a solid contender.  Unfortunately, as I described in the other thread, I can't get my whole array presented in DAS mode (it wants to give me 200GB for a 18TB array).
 
 
Updated: also ran on a single drive instead of the array.  Slightly better write numbers with slightly worse read numbers.  Also, frustratingly, drive capacity was off -- this time showing 1.2 TB instead of 10.

Documenting my full process:
 
1. Put helios64 into recovery mode.
2. Use BalenaEtcher to write Armbian_20.11.10_Helios64_buster_current_5.9.14.img.xz to eMMC.  Reboot
3. Go through 1st login on helios64, setup userrname/password.  Reboot
4. Go through armbian-config to install OMV.  Reboot
5. Per 25-NOV post, created dwc3-0-device.dts and added as an overlay.  Reboot
 
 
6. Login to OMV. Setup RAID 10 array.  
 
... To be updated after array is synced.
 
Side note, I remembered that I have a 5th drive that is not part of the array that I could try to mount:
Unfortunately, no device detected on the Mac.
 

Bunch of random questions:
 
1. Any ETA on when DAS mode would be rolled into kernel 5.x?  
2. Any ideas on how I can get around the 1 post per day limitation?
 
If I can take the liberty, I'd like to describe my setup and solicit suggestions.  
 
I have am running Capture1 on a Mac connected via USB-C.  I'd love to use the Helios64 as a r/w DAS for the Capture1, while still making it available (perhaps ro) to enable network access and backup.
 
Some issues that I foresee:
1. Because the DAS mode is using the Mass Storage Gadget, it seems like my choices are to expose the entire disk/block device or to have a file that simulates the block devices.  The problem with the file is that it would no longer appears as a filesystem in NAS mode, correct?
2. If my assumption in (1) is true, then I have to expose the entire disk.  For the Mac to read the disk, I assume I need to use exFat or Fat32 (as ext4, ZFS, etc. support on Mac sound spotty for r/w)
3. exFat/Fat32 don't appear to be first class citizens in the world of OMV, but it sounds like I can cobble together support and mount those disks manually
4. Once sorted out, would it be possible to combine the Capture1 disk with other NAS-dedicated disks in a SnapRaid group for redundancy?  And expose the Capture1 disk as a (r/o) share on the NAS?
 
My hope is that I can have Capture1 see as a local DAS for work, I can get some level of disk failure redundancy though period SnapRaid parity syncs, and I can create some sort of rsync job to maintain an offsite backup in case I have a bigger failure.