root@deux:~# /usr/bin/wget http://ftp3.usa.openbsd.org/pub/OpenBSD/6.1/amd64/cd60.iso
ip link set dev $DEVICE up ip link add $BRIDGE type bridge ip link set $DEVICE master $BRIDGE ip link set dev $BRIDGE up
Chances are that at some time, you’ll need to repair a corrupted filesystem, or worse, fix something you accidentally broke. Sometimes, your operating system will do this, especially if you are a fan of Linux. Such as the case with the Core2, today:
[ 0.179209] Unpacking initramfs... [ 1.176420] ------------[ cut here ]------------ [ 1.176514] WARNING: at arch/x86/mm/init.c:504 free_init_pages+0x53/0x11f() [...] [ 1.177589] Call Trace: [ 1.177672] [<ffffffff81734b42>] dump_stack+0x19/0x1f [ 1.177759] [<ffffffff8104d6b6>] warn_slowpath_common+0x62/0x7b [ 1.177846] [<ffffffff8104d6e4>] warn_slowpath_null+0x15/0x17 [ 1.177933] [<ffffffff81037181>] free_init_pages+05x3/0x11f [ 1.178025] [<ffffffff81d32c4b>] free_initrd_mem+0x30/0x35 [ 1.178112] [<ffffffff81d1db2b>] populate_rootfs+0xeb/0x10c [ 1.178199] [<ffffffff81d1da40>] ? unpack_to_rootfs+0x289/0x289 [ 1.178286] [<ffffffff8100209b>] do_one_initcall+0x9b/0x135 [ 1.178373] [<ffffffff81d1b8eb>] kernel_init_freeable+0x154/0x1ea [ 1.178461] [<ffffffff81d1b981>] ? kernel_init_freeable+0x1ea/0x1ea [ 1.178550] [<ffffffff81725900>] ? rest_init+0x74/0x74 [ 1.178636] [<ffffffff81725909>] kernel_init+0x9/0xd6 [ 1.178723] [<ffffffff8173d73c>] ret_from_fork+0x7c/0xb0 [ 1.178810] [<ffffffff81725900>] ? rest_init+0x74/0x74 [ 1.178900] ---[ end trace ded000897d630586 ]--- [ 1.179052] Freeing initrd memory: 11812k freed
Long story short, the kernel became unhappy with the latest update, and being a headless machine with no remote hands, I had to figure how to fix it.
Now, although I don’t have remote hands, I have a fairly dated (and limited) sysrescue image which I can boot the system from, and manipulate my installation from there.
Despite architectural and distribution differences, a 3.x kernel with most options available can get you back online with minimal effort.
Althought teaching you how to handle LVM/etc is not something for a quick little diary entry, I will offer this bit of advice: The following mounting heirarchy tends to work OK for Debian, CentOS, and almost any other Linux distribution I’ve thrown at it:
# fsck.{filesystem} /dev/{device}{partition} #root partition
# mount -t {filesystem} /dev/{device}{partition} /mnt
# mount -o bind /dev /mnt/dev
# mount -t sysfs sys /mnt/sys
# mount -t devpts pts /mnt/dev/pts
# mount -t proc proc /mnt/proc
# cd /mnt
# {mount/fsck any subpartitions here}
# chroot /mnt /bin/{dash|bash|ash}
Happy repairs!
If you browse back a few pages, you might notice that along with the mass of printers, there are some PCs, LCDs, and associated components:
I’m hoping to continue refurbishing and selling the handful of laser printers to recoop my expenses (25’ U-Haul 1-way rentals are NOT cheap), but my wish is to rebuild these computers for those who cannot afford them.
Coming from a government auction, they’re all functional- but missing hard drives (and needing new CMOS batteries, but I have plenty CR2032s). There are 5 complete units that are worth salvaging, ranging from P4HT and Core2 based eras. 15â€-17†LCDs, keyboards, and mice are all included, of course.
They’ve all got Windows license stickers on the machines themselves, so I can reinstall an OS- should I be able to find drives. I don’t have drives, but I’m hoping to get a bulk order of ~160GB SATA1 disks cheap enough.
If you find yourself wanting to install ProxMox from their ISO image, and are stuck with SuperMicro hardware, you may notice that their iKVM often throws the video into 640×480, depending on your native local resolution. Not only that, but it sets minsize/maxsize to be the same- so you can’t resize the window!
Rather than give you a tutorial of installing ProxMox via Debian Jessie using a BIOS RAID, I figured I’d help with this, since more people have this issue.
First off, start the iKVM and set “Auto Window Resize†to true.
Boot into BIOS (it’s set to 800×600 on my device). Resize the window if it doesn’t automatically do so.
Disable “Auto Window Resizeâ€. Boot into your virtual CD.
After booting into the ProxMox ISO/CD, press the letter ‘E’. This will take you into a mode to edit the GRUB command line.
Using the arrow keys, place the cursor in the line ABOVE “linux …â€, and type:
gfxload=800x600x16,800x600
Then press the enter key. Finally, go to the end of the “linux …†line by pressing the down arrow, and then press ‘end’. Add
vga=788 -- vga=788
- onto the end of this linux line, ensuring to keep the space above.
Now, press F10, and let it boot. Your iKVM and all data will be reported to the system as an 800×600 video mode.
Now you can actually see the GPL license and agree to the terms!
This can easily be altered to utilize 800×600/etc- whatever your session supports (changing the vga= modes accordingly)- but keep in mind that iKVM can not be larger or smaller than your existing usable screen size, and I strongly suggest you keep it smaller.
Happy Installing!
