Showing posts with label Linux. Show all posts
Showing posts with label Linux. Show all posts

Saturday, January 12, 2013

Simple Codebox For Blogger

Why doesn't Blogger offer this as a code box formatting option??

I found several different methods that involved modifying your Blogger template by adding CSS code. I tried a few of them without the success I wanted. I did find this easy to use web app that will do what I want, until I decide to go back to messing with my Blogger template again.


Enter your code snippet, select a few options, and it outputs html that you can paste into your post that will do the job. For some reason it seems to add a whitespace to the beginning & two to the end of each line. Otherwise, it will work for me until I want to mess with the CSS thing.

Here's an output example. An interesting looking startup script for Virtualbox (I haven't tested this script however, so YMMV)...


#!/bin/bash

# Copyright Information
# CC License BY-NC-SA 3.0 Unported License (May 11, 2012)
# Charles Auer
# http://charlesa.net/scripts/linux/vboxscript.php

### BEGIN INIT INFO
# Provides:       vmboot
# Required-Start: vboxdrv $local_fs
# Required-Stop:  vboxdrv $local_fs
# Default-Start:  2 3 4 5
# Default-Stop:   0 1 6
# Short-Description: Stop/Start VMs before/after System shutdown
### END INIT INFO

# Updated 04/27/2012

# Add this script to /etc/init.d/
# Run "update-rc.d vmboot defaults 99 01" as root

# Written to work with VirtualBox 4.x
# This script will save the state of any running virtual machines.

# User who is running the VMs (Change this!)
VBOXUSER=vboxuser

# Environmental Variables (Do Not Modify!)
SU="sudo -H -u $VBOXUSER"
VBOXMANAGE="/usr/bin/VBoxManage --nologo"
# Get UUID of All Running VMs
# UUID looks like this: a02b5b54-a84d-48fa-8dac-2a3fad55717e
RUNNINGVMS=$($SU $VBOXMANAGE list runningvms | sed -e 's/^".*".*{\(.*\)}/\1/')
# Get UUID of All VMs
ALLVMS=$($SU $VBOXMANAGE list vms | sed -e 's/^".*".*{\(.*\)}/\1/')

# Functions
function getVMName()
{ echo $($SU $VBOXMANAGE list vms | grep "$1" | awk -F\" '{print $(NF -1)}'); }

# Check to ensure $ALLVMS is not null and exit if it is.
if [[ $ALLVMS = "" ]]; then
        echo "No VMs are detected on this host! Did you configure the VBOXUSER variable?"; exit 1
fi

case $1 in
stop)
if [[ -n $RUNNINGVMS ]]; then
        for v in $RUNNINGVMS; do
        echo -e "Saving state of \"$(getVMName $v)\"..." && $SU $VBOXMANAGE controlvm $v savestate
        done; else
        echo "No running VMs to save!"
fi
;;
start)
for v in $ALLVMS; do
        if [[ -n $($SU $VBOXMANAGE showvminfo $v | grep saved) ]]; then
                echo -e "Waiting for VM \"$(getVMName $v)\" to power on..." && $SU $VBOXMANAGE startvm $v --type headless 1> /dev/null && echo "VM \"$(getVMName $v)\" started successfully!"
        fi
# If the previous loop has an error, the loops exits and returns an error.
        if [[ $? -ne 0 ]]; then
                echo "There was an error starting $(getVMName $v)! Try starting it manually to see what the problem is."; break
        fi
done
if [[ -z $($SU $VBOXMANAGE showvminfo $v | grep saved) ]]; then
        echo "No Saved VMs to Start!"
fi
;;
status)
if [[ -n $RUNNINGVMS ]]; then
        echo "List of Running VMs:" && $SU $VBOXMANAGE list runningvms; else
                echo "No VMs Currently Running!"
fi
;;
list)
echo "List of All VMs:" && $SU $VBOXMANAGE list vms
;;
*)
echo "Usage: /etc/init.d/vmboot start | stop | status | list"; exit 1
;;
esac
exit 0
# eof

Samba: Empty .gvfs XUbuntu 12.10

Problem: Unable to navigate to and/or access remote smb (samba) shares via the bash shell.

It seems something changed when I upgraded from XUbuntu 12.04 to 12.10. I used to be able to open gigolo (which was set to automatically mount remote smb shares), and then work with them in bash by navigating to them with:

cd ~/.gvfs
Running an ls command would display all the remote shared folders and away we go

Now, even though the shares are mounted (I can navigate to them with my file manager), there is nothing in ~/.gvfs

Solution: After mounting the remote shares, you will find them under:

/run/user/username/gvfs/smb-share:server=smbServer,share=shareName,user=username

To save time, create symbolic links to the shares (which of course will only work when the share is mounted):

ln -s /run/user/username/gvfs/smb-share:server=smbServer,share=shareName,user=username shareLink

Distro: XUbuntu 12.10
File Manager: Thunar 1.4.0
Samba Connection Manager: gigolo 0.4.1

Friday, December 28, 2012

GMail Backup

The Cloud is great, right?

Keeping your precious personal data files floating about on who knows what server (located in which [totalitarian] nation?), "owned" by company X (subcontracted by company Y), which may (or may not) have a comprehensive security policy that may (or may not) be regularly enforced is (possibly) a wonderful thing, right?

Just for kicks, I think I'll keep a local copy of my family photos, "sensitive" documents, and (on to the point of this post) EMAIL.

Regardless of how our friends at Google utilize the personal information (see Terms & Privacy for more information), we all love GMail, right? It would be a sad day indeed if our beloved GMail account were to suddenly disappear for whatever reason. Or, the 10,000+ emails we never deleted were somehow lost. Again, I like local copies. I like backups.

Enter GMail Backup

GMail Backup is my current application de jour for doing exactly as it's name implies. Description:
Gmail Backup allows to backup and restore the content of your Gmail account. It uses the IMAP protocol to fetch and store your messages. It can also be used to migrate your messages between two accounts, for example between your private inbox and the Google Apps acount.
It's very easy to use, and offers your choice of full or incremental backup.


Download the latest version (gmail-backup-20110307 as of this writing), install, run, enter you GMail loging info, choose a location to store you mail backup, etc...

As you can see, the GUI is simple & self-explanatory, but a little note on the Since Date field is in order. This pertains to the "incremental" backup function. From the documentation:

Downloading all emails from your Gmail Account every time you want to backup your emails would be a nightmare. In this case it comes in hand the incremental downloading feature of email.
Gmail Backup checks all emails in the Gmail Account whether their are already downloaded. If so than it skips them. It only download emails which are not presented in your local copy. However, the checking emails takes time too.
As result, we recommend to specify the date since you want to download emails. For example:
gmail-backup.exe backup backup xxx@gmail.com passwd 20080101
In the example, I specify that I want do check and eventually download emails since 1 January 2008. Consequently, the process of updating of your backup is much faster.
I was using Thunderbird as my email client, and using it to keep a local copy of all my GMail. It has it benefits but these days the GMail web GUI & backing up the mail locally with GMail Backup works for me.


Notes:
Selecting Newest emails only seems the simplest option for keeping your backup current
Yes, you can run the application from the command-line
You can restore your mail to your GMail account with this application

Friday, May 14, 2010

Virtual Box Guest Additions & CentOS 5

Installed CentOS into a VirtualBox virtual machine this evening. I recommend installing the Guest Additions into your virtual machines. Simple to do under Ubuntu. A little more involved with CentOS, but still easy enough.

Google is your friend. Here it is quick and easy:
  1. Start the CentOS virtual machine.
  2. Mount the VboxGuestAdditions.iso
  3. Right-click on the VirtualBox CD icon
  4. Click VboxGuestAdditions.iso to mount it as a virtual CD in CentOS




  5. Press Ctrl+Alt+F2 to open a terminal session if you are not already in one.
  6. Login as yourself (if you have sudo permisions) or root (yes, I know, a terrible thing to ever do)
  7. As yourself preface your commands below with sudo; as root simply enter the following:
  8. mount /dev/hdc /media
  9. cp /media/VBoxLinuxAdditions-x86.run /home/your_username/
  10. cd ~/your_username
  11. chmod +x VBoxLinuxAdditions-x86.run
  12. yum -y install gcc
  13. If not already installed, you will also need to run:
  14. yum install kernel-devel kernel-headers
  15. Time to install the Guest Additions
  16. ./VBoxLinuxAdditions-x86.run
  17. reboot or telinit 6
That's pretty much it. More pointers can be found here.

Saturday, May 08, 2010

Ugly Boot Screen Ubuntu 10.04

Recently did a network upgrade from Ubuntu 9.10 to 10.04 LTS (desktop edition). The upgrade didn't work initially--there was some conflict with XUbuntu which I also had installed under 9.10. I removed all traces of Xubuntu and xfce, and then the network upgrade worked fine.

10.04 LTS is a fine distribution. I really like it. It's been a while since I used Ubuntu and one of the things I enjoy about it is that things just work. Wireless set-up, which had been so painful previously, was a breeze and the connection is fast! Much faster then it had been under XP on the same machine.

Well, to the point. One of Ubuntu 10.04's failings was the boot up splash screen!! So incredibly ugly! I should have taken a picture. The word UBUNTU was outlined in some kind of psychedelic malaise. Painful to look at. Not a show stopper, but please. This isn't a hack distro, this should be slick, professional, pleasant in every way.

Are they working on a fix? I know from bug reports that I am not the only one who's seen similar issues. I don't know, but there is a workaround. I just applied it on this very system I am using to post this entry. Here it is, step-by-step for new users. I used "Alternative One". The only thing I did differently was change screen resolution entries from 1280x1024 to 1024x768 to accommodate the maximum resolution of this relic of a laptop I am using. Here it is, fix that ugly boot logo in Ubuntu 10.04 (Lucid Lynx):

How to Fix the Big and Ugly Plymouth Logo in Ubuntu 10.04

I should post the fun I had doing a network upgrade from Ubuntu 8.04 LTS Server to the 10.04 LTS edition. I'm sure it would have been painless if I wasn't booting from a software RAID1 drives. I hope I can recall how I made it work so I can post for reference the next time I upgrade and it happens again--which of course it will. I have no doubt. It always does.

Oh, and I should mention I am having excellent success running XP from VBox OSE on this dinosaur. I can't believe it works, but it actually works very well!

Well, time to reinstall the Xubuntu desktop.

Saturday, August 29, 2009

Useful Linux Commands

A place to post useful Linux operations in case of organic memory failure:

Convert audio files with bitrate (-b) and sample rate (-ar) options:
avconv -i input.wav -b 64k -ar 41000 output.mp3

Determine which services are running:
service --status-all

Determine Distro Release Version:
lsb_release -a

Store a data CD on your filesystem (this is not one I forget but it pertains the following):
dd if=/dev/cdrom of=/some/dir/data.iso

Mount your virtual data CD:
sudo mount -t auto -o loop /some/dir/data.iso /mnt/vrtl-cd

Check your Linux software RAID status:
cat /proc/mdstat

Ext3 Filesystem Check
sudo umount /SomeFileSystem
sudo screen fsck.ext3 -v -f -p -D -C0 /SomeFileSystem

Sunday, May 03, 2009

Metamorphose File - Folder Renaming

This is a pretty cool application. Something that should be brainlessly easy under the command line in Linux—all I wanted to do was replace one character in all the filenames in one directory. Well, I ended my search when I found Metamorphose—a Windows app that would do the trick which I could run against the filenames since the directory is on a Samba share. In seconds it was all over.

It makes me unhappy when something which should be blatantly easy from the command line ends up requiring a Windows application. Well, I'm sure it is simple. I'm pretty certain I even know how to do it. If so... I forgot...

Old age or Too Much Information

Friday, April 10, 2009

Virtual CD/DVD Disks From .iso Files

Regardless of popular opinion, Linux can often be so much more user friendly then Microsoft.

With one simple command I can access an .iso file as if it were an actual physical CD or DVD disc. Why must everything in the Windows world a) be such a pain in the butt, b) usually cost extra to implement a needed feature (virtually always free in GNU/Linux) and/or c) scare away the average user who just wants things to work without playing (or paying) the geek?

First let's examine the Linux version of adding virtual CD/DVD-Rom from an .iso file. Open a terminal session. Ready? Here goes:

sudo mount -o loop some_image.iso /mnt/img

Now was that so hard? Oh, and you can use any mount point you want: /media/lazy; /mnt/disc; etc. Don't have a mount point you like? No sweat. Just add one before you issue the command above, for example:

sudo mkdir /mnt/disc

or

sudo mkdir /media/image

You get the idea... Once your virtual CD/DVD is ready, navigate to the mount point with a gui file manager or cli and enjoy your virtual CD/DVD. Why burn a disc if you don't have to?

You can get similar results in Windows XP, but it's just simply not as quick, easy or user-friendly as Linux in my biased opinion.

Working with an .iso as a virtual CD/DVD in Windows XP


There are a multiple commercial tools available that will allow you to virtualize an .iso file into a CD/DVD drive, but free is good too. Microsoft offers a free (unsupported) application that will provide you with the functionality to add a virtual CD/DVD-Rom drive from an .iso file in Windows XP similar to what we did above with Linux--the biggest disadvantage is that only a user with administrator rights can utilize the virtual drive. Not so under Linux.

Download winxpvirtualcdcontrolpanel_21.exe from download.com or from Microsoft.

Log into Windows XP as the Administrator or as another user with admin rights.

Run the downloaded file to extract the files to a working directory.

Next, from the command line or the gui file manager, copy VCdRom.sys from your working directory into the %systemroot%\system32\drivers folder.

You can do this with the cli (command line interface, you know: the DOS window) by doing the following:
  1. Click Start → Click Run → Enter cmd → Click OK

  2. Enter copy %systemdrive%\Program Files\msvcd\VCdRom.sys %systemroot%\system32\drivers (all one line)

  3. Press Enter

  4. Enter exit to close the DOS window

Of course you can also copy this file with the gui (graphical user interface, you know Explorer) file manager.

Running VCdControlTool to create your virtual DVD/CD

  1. Open the winxpvirtualcdcontrolpanel_21 application from your working directory

  2. Click Driver Control

  3. Click Install Driver

  4. Navigate to VCdRom.sys or enter %systemroot%\system32\drivers\VCdRom.sys in the File name field

  5. Click Open

  6. Click Start

  7. Click OK

  8. In the Virtual CDRom Control Panel click Add Drive

  9. Click on the drive that appears in the window to select it

  10. Click Mount

  11. Navigate to the .iso that you wish to virtualize as a CD or DVD disc

  12. Select it in the File name field and click Open

  13. Click OK

  14. Click OK in the Virtual CDRom Control Panel window to close it.

You are now ready to use your virtual disc just as you would a physical CD or DVD.

Once you are finished with the virtual disc:
  1. Open the Virtual CDRom Control Panel application

  2. Click Eject

  3. You may now mount another .iso file,

    1. or to finish your session leaving the virtual CD/DVD drive assigned, simply click OK

    2. to end your session and delete the virtual CD/DVD-Rom drive, Click Remove Drive & OK
Final thoughts... Today, the Linux desktop works just as well or better then anything Microsoft is putting out. I find Linux on the desktop often outperforms the Windows desktop in resource management, stability and performance. It is unfortunate that it is not more widely utilized. Of course this article was not about the pros & cons of competing OS desktops. I just think it provides an example of how powerful and simple Linux can be (for free) when compared to the Microsoft offerings.

Note: Use the above information at your own risk. Your mileage may vary. winxpvirtualcdcontrolpanel_21.exe is a free, unsupported application supplied by Microsoft for Windows XP only. The above information is based on my usage of that application as of today only. Others may have more information about usage details and troubleshooting.

As to the Linux details, yeah, use as your own risk (blah blah blah), but don't be scared. It just plain works.

Wednesday, June 18, 2008

Ubuntu Upgrade & Software RAID

You never know what you are going to get when you do a distribution upgrade.

Somewhere along the way I "upgraded" my little fileserver from Ubuntu 6.06 LTS (Long Term Support) to 6.10 (NOT Long Term Support). Why? I do not know. Support for 6.06 LTS will end June 2011 but support for 6.10 ended April 2008!! Unfortunately, I only realized this yesterday. No wonder I hadn't seen any package updates for some time. :-(

Time to upgrade, NOW!

Ubuntu's latest is another LTS release, 8.04. So my big plan is go to somehow get from 6.10 to this latest LTS release. Supposedly you can do it if you upgrade a release at a time. Away we went using Method 2 here...

Changed my sources in /etc/apt/sources.list replacing all instances of edgy to feisty.

sudo apt-get update


sudo apt-get dist-upgrade

sudo apt-get -f install


sudo dpkg --configure -a


sudo telinit 6


It rebooted, so I thought I was probably safe.
sudo lsb_release -a showed me that I was indeed upgraded to 7.04. All was right with the world...

Not so.

My RAID5 & RAID1 devices were missing a drive! What happened?!

It turns out that upgrading turned two of my IDE drives into SCSI devices and left one as a regular IDE device. Bizarre. The missing RAID drives were the partitions from the one IDE device that was left. I used Webmin to simply add the appropriate partions from the IDE drive to the SCSI RAID devices and that was it. It worked without sending my data to /dev/null.

The RAID5 devices rebuilt and the RAID1 was back to mirroring with a spare. All was right with the world.

My question is, what's going to happen during my upgrade from 7.04 - 7.10 - 8.04? Will I be so lucky. I was pretty freaked out when my IDE drives "turned" into SCSI devices. Just weird, and why the heck did it leave one of the IDE drives as such instead of making it a SCSI device? I do not know...

Wednesday, April 30, 2008

Identify Your Hardware With Linux

I wanted to find out if the old mainboard I am using for my little file server supported USB 2.0 and not a measly 1.1--let's keep that USB drive (used to back up the server) flying along as fast as possible, eh?

Came across this thread which lead me to the answer. I could now get the needed information without shutting down the box, opening it up and hopefully finding the model number so I could google up the answers, etc. etc.

No GUI app need apply, I wanted a command line solution. Here are some options I found:

lspci -vv or sudo lspci -vv

But the really cool one is:

sudo lshw

That shows you just about everything you could want regarding your hardware. I found out what model mainboard I am running and the USB info I was looking for...

Thursday, June 14, 2007

Ubuntu Edgy Server Troubles

One thing leads to another but finally it all worked out (for now).

First, I found that my VIA C3 Linux Software RAID server (scroll down in this link for details) couldn't take a simple cp backup without taking a dive. Unreal.

I got a reasonable deal on a 500GB external drive. USB 2 of course. That was my first problem. The junk board didn't have USB 2 connections so I had to upgrade it with a two port USB 2 PCI card. Great.

My first attempt at backing up my /data & /home partitions with a simple tar command (no compression) ended in a kernel crash. Next I tried an arcane cp | tar type command (to maintain file permissions). I will have to see if I can find it again. Anyway, it ended the same way. What's going on here?

Time for some custom kernel action. I built a couple on my VMWare build server (basically the same OS sans the RAID setup, and the kernel source & build tools installed.) I have the VMWare build box on the AMD64 box--much faster kernel builds. It's very easy to do. Customize you configuration and use these instructions to build your packages. Nothing to it. I got rid of extemporaneous fluff that wasn't needed for my C3 box, configured it so that Reiserfs and RAID 1 & 5 were compiled into the kernel (as opposed to modules), and hoped that would do the trick. No dice.

I was even reduce to running simple cp -av commands for the back up, I mean really, what OS is going to choke on a copy command? Still no luck. It still broke.

Ok, one more shot with software and then we are trying something drastic. I grabbed the latest stable linux source from kernel.org and again compiled yet another kernel. Surely the bugs were gone and I would see success. Nope. It was apparent (and I had a hunch all along that this was the case) that the processor just could not deal with the load. Sure, there was enough memory on the board but it just wasn't going to happen. The C3 is just too weak.

Drastic Measures


I pulled my Windows 2000 drive out of the AMD64 box (with all my neato PCI cards in it: RME Hammerfall; NTSC/HDTV tuner card; etc.) and put my RAID disks into the case. I used a standard (none C3 specific) kernel to boot and everything was running smoothly--except no ethernet. Oh brother...

The kernel modules for the NIC was loaded but ifconfig showed nothing but the loopback. I was forced to track down the configs to make it work. You would think it would all be in /etc/network but not quite. I will spare you the details and get to the point: you make changes in two places--or perhaps one really (if you have the right NIC driver loaded). In my case I made changes to /etc/network/interfaces & /etc/iftab.

Here is what interfaces looks like (I have a static IP address for it, makes like easier on my network & it is a server--if you believe it or not):

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo eth1
iface lo inet loopback
# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
# The primary network interface
iface eth1 inet static
address 192.168.0.5
netmask 255.255.255.0
broadcast 192.168.0.255
network 192.168.0.0
gateway 192.168.0.1


The only real change I made here was replacing eth0 with eth1. Even without modifying the next file, it would come up after a lengthy wait while the system autoconfigured the NIC. The next file /etc/iftab could have remedied this issue without even touching the previous file I believe--you'll see why shortly:


# This file assigns persistent names to network interfaces. See iftab(5).
# eth0 mac 00:00:0d:33:50:83
eth1 mac 02:R2:D2:C3:P0:07


I could have just changed the MAC address of the NIC for eth0 and I'll bet everything would have come up just fine. Instead, in my case, eth0 disappears and eth1 takes over. No big deal. It comes up just as it should. I may go back and "fix" it for semantics I suppose but I doubt it since if it ain't broke, don't fix it.

Ok, so the network is now working, but I forgot to mention during all of the crashes when the drives were in the C3 box I was doing reiserfsck check on the md devices all the time--even on the external drive. I will have to say ReiserFS is pretty dang solid. When it did come up with errors reiserfsck --fix-fixable /dev/mdx would generally do the job. Unfortunately, since you cannot unmout your root filesystem that one was a bit of a trick. A couple of times though --fix-fixable didn't work and I had to use the more drastic --rebuild-tree (absolutely back up your partition before running this command). Since I was now able to actually get a good backup onto the external HDD without the OS dying, it was a good time for --rebuild-tree where needed. It was nice and fast, and it worked without any issues on the partition that needed it.

So now you would think all was right with the world. The server running smoothly on nice fast hardware--life is good. However, I had this nagging feeling that / needed to be checked--since it had been crashed several times. You can't unmount root when it's running of course, so an extensive test required outside intervention. Enter everyone's favorite LiveCD, Knoppix.

I wanted to get Knoppix to assemble /dev/md0 (my RAID1 root device) with mdadm but I was never able to get it to work for me. Instead I ran a simple reiserfsck check on each unmounted partition that was part of the array. It's RAID1 (mirroring) so each disk is simply a copy of the others. The first two disks came out fine, no corruptions. The third, hdg1 was not so fortunate. reiserfsck wanted a --rebuild-tree on that one. Uh, no thanks... since I had no idea what that would do to the other two drives when it was rebooted without Knoppix. Enter the aforementioned mdadm, an extremely useful & powerful tool for RAID administration even if it is not well documented (at least I should say, I didn't find everything on it that I was looking for even though "google is [my] friend.") I decided that the simplest fix would be to "fail " the drive with the corrupted partition, reformat it, and then put it back into the array. I don't know about you kids but this was what I came up with (via this article) and it worked perfectly well for me:

# Fail the corrupted partition
mdadm /dev/md0 --fail /dev/hdg1 --remove /dev/hdg1

# Reformat the partition
mkreiserfs /dev/hdg1

# Add the partition back into the RAID device
mdadm /dev/md0 --add /dev/hdg1

The OS knew right what to do and added hdg1 right back in as the spare drive for the RAID1 device (which was the initial configuration of this particular configuration--two drives mirroring with one spare).

Ok, so now I am confident that all my partitions are clean, even the external drive, and my RAID1 & 5 devices are working properly. What else could possibly go wrong now?

I really cannot say what change(s) I made that caused the following disaster but the recovery was really quite simple in the end--even if it did take almost all day to finally stumble upon it. Here's the list of things that went terribly wrong in no particular order:
  • Samba ceased to start automatically
  • Webmin ceased to start automatically or not at all.
  • /etc/mtab & mount would only display the root filesystem as being mounted (even though nothing had been changed in /etc/fstab). mount -a would not resolve the issue either, but even though they were not listed /home & /data were still available. Very, very strange. Totally disconcerting.
  • Swap would not automatically start.
I would manually start Webmin and proceeded to change various boot time options. One option that caused me terrible grief was the checkfs.sh and/or checkroot.sh options at boot time. Do yourself a favor and don't enable these in Webmin. The box would lock up hard and keep the root filesystem in a read-only state. This causes a world of grief because the OS needs writing capabilities. In this state you couldn't even manually start some of the services you wanted. Fortunately I found a command that would undo this particular disaster:

mount -w -n -o remount /

I've seen this before, but in the midst of my sorrows, I couldn't remember it. Once / was back in rw mode, I could then start Webmin again. Play around with boot time settings, and still have problems. Something was wrong with the init scripts. Something terribly wrong, and I hadn't a clue how to fix it.

I decided that I would try to find a package through aptitude search that would allow me to reset the init scripts to "factory default" since I had obviously blown mine up somehow. Wonderful tool aptitude, highly recommended. This is what I did:

sudo -s
apt-get update
apt-get upgrade

# After finding what I was looking for
# via aptitude search I issued the
# following command

aptitude remove initscripts

# Ugly messages follow about breaking
# things and uninstalling other important
# packages but I went ahead with the removal
# anyway (making note of the other packages
# that were getting whacked as well).
#
# Time to put everything back based on my
# notes of the
packages removed

aptitude install initscripts ubuntu-minimal system-services upstart-compat-sysv
reboot

Reboot... The moment of truth... And there it was! Everything, was back to normal. All the filesystems mounted--showing up in /etc/mtab & when the mount command was executed. Samba & Webmin started automatically. "No runs, no drips, no errors." "All was right with the world."

And there you have it. Many disasters and many (recovery) lessons learned. Using Knoppix to run reiserfsck on the root partition RAID1 drives was nice. I wish I could have figured out how to make it assemble the RAID device under Knoppix though. That would have been even better, and a necessity to checking a RAID5 device if your OS blows up completely.

Now, I have to find a permanent home for the drives (an the OS that lives on them). A box with good airflow & a CPU /MoBo /RAM with enough capacity to meet my seemingly simple needs. I'm not leaving them in the AMD64 box. I need to put that back together so we can use it as the big workstation with all the toys in it.

Well, when all is said and done, at least when I move the drives again I should be better prepared for some of the weirdness that may occur...