This will guide you to prepare a installation media from Windows and install ubuntu into Soekris net6501.
Stuffs you need:
- a USB stick that CAN BE RECOGNIZED by net6501 device.
Not sure? Attach it to net6501 and reboot. If you can read the SIZE of this stick while booting, it is.
- an ISO file for ubuntu server 32-bit. Version 16.10 is tested.
- rufus. Guide and download point at https://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows.
- a working serial connection from your workstation to your net6501, software included.
Prepare installation media:
- Use rufus to build the USB stick. Check the guide above.
- Link net6501 to your computer using serial connection and start the link. In this case, I’m using the default setting (Speed=19200, Data bits=8, Stop bits=1, Parity=None, Flow control=XON/XOFF).
- Boot your net6501 with USB stick attached.
- Hit ctrl-p to go into bios.
- Type “boot 81” (without quotes) and press enter to boot from USB.
- You will see that something wrong with gfxboot.
- Type this text below SLOWLY and press enter. DO NOT COPY AND PASTE:
- Do not press any key related to screen mode selection. It will be passed.
- Choose a language and continue installation steps as normal.
Grub configuration need to be adjusted for using serial as console.
Edit /etc/default/grub and change to these lines below:
Then run update-grub.
Hope this help you.
Microsoft launched KB3194721 (for SqlServer 2012) and KB3194718 (for SqlServer 2014) this month though WSUS channel. If you choose to deploy them though WSUS, just as I did, you may face a bug on a cluster based SqlServer.
On the server with SqlServer installed as cluster, these patches just act as cancelled or failed. For digging the problem, I download the package from Microsoft Download Site and try to install them manually. The first step is decompressing. Files are placed on the largest drive (I dunno it based on the total or free space). In my case, one disk drive for a database role is chosen. Then the upgrading procedure starts, with a bug that is:
If the owner of this instance role of cluster is the same computer, the role will be automatically stopped during update process, and will be started later. But while the role is set to stop, the disk drive is offline with it. So, if that drive is the largest, sadly, the update procedure fails — source files of update package are missing.
Even you run these packages manually, not from WSUS, it’s still not possible to choose the folder to decompress. If some drive of database role of cluster is larger than all server self-owned disks, you may want to STOP THE NODE in cluster as a workaround.
Microsoft fixed the problem about Windows Update working with WSUS, finally after nearly 2 months.
In our company, our major productive servers are hosted in vSphere as Windows-based virtual machines. Some of them need very big disks. Through the largest disk space supported in vSphere is 16TB (or maybe more, i dunno), I’m not interested to create such a big file in VMFS. It will be really a pain your *** when you have to move such a big file among datastores, even among data facilities by using portable hard drives.
Creating smaller disks instead of a big one for every Windows-based VM, IMHO.
Fortunately, Windows support to merge small disks as a big one, using dynamic disk function. There are 4 kinds of volume can be supported in such a condition: Spanned, Striped, Mirrored and RAID-5. You can consider them like JBOD, RAID-0, RAID-1 and RAID-5 functions in a simple legacy storage device.
Because data protection is existed in the SAN, Mirrored and RAID-5 volumes are not considered at all. Striped will make it a little faster when lots of virtual disks fight for limited IOPS resources within one datastore. But there is no way to extend any stripped volume (https://technet.microsoft.com/en-us/library/cc770938.aspx).
So, the useless volume format in a traditional world, spanned volume, is the best solution, maybe the only one. Next time when you need to create big virtual disks for Windows in any virtualization environment, don’t forget to consider using Spanned Volumes.
After several weeks testing, I’m sad to tell you all that at least currently, Windows 10.0.14394 (aka 1607) still cannot work with WSUS.
Problem: If there is Windows related package push from WSUS, svchost processes on Windows clients keep crashing.
Check this for details: https://social.technet.microsoft.com/Forums/windows/en-US/31718a20-64dd-43f7-87d7-c86f03f74a4d/14393-windows-update-crash-every-minute?forum=win10itprogeneral