Purpose: So you tried to upgrade your nanostation2 (or other ubiquiti hardware) and managed to “brick” it? This should get you back on your feet in no time.

Purpose:

To setup a routerboard or other routing device making use of a single Static IP address with a Qwest DSL modem. To make this work properly we will make use of Transparent bridging mode with the modem and we will make use of ppoe client on the routerboard.

Background:

You can easily order an static ip address with Qwest or many other providers, however they do not often tell you how to setup your devices with this new static information (in most cases). It is believed that with Qwest you must have a small block of addresses to properly allow your gateway/vpn/routerboard to have the external static address. This is incorrect! When the DSL modem is operating in transparent bridging mode the device directly after the modem should be able to have the external static IP. This however, does not mean this is simple to setup (mostly due to a lack of documentation on doing so).

So i had a system do this to me the other night. After removing a virus and rebooting several times the system appeared to be in working order. I shut down the system for the night. The system did not ever fully shutdown and in the morning it was "Forced off". After trying to boot again i got the BSOD with "UNMOUNTABLE_BOOT_VOLUME". This is a *mostly* patched windows XP professional machine. Mounting the drive in Linux doesn't show any apparent drive failures or data corruption. 

 A little digging turned up that if you boot off a XP install cd you can go into the recovery console. 

First try running the following commands. Make sure you have backups first though because there is a chance of data loss!

1. chkdsk c: /r

Reboot when completed. If that doesn't do it reboot into the recovery console again and try this.

2. fixboot 

If your like me that still didnt fix the problem. 

Reboot into bios (press del or f2 on system start) and look for the hard drive settings. I found the desktop i was working on has a SATA hard drive.

Under the drive controller settings there is an option to set the mode of the SATA drives. 

Look for RAID AUTO ATA. 

Make sure your drives are set to that and reboot. You should now load into windows again! If not you probably have a different error message and will have to go from there.

-E

Today i was trying to update my centOS 5x server (5.3 to be exact) and for some reason when i tried to run a yum update or yum install all i got was a HANGGGGGGGGGGGGGGGGGGGGGGGGGGG.

Luckly i found a rather simple solution (Thank you google!)

Orig: http://episteme.arstechnica.com/eve/forums/a/tpc/f/96509133/m/647005316631/inc/1

Poster: Alton

Try this. Do all 3 of these steps one after the other:

# rm -f /var/lib/rpm/__db*
# rpm --initdb
# rpm --rebuilddb

 I found when doing the above one right after the other that all of my problems went away and yum would once again happily work. It was suggested that this may be related to killing yum or RPM at the wrong time thus leaving a lock file open which can cause you problems. 

-E