RecceDG
February 5th, 2015, 04:39 PM
I'm starting this thread to record my trials and tribulations with my main Linux box.
This machine is my household Samba server, housing the shared network drive that holds all our images, documents, videos, music etc. It houses the home Wiki site (that we use as a project planner). I also use it as a study station (Recoll and a ton of pdf textbooks is very handy) It hosts our Subsonic server for whole-house music playback, and I also use it as a Linux gaming machine, via Steam.
The machine itself is a Phenom II x6 1090T, with 8Gb of DDR2 RAM (it's an AM2+ motherboard) and a Radeon HD 7870 graphics card. It has 2 x 3Tb drives, 2 x 1 Tb drives, and a brand new 120 Gb SSD.
It had been running 14.04 LTS 32 bit, upgraded in place from Ubuntu 10 from when I first built the box in 2009. The upgrade from 12.04 to 14.04 went particularly poorly, and the machine was getting flakier and flakier with time. I bought the SSD specifically to hold a new, fresh install of the OS with a view to eliminating all the flakiness. And to be honest, I was planning on moving to Fedora and washing my hands of Ubuntu and a lot of the strange choices Canonical has been making lately.
Unfortunately, I need the AMD Catalyst drivers and I want GNOME as my desktop environment, and those don't play well on Fedora (or so I'm told). I'm also heavily dependent on Steam working (which prefers Ubuntu) and the other bits of my setup also are known to work on Ubuntu... so I guess I'm locked in for the moment.
Recently, the latest crazy has been that the machine would segfault 9 times out of 10 at boot if the SSD was plugged in - the problem occuring when the md drives are being assembled. I have my root partition as an md drive, my home partition as an md drive, and a third md drive is mounted as extra space in /home.
This AM, my hand was forced. I got up to find the machine hard locked, and it segfaulted on boot no matter if the SSD was plugged in or not. Happily, I had a 14.04 LTS 64 bit install DVD ready to go.
The first attempt at installing crashed with about 3/4 of the "copying files" process done. It attempted to file a bug report (it opened Mozilla, I logged into launchpad) but it never completed; it was stuck on a 10-second refresh loop that never ended.
The second attempt, I unchecked "download updates while installing" and this time it worked. It complained about the language package checksum not matching the DVD (and recommended burning the disk slower or moving the computer to a cooler environment) but otherwise it installed to competion. On reboot, I entered the BIOS and set the boot priority to the SSD, and the system booted pretty much immediately (SSDs are pretty cool)
Once logged in, I changed the display preferences to account for my portrait-mode second monitor, and then attempted to start mdadm. It wasn't installed, so I installed it, then ran "sudo mdadm --assemble --scan" and it found all 3 md drives. The /home drive and the /home/media/blah drives came right up; the / drive only came up on 1 drive.
I now suspect that either the physical drive that didn't come up is failing, or that something corrupted that partition.
My plan going forward is to:
1. Mount the md arrays in temporary mount points
2. Move the old user directory from the md version of /home to an olduser directory
3. Copy the /home directory from the SSD to the md version of /home
4. Edit /etc/fstab to mount the md /home as /home and the old / degraded array as /oldroot
5. Reboot.
That should get me all my data files back, set up my user with a clean home directory with no old dotfiles in it, and give me access to the old drive and old config files to help setting up the various servers easier.
Once I have the new system fully set up, I'm going to reformat the 2 x 1Tb drives as a single RAID 1 partition (like the 3Tb drives are) plus a little swap space. Long-term, I'm going to migrate all the drives to 3 x 6Tb drives in a RAID 5 setup.
My immediate issue is setting up the GNOME environment and getting rid of Unity. What is the current recommended process for that?
This machine is my household Samba server, housing the shared network drive that holds all our images, documents, videos, music etc. It houses the home Wiki site (that we use as a project planner). I also use it as a study station (Recoll and a ton of pdf textbooks is very handy) It hosts our Subsonic server for whole-house music playback, and I also use it as a Linux gaming machine, via Steam.
The machine itself is a Phenom II x6 1090T, with 8Gb of DDR2 RAM (it's an AM2+ motherboard) and a Radeon HD 7870 graphics card. It has 2 x 3Tb drives, 2 x 1 Tb drives, and a brand new 120 Gb SSD.
It had been running 14.04 LTS 32 bit, upgraded in place from Ubuntu 10 from when I first built the box in 2009. The upgrade from 12.04 to 14.04 went particularly poorly, and the machine was getting flakier and flakier with time. I bought the SSD specifically to hold a new, fresh install of the OS with a view to eliminating all the flakiness. And to be honest, I was planning on moving to Fedora and washing my hands of Ubuntu and a lot of the strange choices Canonical has been making lately.
Unfortunately, I need the AMD Catalyst drivers and I want GNOME as my desktop environment, and those don't play well on Fedora (or so I'm told). I'm also heavily dependent on Steam working (which prefers Ubuntu) and the other bits of my setup also are known to work on Ubuntu... so I guess I'm locked in for the moment.
Recently, the latest crazy has been that the machine would segfault 9 times out of 10 at boot if the SSD was plugged in - the problem occuring when the md drives are being assembled. I have my root partition as an md drive, my home partition as an md drive, and a third md drive is mounted as extra space in /home.
This AM, my hand was forced. I got up to find the machine hard locked, and it segfaulted on boot no matter if the SSD was plugged in or not. Happily, I had a 14.04 LTS 64 bit install DVD ready to go.
The first attempt at installing crashed with about 3/4 of the "copying files" process done. It attempted to file a bug report (it opened Mozilla, I logged into launchpad) but it never completed; it was stuck on a 10-second refresh loop that never ended.
The second attempt, I unchecked "download updates while installing" and this time it worked. It complained about the language package checksum not matching the DVD (and recommended burning the disk slower or moving the computer to a cooler environment) but otherwise it installed to competion. On reboot, I entered the BIOS and set the boot priority to the SSD, and the system booted pretty much immediately (SSDs are pretty cool)
Once logged in, I changed the display preferences to account for my portrait-mode second monitor, and then attempted to start mdadm. It wasn't installed, so I installed it, then ran "sudo mdadm --assemble --scan" and it found all 3 md drives. The /home drive and the /home/media/blah drives came right up; the / drive only came up on 1 drive.
I now suspect that either the physical drive that didn't come up is failing, or that something corrupted that partition.
My plan going forward is to:
1. Mount the md arrays in temporary mount points
2. Move the old user directory from the md version of /home to an olduser directory
3. Copy the /home directory from the SSD to the md version of /home
4. Edit /etc/fstab to mount the md /home as /home and the old / degraded array as /oldroot
5. Reboot.
That should get me all my data files back, set up my user with a clean home directory with no old dotfiles in it, and give me access to the old drive and old config files to help setting up the various servers easier.
Once I have the new system fully set up, I'm going to reformat the 2 x 1Tb drives as a single RAID 1 partition (like the 3Tb drives are) plus a little swap space. Long-term, I'm going to migrate all the drives to 3 x 6Tb drives in a RAID 5 setup.
My immediate issue is setting up the GNOME environment and getting rid of Unity. What is the current recommended process for that?