In a previous post called, Scaled Solar System, I used for math equations. Recently I needed the ability to create a few documents that are mostly works in progress, and I wanted the ability to track the progress of these documents using git.
Traditional word processing tools like Google Docs or Microsoft Word are insufficient because tracking changes with Microsoft Word is simply too difficult to deal with.
Both my wife and I are about to travel to China in November and we had several disparate itineraries from various airlines, tour operators, hotels, and such. In the past, I usually used Microsoft Excel to create a combined itinerary. However, last year I tried to keep the combined itinerary in the iOS Notes App. Both solutions were less than ideal. Excel proved too difficult to edit on the go because I either had to use the mobile Excel app or open up my laptop. Once changes are made it would be difficult to track the changes that I made.
With the iOS Notes App, editing the cells within a table is okay for simple stuff, but for a complicated itinerary, the formatting capabilities simply did not exist. The tracking of changes was also an issue.
This time around, I am going to use . I have not used since I wrote my fourth-year thesis back at University of Toronto, that would be 33 years ago!
It took me some time to set up my Neovim environment for editing and previewing. The MacTeX package is an excellent all-in-one package for my Mac. After about a couple days, I was able to create a master itinerary with all the attached source itineraries, all delivered in a single PDF document. I am also able to create hyperlinks within the PDF so that I can jump to the source itinerary or booking information from the master itinerary entry.
The resulting PDF master itinerary has been very satisfactory. It was fulfilling to once again work with !
I felt compelled to listen to my Bedroom audio system which I have not done for quite a while. I was pleasantly surprised by the musicality of the playlist that I quickly mustered for the night. I created the playlist on my old Mac mini 2018 using Apple Music configured for lossless music and USB output. On the other end of the USB is a Topping D90 DAC. My Q-Acoustic 3020i bookshelf speakers are powered by the S.M.S.L. DA-9 stereo amplifier.
With the acquisition of the S.M.SL. DA-9 stereo amplifier from my Winnipeg trip last year, and a freed, old Mac mini. I am able to swap out the old Raspberry Pi running Volumio as my streamer, and use the Mac mini instead. This way not only can I take advantage of Apple Music Loseless, but I can also install mpd to play my FLAC library. I still use the Rigelian App on both my Mac and iOS devices to control music from my mpd.
However to get the Mac mini working with my Topping D90 external DAC, I had to configure mpd appropriately. Below is a snippet of the mod configuration for audio_output. The configuration file is stored in ~/.mpd/mpd.conf.
audio_output {
type "osx"
name "D90 "
device "D90 " # optional
mixer_type "disabled"
dop "yes"
}
The following command can be used to obtain the detail of the USB audio devices that my Mac is aware of:
system_profiler SPAudioDataType
Note the extra trailing space of the D90 name.
Below are the pictures of the equipment and software of my stack.
My External DAC Topping D90My Stereo Amplifier S.M.S.L DA-9Q-Acoustics 3020i Bookshelf SpeakersI use the Rigelian App to control my music on mpdAll together now!
Several months ago I had an old 3TB hard drive (HDD) crashed on me. Luckily it was a hard drive that is primarily used for backup purposes, so the data lost can quickly be duplicated from source by performing another backup. Since it was not critical that I replace the damaged drive immediately, it was kind of left to fester until today.
Recently I acquired four additional WD Red 6TB HDD, and I wanted to install these new drives into my NAS chassis. Since I am opening the chassis, I will irradicate the damaged drive, and also take this opportunity to swap some old drives out of the ZFS pool that I created earlier and add these new drives into the pool.
I first use the following command to add two additional mirror vdev’s each composed of the two new WD Red drives.
The drive id’s is located in the following path: /dev/disk/by-id and is typically prefixed with ata or wwn.
This created two vdev’s into the pool, and I can remove an existing vdev. Doing so will automatically start redistributing the data on the removing vdev to the other vdev’s in the pool. All of this is performed while the pool is still online and running to service the NAS. To remove the old vdev, I execute the following command:
sudo zpool remove vault {vdev_name}
In my case, the old vdev’s name is mirror-5.
Once the remove command is given, the copying of data from the old vdev to the other vdev’s begins. You can check the status with:
sudo zpool status -v vault
The above will show the copying status and the approximate time it will take to complete the job.
Once the removal is completed, the old HDD of mirror-5 is still labeled for ZFS use. I had to use the labelclear command to clean the drive so that I could repurpose the drives for backup duty. Below is an example of the command.
The above indirect-5 can be safely ignored. It is just a reference to the old mirror-5.
This time we replaced the entire vdev, another technique is to replace the actual drives within the vdev. To do this, we will have to use the zpool replace command. We may also have to perform a zpool offline first before the replace command. This can be successively done on all the old drives in the mirror with newer drives with larger capacities to increase an existing vdev’s size.
In a previous post, I talked about switching our electricity rates from a tiered rate schedule to an Ultra Low Overnight (ULO) rate schedule. The latter rate schedule effectively means we pay a third less when using electricity from 11pm to 7am.
I have received a full month’s invoice while on the ULO rate. Below is a comparison with the previous year.
Compare 2023 vs 2024 Invoices
The above is a clear depiction of the resulting differences. We are able to get way more credits using the ULO rates. I call this a huge success, especially since we had a few hot days with the air conditioning running. Let us see how the remaining months will add to our credits.
As of January 2024, Alectra Utilities begin to allow residential customers with net meters to take advantage of the Ultra-Low Overnight (ULO) rate schedule. Since I have plenty of battery backup, I thought this ULO pricing schedule is perfect for my solar and battery backup situation.
Ultra-Low Overnight Electricity Rates from Alectra Utilities
The idea is to use my batteries from 7am to 11pm during the non-ULO periods, and then replenish my batteries at the low $0.028 per kWh after 11pm. I also switched our two Green Vehicles to charge after 11pm.
Another great benefit of the ULO schedule is that electricity generated and feedback to the grid is credited with the increased rates. This means any surplus electricity sent back to the grid between 4pm and 9pm during the weekdays gets a premium credit of $0.286 per kWh. This is ten times more than the usage after 11pm!
After reconfiguring my solar – backup system to this new schedule, you can see from the above chart that my electricity consumption is now in alignment with the ULO schedule.
The process of switching from a Tier Rate schedule to the ULO schedule was not simple. I had to call Alectra customer support and waited for literally hours to get a staff member who was knowledgeable enough to help me with the switch.
I hope the pain is now over and we begin to reap the benefits of the ULO pricing. Let us hope that this summer we will be able to collect much more credit because of ULO.
I liken individualism to cancerous cells to society, some are malignant and some are benign. If you have too much of the former, you embark on a social evolutionary force of society that may not be sustainable. Especially malignant forces that consumes social resources and then breaks foundational bonds between individuals, acting as a divisive force in society. I would also include those who are extremely wealthy and successful individuals here, since they contribute to the income gap and their individual morals act as tribal magnets creating a divisive force.
The benign goes with the flow or fails to seek enough influence or creates enough havoc to be a social impact.
Like malignant cells group together and prosper or grow to form tribes (tumors).
My current bet (not sure), is that a society that concentrates on individualism will ultimately result in a bilateral class structure where one class dominates over the other. The stability and growth potential will then depend on the attenuation of the tension between the classes. Done correctly, the subjugated class may not feel it. Done incorrectly results in a revolution.
All forms of government must face this reality of individualism. The difference is the way in which they manage it. The big experiment of the West is they let the tumors grow. This experiment has reached the typical dynastic period of 200–300 years, so it will be interesting to see if it is still sustainable or not. In the past, there has been self imposed chemotherapies to the likes of wars that perform resets on the malignant cells, so to create more room for individualism to flourish.
On April 9th, 2024 both my wife and I hopped on a flight to Vancouver to visit some friends and family. I got an excellent deal from Expedia for TD paying $1035 CAD for 2 return trips and a rental SUV for the week. We ended up getting a fancy Nissan Rogue for the trip.
We did not do any sightseeing other than Port Moody. Our primary purpose while staying in the City of Vancouver is to sample the Chinese food in Vancouver. This means hanging out largely in Richmond and doing some dim sum.
On the fourth day of our trip, we took the BC Ferries to Vancouver Island, visiting Nanaimo for two days, and spending our final two days in Victoria. We finished the week-long trip by taking a return ferry to Tsawwassen terminal, which is close enough to Richmond for us to get another good Chinese B.B.Q pork meal at HK BBQ Master, which I highly recommend!
Our rough schedule looked something like this:
Day 1 – Fish & chips along with ice cream at Port Moody; visited Natalie’s beautiful home on the hills, and gave Zoey (her cat) a nice rub; and then to Burnaby to stay at our cousin’s place and got introduced to Maple our new, small canine friend;
Day 2 – Lunch, snacks & dinner in Richmond; love the pineapple bun with its tasty, thick, cold butter; savored the lamb served at Hao’s;
Day 3 – Dim sum at Kirin restaurant in New Westminister and catching up with Agnes; followed by dessert at La Foret Jubilee with Natalie joining us;
Day 4 – Ferry from Horseshoe Bay to Departure Bay at Nanaimo; did some hiking and scenery;
Day 7 – Hiked the Beacon’s Hill Park with a huge breakfast at Blue Fox Cafe; met a couple of new friends, one named Lynda at the cafe; visited the Butterfly Gardens; drove along the Malahat scenic views; experienced high tea at Pendray Inn and Tea House; and finally dinner at the Pagliacci’s.
Day 8 – Took the ferry back from Swartz Bay to Tsawwassen just in time to do lunch at HK BBQ Master; say goodbye to Derrick and Maple; and back on the afternoon flight to Toronto; Darci welcomed us back home at 2:00am on the following day!
The most memorable part of the trip was of course getting to meet up with our family and friends. The best food from this trip had to be from HK BBQ Master, in my opinion, with an honorable mention of the Banh-mi sandwiches that Derrick got for us from his famous Vietnamese sandwich vendor.
What would we do differently? I think knowing what we know about Nanaimo, we would probably skip all of Nanaimo1 and reallocate the days to be one more in Vancouver and an extra day in Victoria. We would also switch the order of our visit to Vancouver and the Island. This way we can spend more time during the weekend with our friends and family.
With this trip and our visit to Victoria, the capital city of British Columbia, we have completed our tour of all of the provincial capitals in Canada. Checkbox checked!
Below is a summary video produced by Carol of our trip.
About three weeks ago, I was casually browsing eBay and found this little gem, a Host Bus Adapter that can do PCIe 2.0 x8 (~4 to 8GB/s). This is way better than the one that I purchased earlier (GLOTRENDS SA3116J PCIe SATA Adapter Card) which can operate on a single lane of PCIe 3.0 yielding only 1GB/s. I could not pass it up at a price of only $ 40 CAD, so I purchased two of these to replace the old adapter card I had.
LSI 6Gbps SAS HBA 9200-8i IT Mode ZFS FreeNAS unRAID + 2*SFF-8087 SATA
This new card LSI 6Gbps SAS HBA 9200-8i only supports 8 SATA ports per card, so I had to get two of them to support all of the hard drives that I have. These SAS HBA cards must have the IT (initiator target) mode firmware because the default firmware (IR mode) supports a version of hardware RAID, which I did not want. With the IT mode, the hard drives will be logically separated on the card and only share the physical bandwidth of the PCIe bus. This is a must for ZFS.
With these new cards, my write throughput to my NAS hard drives now averages around 500MB/s. Previously, I was only getting about half of this.
I wish I would have found these sooner. Now I have two spare PCIe SATA expansion cards, one supporting 8 ports, and the other supporting 16 ports. I will place them on another server. Perhaps in a future Proxmox cluster project.
Thanks to my cousins who also purchased Tesla using my Tesla referral code, I have some referral credits that I can use to select a 3 months trial of Tesla’s Full Self Driving (FSD) capability. On March 1st, 2024, I turned this feature on.
It was pretty easy to set up. After agreeing with all the legal stuff and enable the feature, I just set the destination, set it to drive mode, wait for the autopilot icon to show, and double tap the right stalk and away we go!
There are three settings to FSD: chill, average, aggressive/assertive. I just left it on the default, average mode.
Pulling out of the driveway, the car was a bit jerky, but once it got on the road, it made all the right decisions. I override the mode on our neighbourhood feeder road from Leslie Street just to make sure that I can override the mode, and then quickly re-engage the FSD.
On this occasion, all traveling was done on regular roads, no highways, so it was more challenging for the car. It made all the turns correctly, but I did have to override it once when it did not recognize the restricted Via Bus Lane on Yonge Street. It even pulled into the parking area at Mr. Congee, but did not fully complete the trip by parking the car. I had to park it manually.
On the way back, it hesitated too much on a left-hand turn. I had to press the accelerator to help it along. Doing this did not override the FSD mode.
I will be driving to Montreal in about 4 weeks, so I will be looking forward to testing FSD on the highway.
My initial assessment is that I probably would not have paid any more money to gain this feature. Once again, thanks to my cousins who allowed me to experience this through the use of my Tesla redemption credits.
In a previous post, I described the hardware changes that I made to facilitate additional drive slots on my NAS Media Server.
We now need to migrate from an LVM system consisting of 40TB of redundant mirrored storage using mdadm to a ZFS system consisting of a single pool and a dataset. Below is a diagram depicting the logical layout of the old and the intended new system.
Before the migration, we must backup all the data from the LVM system. I cobbled together a collection of old hard drives and then proceeded to create another LVM volume as the temporary storage of the content. This temporary volume will not have any redundancy capability, so if any one of the old hard drives fails, then out goes all the content. The original LVM system is mounted on /mnt/airvideo and the temporary LVM volume is mounted on /mnt/av2.
I used the command below to proceed with the backup.
I can then monitor the progress of the backup with:
tail -f ~/nohup.avs.rsync.out
The backup took a little more than 7 days to copy around 32 TB of data from our NAS server. During this entire process, all of the NAS services continued to run, so that downtime was almost non-existent.
Once the backup is completed, I wanted to move all the services to the backup before I started to dismantle the old LVM volume. The following steps were done:
Stop all services on other machines that were using the NAS;
Stop all services on the NAS that were using the /mnt/airvideo LVM volume;
Remove or comment out the entry in the /etc/fstab file that automatically mounts the old LVM volume on boot. This is no longer necessary because ZFS is remounted by default;
Now that the services are all up and running, we can then start destroying the old LVM volume (airvideovg2/airvideo) and volume group (airvideovg2). We can obtain a list of all the physical volumes that make up the volume group.
The /dev/mdX devices are the mdadm mirror devices, each consisting of a pair of hard drives.
sudo lvremove airvideovg2/airvideo
Do you really want to remove and DISCARD active logical volume airvideovg2/airvideo? [y/n]: y
Flushing 0 blocks for cache airvideovg2/airvideo.
Do you really want to remove and DISCARD logical volume airvideovg2/lv_cache_cpool? [y/n]: y
Logical volume "lv_cache_cpool" successfully removed
Logical volume "airvideo" successfully removed
sudo vgremove airvideovg2
Volume group "airvideovg2" successfully removed
At this point, both the logical volume and the volume group are removed. We say a little prayer to ensure nothing happens with our temporary volume (/mnt/av2), that is currently in operation.
We now have to disassociate the mdadm devices from LVM.
sudo pvremove /dev/md1
Labels on physical volume "/dev/md1" successfully wiped.
sudo pvremove /dev/md2
Labels on physical volume "/dev/md2" successfully wiped.
sudo pvremove /dev/md3
Labels on physical volume "/dev/md3" successfully wiped.
sudo pvremove /dev/md4
Labels on physical volume "/dev/md4" successfully wiped.
sudo pvremove /dev/nvme0n1p1
Labels on physical volume "/dev/nvme0n1p1" successfully wiped.
You can find the physical hard drives associated with each mdadm device using the following:
We then have to stop all the mdadm devices and zero their superblock so that we can reuse the hard drives to set up our ZFS pool.
sudo mdadm --stop /dev/md1
mdadm: stopped /dev/md1
sudo mdadm --stop /dev/md2
mdadm: stopped /dev/md2
sudo mdadm --stop /dev/md3
mdadm: stopped /dev/md3
sudo mdadm --stop /dev/md4
mdadm: stopped /dev/md4
# Normally you also need to do a --remove after the --stop,
# but it looks like the 6.5 kernel did the remove automatically.
#
# For all partitions used in the md device
for i in sdb1 sdc1 sdp1 sda1 sdo1 sdd1 sdg1 sdn1
do
sudo mdadm --zero-superblock /dev/${i}
done
Now with all of the old hard drives freed up, we can repurpose them to create our ZFS pool. Instead of using the /dev/sdX reference of the physical device, it is recommended to use /dev/disk/by-id with the manufacturer’s model and serial number so that the ZFS pool can be moved to another machine in the future. We also used the -f switch to let ZFS know that it is okay to erase the existing content on those devices. The command to create the pool we named vault is this:
zpool create -f vault mirror /dev/disk/by-id/ata-ST10000VN0008-2JJ101_ZHZ1KMA0-part1 /dev/disk/by-id/ata-WDC_WD101EFAX-68LDBN0_VCG6VRWN-part1 mirror /dev/disk/by-id/ata-ST8000VN0022-2EL112_ZA1E8GW4-part1 /dev/disk/by-id/ata-ST8000VN0022-2EL112_ZA1E8S0V-part1 mirror /dev/disk/by-id/ata-ST10000VN0004-1ZD101_ZA2C69FN-part1 /dev/disk/by-id/ata-ST10000VN0004-1ZD101_ZA2964KD-part1 mirror /dev/disk/by-id/ata-ST12000VN0008-2YS101_ZRT008SC-part1 /dev/disk/by-id/ata-ST12000VN0008-2YS101_ZV701XQV-part1
# The above created the pool with the old drives from the old LVM volume group
# We then added 4 more drives, 2 x 6TB, and 2 x 4TB drives to the pool
# Adding another 6TB mirror:
sudo zpool add -f vault mirror /dev/disk/by-id/ata-WDC_WD60EFRX-68L0BN1_WD-WX31D87HDU09-part1 /dev/disk/by-id/ata-WDC_WD60EZRZ-00GZ5B1_WD-WX11D374490J-part1
# Adding another 4TB mirror:
sudo zpool add -f vault mirror /dev/disk/by-id/ata-ST4000DM004-2CV104_ZFN0GTAK-part1 /dev/disk/by-id/ata-WDC_WD40EZRX-00SPEB0_WD-WCC4E0354579-part1
We also want to add the old NVMe as ZFS L2ARC cache.
ls -lh /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_500GB_S4P2NF0M419555D
lrwxrwxrwx 1 root root 13 Mar 2 16:02 /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_500GB_S4P2NF0M419555D -> ../../nvme0n1
sudo zpool add vault cache /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_500GB_S4P2NF0M419555D
Once the pool is created, we wanted to set some pool properties so that in the future when we replace these drives with bigger drives, the pool will automatically expand.
zpool set autoexpand=on vault
With the pool created, we can then create our dataset or filesystem and its associated mount point. We also want to ensure that the filesystem also supports posixacl.
zfs create vault/airvideo
zfs set mountpoint=/mnt/av vault/airvideo
zfs set acltype=posixacl vault
zfs set acltype=posixacl vault/airvideo
We mount the new ZFS filesystem on /mnt/av because the /mnt/airvideo is soft-linked to the temporary /mnt/av2 volume that is still in operation. We first have to re-copy all our content from the temporary volume to the new ZFS filesystem.
This took around 4 days to complete. We can all breathe easy again because all the data now have redundancy again! We can now bring the new ZFS filesystem live.
sudo systemctl stop apache2.service smbd nmbd plexmediaserver.service
sudo rm /mnt/airvideo
sudo zfs set mountpoint=/mnt/airvideo vault/airvideo
sudo systemctl start apache2.service smbd nmbd plexmediaserver.service
zfs list
NAME USED AVAIL REFER MOUNTPOINT
vault 31.0T 14.2T 96K /vault
vault/airvideo 31.0T 14.2T 31.0T /mnt/airvideo
The above did not take long and the migration is completed!
df -h /mnt/airvideo
Filesystem Size Used Avail Use% Mounted on
vault/airvideo 46T 32T 15T 69% /mnt/airvideo
Getting the capacity of our new ZFS filesystem shows that we now have 46TB to work with! This should last for at least a couple of years I hope.
I also did a quick reboot of the system to ensure it can come back up with the ZFS filesystem in tack and without issues. It has now been running for 2 days. I have not collected any performance statistics, but the services all feel faster.
