How to kill Ubuntu and fix it

If you have two SSDs in a RAID 0, and one is in an enclosure. Put the drive in the enclosure into an Insignia enclosure, then plug it in and attempt to boot Ubuntu. You’ll get I/O errors, then you’ll force it off.

After you put it back in the old/working enclosure, you’ll find it just says loading, but sits there for a long time without booting.

Fixing it is easy, you should have a USB drive with Ubuntu on it. Boot from that, install mdadm “sudo apt-get install mdadm”, then assemble the RAID “sudo mdadm –assemble /dev/md0”. Then you just need to run fsck on the drive “fsck /dev/md0p1 -y”, I don’t remember the exact name for the partition on md0, you can get it by running “sudo fdisk -l”. No I’m not typing this on NUC.

After running fsck, you can reboot, and it should boot now. I won’t buy any Insignia products now, well not computer stuff, like USB 3.0 cards, enclosures. Could be the USB on the NUC. My other Insignia enclosure worked fine, until it fell over and the drive in it died. The enclosure might still work, never bought a new drive. That’s a 3.5 enclosure though.

Why the fuck is USB 3.0 so damn picky? The card either sucks, or the enclosure does. I don’t remember having any problems with USB 2.0, but all motherboards have working USB 2.0 on them.

How to hide your content from ad block users

Add “adsbygoogle” to the post’s class. I just tested it in Opera, and after adding that class to the div, the post was hidden. Could mess up the formatting though.

That’ll work for Adblock Plus.

Nothing special, their ad blocker does all the work for you. You just have to add the ad class to non ads.

Doesn’t appear to change the formatting. I need to add a couple brs under the ad.

If you want your whole site to be hidden, make a div with that class and put everything in it.

There’s always a downside to blocking stuff on sites. The website owner might be an asshole, and trick your blocker into blocking everything. Maybe later I’ll add a ad div. Maybe add a check to see if it’s hidden, if it is have JavaScript show them a message instead of the site.

iPerf 3

<br>[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd<br>[  4]   0.00-1.00   sec  82.8 MBytes   695 Mbits/sec    0    211 KBytes       <br>[  4]   1.00-2.00   sec  87.1 MBytes   731 Mbits/sec    0    211 KBytes       <br>[  4]   2.00-3.00   sec  86.7 MBytes   727 Mbits/sec    0    211 KBytes       <br>[  4]   3.00-4.00   sec  87.3 MBytes   732 Mbits/sec    0    211 KBytes       <br>[  4]   4.00-5.00   sec  85.9 MBytes   721 Mbits/sec    0    211 KBytes       <br>[  4]   5.00-5.67   sec  58.6 MBytes   729 Mbits/sec    0    211 KBytes       <br>- - - - - - - - - - - - - - - - - - - - - - - - -<br>[ ID] Interval           Transfer     Bandwidth       Retr<br>[  4]   0.00-5.67   sec   489 MBytes   722 Mbits/sec    0             sender<br>[  4]   0.00-5.67   sec   487 MBytes   721 Mbits/sec                  receiver<br><br>iperf Done.<br>

As you can see, the wired performance on my Banana Pi R1 is much better then the wireless on my TP-LINK. It’ll be interesting to see what the NETGEAR is on 5 GHz. Should be better then the 2.4 GHz on the TP-LINK. But it won’t be as good as the wired on my Banana Pi R1, the NVIDIA doesn’t do AC, and AC is probably still slower then wired gigabit.

<br>[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd<br>[  4]   0.00-1.00   sec  78.2 MBytes   656 Mbits/sec    0    221 KBytes       <br>[  4]   1.00-2.00   sec  86.6 MBytes   726 Mbits/sec    0    221 KBytes       <br>[  4]   2.00-3.00   sec  85.1 MBytes   714 Mbits/sec    0    221 KBytes       <br>[  4]   3.00-4.00   sec  86.6 MBytes   727 Mbits/sec    0    221 KBytes       <br>[  4]   4.00-5.00   sec  86.4 MBytes   725 Mbits/sec    0    221 KBytes       <br>[  4]   5.00-6.00   sec  86.7 MBytes   728 Mbits/sec    0    221 KBytes       <br>[  4]   6.00-7.00   sec  85.9 MBytes   721 Mbits/sec    0    221 KBytes       <br>[  4]   7.00-8.00   sec  86.6 MBytes   726 Mbits/sec    0    221 KBytes       <br>[  4]   8.00-9.00   sec  86.9 MBytes   729 Mbits/sec    0    221 KBytes       <br>[  4]   9.00-10.00  sec  86.5 MBytes   726 Mbits/sec    0    221 KBytes       <br>[  4]  10.00-11.00  sec  86.0 MBytes   721 Mbits/sec    0    221 KBytes       <br>[  4]  11.00-11.40  sec  35.2 MBytes   736 Mbits/sec    0    221 KBytes       <br>- - - - - - - - - - - - - - - - - - - - - - - - -<br>[ ID] Interval           Transfer     Bandwidth       Retr<br>[  4]   0.00-11.40  sec   977 MBytes   719 Mbits/sec    0             sender<br>[  4]   0.00-11.40  sec   976 MBytes   718 Mbits/sec                  receiver<br><br>iperf Done.<br>

Update
Using iPerf, not 3, the server running on router, and the client on NUC.

<br>[  3]  0.0- 1.0 sec   106 MBytes   890 Mbits/sec<br>[  3]  1.0- 2.0 sec   109 MBytes   911 Mbits/sec<br>[  3]  2.0- 3.0 sec   110 MBytes   919 Mbits/sec<br>[  3]  3.0- 4.0 sec   111 MBytes   930 Mbits/sec<br>[  3]  4.0- 5.0 sec   110 MBytes   921 Mbits/sec<br>[  3]  5.0- 6.0 sec   112 MBytes   940 Mbits/sec<br>[  3]  6.0- 7.0 sec   109 MBytes   918 Mbits/sec<br>[  3]  7.0- 8.0 sec   110 MBytes   926 Mbits/sec<br>[  3]  0.0- 8.9 sec   977 MBytes   921 Mbits/sec<br>

Which is faster then NUC to desktop. Desktop is running windows. Maybe cgywin has a penalty hit. The ethernet adapter on desktop should be fine, it’s made by Intel. Think it’s a regular PCI card.