Wednesday, May 25, 2016

With BIOS update, Intel RAID gives "Non-Member Disk" error on RAID1+0 set

In prep to play the new DOOM 4 by installing a Windows SSD in my video editing machine, I ran a BIOS update on my Asus P9X79.  After the update, the Intel onboard C600 chipset RAID controller dropped two of the four RAID1+0 members that I had created from RAID members to "Non-Member" disks.  After researching the problem, it seemed that many people have had the issue with the Intel RAID:
 
Apparently, Intel RAID gets upset when the BIOS gets updated.  At a high level, what you do to resolve is 
A. Turn all members into Non-Raid Members
B. Re-create the RAID in the exact same order that it was created
- Don't Delete the RAID set, as that has caused data loss for some people
C. Usually, the partition table gets blown away when you recreate the RAID.  You then have to go find it again by running a program like TestDisk to find and rewrite any missing partitions
------------------
The Path I Took
Of course, when I ran TestDisk, I compounded the problem by choosing the wrong partition.  I basically got confused, as TestDisk allows you to select from a couple of choices:
1) Intel/PC partition
2) EFI GPT partition map
 
Now, my BIOS is UEFI and the drives all had GPT partition maps.  I thought that was the logical choice and I selected it.  It showed me two main drives:
- MS Data partition, size 200MB
- MS Data partition, size 2.7TB, the size of my RAID set
 
First, I wrote the 200MB partition table having the 200MB filesystem.  This was the wrong thing to do.  I got confused because my drives were GPT and because most of the people on the threads I had been reading were Windows.  It was only after spending Saturday and Sunday reading that I found a couple (out of the hundreds) of posts on people with Linux OSs that actually had the correct instructions to fix my issue.  
 
For my Linux Fedora 22 system, I actually needed to select "1) Intel/PC partition".  Before I did this, I decided to:
1) Pull off any data that I could using PhotoRec, a program that reads files block-by-block, written by the same guy who wrote TestDisk, Christophe Grenier.  I wrote that data to my 3GB SATA.  This took about ten hours.
- I ran through this exercise, but of course, the files that PhotoRec outputs are labeled F000001.txt, F000002.sh, F000003.gz and so on.  The names and directory structures are totally lost.  The content of the data files, however, is kept and I was able to find the video editing scripts that I had spent 100s of hours developing.  That was good, but it would be an enormous pain-in-the-A to dig through them and rename them all.
 
2) After pulling off the data, I was going to blow away the 200MB MS Partition, as creating this was a mistake.  I did this with some trepidation, obviously, as I didn't want to do any more harm.
 
Once those two things were done, I went back into TestDisk and selected "Intel/PC partition."  This time, I saw a Linux partition of the correct size, 2.7TB.  TestDisk gives you the option of viewing the directory structure.  When I did this I got a foreboding message:
“Can’t open filesystem. Filesystem seems damaged.”
 
Ugh.  I pressed on and wrote the partition table to disk.  Mounting the filesystem, I got a new error:
mount: wrong fs type, bad option, bad superblock on /dev/md126p1
 
Ugh.  Doing some research, I found this article on fixing bad superblocks, which entails finding a good one from the many that are sprinkled throughout an ext4 filesystem:
 
I found the backup superblocks by using mke2fs:
sudo mke2fs -n /dev/md126p1
 
mke2fs showed me a number of superblocks available.  I prayed they were corrupt.  Using e2fsck, I chose one of the superblocks, 32768, from the output of mke2fs: 
sudo e2fsck -f -b 32768 /dev/md126p1
 
When the program ran, it found a few errors.  In case there were many errors, I CTRL-C'd out of e2fsck and restarted the program by adding the "-y" switch to let it run unattended and accept all fixes with a "yes."  I let it run.  After I came back to the terminal, I found the screen full of the text output of the program, with thousands of sector id codes scrolling by.  I wasn't sure if this was bad or good..but I let it finish.  Afterward, I mounted the drive.  
 
The mount came back without error.  Good.  The moment of truth was when I ran an "ls" and saw my files and directories!  However, I wasn't out of the woods yet.  The proof would be if I was able to access them.  I played some music files, opened a few videos, started up a VM..they all worked!  YAHOO!!  I didn't lose my stuff!!  Even though I have pretty much everything backed up, I did not have my scripts backed up and I've spent 100s of hours on those.  Thank God I got them back!!
 
So..hooray for me!
:)
Now onto playing DOOM, the reason why I got into that mess in the first place!!

Reference

Saturday, February 14, 2015

Fedora 18 to Fedora 21 upgrade using FedUp

Moved from Fedora 18 to 21.  I gotta say..pretty smooth.

Read up here:
https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F
and read up on Common Bugs, as I hit the "Downloading failed: Didn't install any keysbug
http://fedoraproject.org/wiki/Common_F21_bugs

Oops, broken dependencies during FedUp, disabling RPM Fusion repos..

[sodo@monstrous 2014]$ sudo fedup --disablerepo rpmfusion-free --disablerepo rpmfusion-nonfree --disablerepo rpmfusion-nonfree-updates  --disablerepo rpmfusion-nonfree-updates-testing  --disablerepo rpmfusion-free-updates  --disablerepo rpmfusion-free-updates-testing --network 21
setting up repos...
getting boot images...
.treeinfo.signed                                                                                                                                             | 2.1 kB  00:00:00     
setting up update...
finding updates 100% [=============================================================================================================================================================]
WARNING: potential problems with upgrade
  audacious-plugins-freeworld-mms-3.3.4-1.fc18.x86_64 (no replacement) requires audacious-libs-3.3.4-2.fc18.x86_64 (replaced by audacious-libs-3.5.2-1.fc21.x86_64)
  gstreamer1-plugins-ugly-1.0.10-1.fc18.x86_64 (no replacement) requires libcdio-0.83-5.fc18.x86_64 (replaced by libcdio-0.92-3.fc21.x86_64)
  OpenEXR_Viewers-nonfree-1.0.2-10.fc18.x86_64 (no replacement) requires OpenEXR-libs-1.7.1-1.fc18.x86_64 (replaced by OpenEXR-libs-2.1.0-5.fc21.x86_64)
  OpenEXR_Viewers-nonfree-1.0.2-10.fc18.x86_64 (no replacement) requires ilmbase-1.0.3-4.fc18.x86_64 (replaced by ilmbase-2.1.0-3.fc21.x86_64)
  gstreamer-plugins-ugly-0.10.19-5.fc18.x86_64 (no replacement) requires libcdio-0.83-5.fc18.x86_64 (replaced by libcdio-0.92-3.fc21.x86_64)
  librtmp-2.4-0.2.20110811gitc58cfb3e.fc17.x86_64 (no replacement) requires gnutls-2.12.23-2.fc18.x86_64 (replaced by gnutls-3.3.12-1.fc21.x86_64)
  audacious-plugins-freeworld-ffaudio-3.3.4-1.fc18.x86_64 (no replacement) requires audacious-libs-3.3.4-2.fc18.x86_64 (replaced by audacious-libs-3.5.2-1.fc21.x86_64)
  vlc-core-2.0.9-1.fc18.x86_64 (no replacement) requires libgcrypt-1.5.3-1.fc18.x86_64 (replaced by libgcrypt-1.6.1-7.fc21.x86_64)
  librtmp-2.4-0.2.20110811gitc58cfb3e.fc17.x86_64 (no replacement) requires libgcrypt-1.5.3-1.fc18.x86_64 (replaced by libgcrypt-1.6.1-7.fc21.x86_64)
  mplayer-1.1-4.20121008svn.fc18.x86_64 (no replacement) requires libass-0.10.1-2.fc18.x86_64 (replaced by libass-0.12.0-1.fc21.x86_64)
  vlc-core-2.0.9-1.fc18.x86_64 (no replacement) requires libmatroska-1.3.0-3.fc18.x86_64 (replaced by libmatroska-1.4.2-1.fc21.x86_64)
  vlc-core-2.0.9-1.fc18.x86_64 (no replacement) requires gnutls-2.12.23-2.fc18.x86_64 (replaced by gnutls-3.3.12-1.fc21.x86_64)
  vcdimager-0.7.24-5.fc18.x86_64 (no replacement) requires libcdio-0.83-5.fc18.x86_64 (replaced by libcdio-0.92-3.fc21.x86_64)
  audacious-plugins-freeworld-aac-3.3.4-1.fc18.x86_64 (no replacement) requires audacious-libs-3.3.4-2.fc18.x86_64 (replaced by audacious-libs-3.5.2-1.fc21.x86_64)
  mjpegtools-gui-2.0.0-5.fc18.x86_64 (no replacement) requires SDL_gfx-2.0.22-3.fc18.x86_64 (replaced by SDL_gfx-2.0.25-2.fc21.x86_64)
  vcdimager-libs-0.7.24-5.fc18.x86_64 (no replacement) requires libcdio-0.83-5.fc18.x86_64 (replaced by libcdio-0.92-3.fc21.x86_64)
  vlc-core-2.0.9-1.fc18.x86_64 (no replacement) requires libebml-1.2.2-3.fc18.x86_64 (replaced by libebml-1.3.1-1.fc21.x86_64)
  mencoder-1.1-4.20121008svn.fc18.x86_64 (no replacement) requires libcdio-0.83-5.fc18.x86_64 (replaced by libcdio-0.92-3.fc21.x86_64)
  ffmpeg-libs-1.0.8-1.fc18_fozz.x86_64 (no replacement) requires gnutls-2.12.23-2.fc18.x86_64 (replaced by gnutls-3.3.12-1.fc21.x86_64)
  ffmpeg-libs-1.0.8-1.fc18_fozz.x86_64 (no replacement) requires libass-0.10.1-2.fc18.x86_64 (replaced by libass-0.12.0-1.fc21.x86_64)
  normalize-0.7.7-6.fc17.x86_64 (no replacement) requires 1:audiofile-0.2.7-4.fc18.x86_64 (replaced by 1:audiofile-0.3.6-4.fc21.x86_64)
  avidemux-libs-2.6.4-5.fc18.x86_64 (no replacement) requires libass-0.10.1-2.fc18.x86_64 (replaced by libass-0.12.0-1.fc21.x86_64)
  vlc-core-2.0.9-1.fc18.x86_64 (no replacement) requires libass-0.10.1-2.fc18.x86_64 (replaced by libass-0.12.0-1.fc21.x86_64)
  audacious-plugins-freeworld-mp3-3.3.4-1.fc18.x86_64 (no replacement) requires audacious-libs-3.3.4-2.fc18.x86_64 (replaced by audacious-libs-3.5.2-1.fc21.x86_64)
  mplayer-1.1-4.20121008svn.fc18.x86_64 (no replacement) requires libcdio-0.83-5.fc18.x86_64 (replaced by libcdio-0.92-3.fc21.x86_64)
  ffmpeg-libs-1.0.8-1.fc18_fozz.x86_64 (no replacement) requires libgcrypt-1.5.3-1.fc18.x86_64 (replaced by libgcrypt-1.6.1-7.fc21.x86_64)
  mencoder-1.1-4.20121008svn.fc18.x86_64 (no replacement) requires libass-0.10.1-2.fc18.x86_64 (replaced by libass-0.12.0-1.fc21.x86_64)
  gstreamer1-plugins-bad-freeworld-1.0.10-1.fc18.x86_64 (no replacement) requires gnutls-2.12.23-2.fc18.x86_64 (replaced by gnutls-3.3.12-1.fc21.x86_64)
verify local files 100% [==========================================================================================================================================================]
testing upgrade transaction
rpm transaction 100% [=============================================================================================================================================================]
rpm install 100% [=================================================================================================================================================================]
setting up system for upgrade
WARNING: problems were encountered during transaction test:
  broken dependencies
    librtmp-2.4-0.2.20110811gitc58cfb3e.fc17.x86_64 requires libgcrypt-1.5.3-1.fc18.x86_64, gnutls-2.12.23-2.fc18.x86_64
    vlc-core-2.0.9-1.fc18.x86_64 requires libass-0.10.1-2.fc18.x86_64, libgcrypt-1.5.3-1.fc18.x86_64, libebml-1.2.2-3.fc18.x86_64, gnutls-2.12.23-2.fc18.x86_64, libmatroska-1.3.0-3.fc18.x86_64
    audacious-plugins-freeworld-ffaudio-3.3.4-1.fc18.x86_64 requires audacious-libs-3.3.4-2.fc18.x86_64
    vcdimager-0.7.24-5.fc18.x86_64 requires libcdio-0.83-5.fc18.x86_64
    audacious-plugins-freeworld-aac-3.3.4-1.fc18.x86_64 requires audacious-libs-3.3.4-2.fc18.x86_64
    gstreamer-plugins-ugly-0.10.19-5.fc18.x86_64 requires libcdio-0.83-5.fc18.x86_64
    normalize-0.7.7-6.fc17.x86_64 requires audiofile-1:0.2.7-4.fc18.x86_64
    ffmpeg-libs-1.0.8-1.fc18_fozz.x86_64 requires libass-0.10.1-2.fc18.x86_64, libgcrypt-1.5.3-1.fc18.x86_64, gnutls-2.12.23-2.fc18.x86_64
    mjpegtools-gui-2.0.0-5.fc18.x86_64 requires SDL_gfx-2.0.22-3.fc18.x86_64
    vcdimager-libs-0.7.24-5.fc18.x86_64 requires libcdio-0.83-5.fc18.x86_64
    OpenEXR_Viewers-nonfree-1.0.2-10.fc18.x86_64 requires OpenEXR-libs-1.7.1-1.fc18.x86_64, ilmbase-1.0.3-4.fc18.x86_64
    audacious-plugins-freeworld-mp3-3.3.4-1.fc18.x86_64 requires audacious-libs-3.3.4-2.fc18.x86_64
    audacious-plugins-freeworld-mms-3.3.4-1.fc18.x86_64 requires audacious-libs-3.3.4-2.fc18.x86_64
    gstreamer1-plugins-bad-freeworld-1.0.10-1.fc18.x86_64 requires gnutls-2.12.23-2.fc18.x86_64
    avidemux-libs-2.6.4-5.fc18.x86_64 requires libass-0.10.1-2.fc18.x86_64
    gstreamer1-plugins-ugly-1.0.10-1.fc18.x86_64 requires libcdio-0.83-5.fc18.x86_64
    mplayer-1.1-4.20121008svn.fc18.x86_64 requires libass-0.10.1-2.fc18.x86_64, libcdio-0.83-5.fc18.x86_64
    mencoder-1.1-4.20121008svn.fc18.x86_64 requires libass-0.10.1-2.fc18.x86_64, libcdio-0.83-5.fc18.x86_64
Continue with the upgrade at your own risk.


Full list of packages without updates:
Packages without updates:
  a52dec-0.7.4-16.fc17.x86_64
  a52dec-devel-0.7.4-16.fc17.x86_64
  adobe-release-x86_64-1.0-1.noarch
  aic94xx-firmware-30-4.fc18.noarch
  automake14-1.4p6-23.fc18.noarch
  automake17-1.7.9-17.fc18.noarch
  btparser-0.25-1.fc18.x86_64
  celt-0.11.1-4.fc18.x86_64
  celt-devel-0.11.1-4.fc18.x86_64
  easymock2-2.5.2-7.fc18.noarch
  faac-1.28-4.fc17.x86_64
  faac-devel-1.28-4.fc17.x86_64
  firstboot-18.7-1.fc18.x86_64
  freetype-freeworld-2.4.10-4.fc18.x86_64
  google-chrome-stable-40.0.2214.111-1.x86_64
  google-earth-stable-7.1.2.2041-0.x86_64
  google-talkplugin-5.40.2.0-1.x86_64
  gstreamer-ffmpeg-0.10.13-10.fc18.x86_64
  gstreamer1-libav-1.0.10-1.fc18.x86_64
  jre-1.7.0_40-fcs.x86_64
  kernel-3.11.10-100.fc18.x86_64
  kernel-3.11.7-100.fc18.x86_64
  kernel-devel-3.11.10-100.fc18.x86_64
  kernel-devel-3.11.7-100.fc18.x86_64
  kernel-modules-extra-3.11.10-100.fc18.x86_64
  kernel-modules-extra-3.11.7-100.fc18.x86_64
  lame-3.99.5-1.fc18.x86_64
  lame-devel-3.99.5-1.fc18.x86_64
  lame-libs-3.99.5-1.fc18.x86_64
  libCg-3.1.0013-2.fc18.x86_64
  libdca-0.0.5-6.fc17.x86_64
  libdvbpsi-0.2.2-2.fc17.x86_64
  libdvbpsi-devel-0.2.2-2.fc17.x86_64
  libgssglue-0.4-1.fc18.x86_64
  libmad-0.15.1b-15.fc18.x86_64
  libmimic-1.0.4-5.fc17.x86_64
  libmms-0.6.2-2.fc18.x86_64
  libmpeg2-0.5.1-9.fc17.x86_64
  libmpg123-1.14.4-1.fc18.x86_64
  live555-0-0.38.2012.10.18.fc18.x86_64
  mac-libs-3.99-9.u4b5.fc17.x86_64
  mjpegtools-devel-2.0.0-5.fc18.x86_64
  mjpegtools-libs-2.0.0-5.fc18.x86_64
  mplayer-common-1.1-4.20121008svn.fc18.x86_64
  msttcorefonts-2.5-1.noarch
  nvidia-settings-319.32-1.fc18.x86_64
  nvidia-xconfig-319.32-1.fc18.x86_64
  opencore-amr-0.1.3-2.fc18.x86_64
  rpmfusion-free-release-18-3.noarch
  rpmfusion-nonfree-release-18-3.noarch
  twolame-libs-0.3.13-2.fc17.x86_64
  uade-2.13-3.fc17.x86_64
  vo-amrwbenc-0.1.2-1.fc18.x86_64
  x264-devel-0.128-2.20121118gitf6a8615.fc18.x86_64
  x264-libs-0.128-2.20121118gitf6a8615.fc18.x86_64
  xfce4-websearch-plugin-0.1.1-0.18.20070428svn2704.fc18.x86_64
  xmms-mp3-1.2.11-4.20071117cvs.fc17.x86_64
  xmms-uade-2.13-3.fc17.x86_64
  xmms-xmp-3.5.0-3.fc18.x86_64
  xmmsctrl-1.8-9.fc18.x86_64
  xvidcore-1.3.2-3.fc17.x86_64
  xvidcore-devel-1.3.2-3.fc17.x86_64
  y4mscaler-9.0-11.fc17.x86_64
  1:anaconda-yum-plugins-1.0-8.fc18.noarch
  1:faad2-2.7-2.fc17.x86_64
  1:faad2-devel-2.7-2.fc17.x86_64
  1:faad2-libs-2.7-2.fc17.x86_64
  1:xmms-faad2-2.7-2.fc17.x86_64

Delete some problem children before starting upgrade..
[sodo@monstrous ~]$ cat zapDepsProblemsExe.sh 
sudo yum remove librtmp-2.4-0.2.20110811gitc58cfb3e.fc17.x86_64 \
vlc-core-2.0.9-1.fc18.x86_64 \
audacious-plugins-freeworld-ffaudio-3.3.4-1.fc18.x86_64 \
vcdimager-0.7.24-5.fc18.x86_64 \
audacious-plugins-freeworld-aac-3.3.4-1.fc18.x86_64 \
gstreamer-plugins-ugly-0.10.19-5.fc18.x86_64 \
normalize-0.7.7-6.fc17.x86_64 \
ffmpeg-libs-1.0.8-1.fc18_fozz.x86_64 \
mjpegtools-gui-2.0.0-5.fc18.x86_64 \
vcdimager-libs-0.7.24-5.fc18.x86_64 \
OpenEXR_Viewers-nonfree-1.0.2-10.fc18.x86_64 \
audacious-plugins-freeworld-mp3-3.3.4-1.fc18.x86_64 \
audacious-plugins-freeworld-mms-3.3.4-1.fc18.x86_64 \
gstreamer1-plugins-bad-freeworld-1.0.10-1.fc18.x86_64 \
avidemux-libs-2.6.4-5.fc18.x86_64 \
gstreamer1-plugins-ugly-1.0.10-1.fc18.x86_64 \
mplayer-1.1-4.20121008svn.fc18.x86_64 \
mencoder-1.1-4.20121008svn.fc18.x86_64 


Let's give it a shot
..
..
..upgrade worked!  Took about 1/2 hour

Had a strange problem with my keyboard only working from an older USB port.  Weird.

And I had to reinstall some apps.
[sodo@monstrous ~]$ cat restOfProgs.sh 
sudo yum install  a52dec \
  a52dec-devel \
  adobe-release-x86_64 \
  automake* \
  btparser \
  faac \
  faac-devel \
  firstboot \
  freetype-freeworld \
  google-earth-stable \
  google-talkplugin \
  gstreamer-ffmpeg \
  gstreamer1-libav \
  lame \
  lame-devel \
  lame-libs \
  libCg \
  libdca \
  libdvbpsi \
  libdvbpsi-devel \
  libgssglue \
  libmad \
  libmimic \
  libmms \
  libmpeg2 \
  libmpg123 \
  live555 \
  mac-libs \
  mjpegtools-devel \
  mjpegtools-libs \
  mplayer \
  mplayer-common \
  msttcorefonts \
  opencore-amr \
  twolame-libs \
  uade \
  vo-amrwbenc \
  x264-devel \
  x264-libs \
  xmms-mp3 \
  xmms-uade \
  xmms-xmp \
  xmmsctrl \
  xvidcore \
  xvidcore-devel \
  y4mscaler \
  faad2 \
  faad2-devel \
  faad2-libs \
  xmms-faad2 
[sodo@monstrous ~]$ cat ffmpegDeps.sh 
yum install libcdio-paranoia-devel \ 
ocl-icd-devel \
opencl-headers \ 
soxr-devel \
x265-devel


Now rebuild FFmpeg from my old instructions here:
http://crazedmuleproductions.blogspot.com/2010/02/fedora-12-x86-64-cinelerra-install.html

Worked, but a little libx264 version mismatch, so let's link the older static object to the new one..
[sodo@monstrous x86_64]$ ffmpeg -i Downloads/StormPigs20141227.mp4 test.wmv
ffmpeg: error while loading shared libraries: libx264.so.128: cannot open shared object file: No such file or directory
[sodo@monstrous x86_64]$ sudo ln -s /usr/lib64/libx264.so /usr/lib64/libx264.so.128
[sudo] password for sodo: 
[sodo@monstrous x86_64]$ ll /usr/lib64/libx264*
lrwxrwxrwx 1 root root      17 Dec 22 10:51 /usr/lib64/libx26410b.so -> libx26410b.so.142
-rw-r--r-- 1 root root  885768 Dec 22 10:51 /usr/lib64/libx26410b.so.142
lrwxrwxrwx 1 root root      14 Dec 22 10:51 /usr/lib64/libx264.so -> libx264.so.142
lrwxrwxrwx 1 root root      21 Feb 14 18:55 /usr/lib64/libx264.so.128 -> /usr/lib64/libx264.so
-rw-r--r-- 1 root root 1034936 Dec 22 10:51 /usr/lib64/libx264.so.142

All good.  FFmpeg works.

Update some progs dependent upon FFmpeg:
[sodo@monstrous ~]$ cat ffmpegDeps.sh 
yum install libcdio-paranoia-devel \ 
ocl-icd-devel \
opencl-headers \ 
soxr-devel \
x265-devel \
libquicktime \
mencoder \
mjpegtools-lav \
mplayer \
vlc \
vlc-core \
vlc-devel \
vlc-extras \
vlc-plugin-jack \
x264* 

We'll hafta see how it goes from here, but no odd audio problems, which I usually get and video plays fine.  Maybe Linux is grown up!

Other issues
After F21 upgrade, vmware 7.0 player borked: /lib64/libgcrypt.so.11: version `GCRYPT_1.2' not found. Older ver here: http://bit.ly/1Arz3Z5

Cinelerra 4.6 HV on Fedora21 immediately segfaults.Biggest thing: QA & lock down to test on 1 distro..clearly state what distro is supported..OpenGL the cause, move to X11-XV.

Fedora 21 upgrade broke Cinelerra Monty: vdevicebuz.C: error: ‘memcpy’ was not declared in this scope, fix here: http://bit.ly/1ECEtA8

Lost my FFmpeg presets: http://bit.ly/1yHRoMp

Chrome v 40.0.2214.111 tabs hang using Fedora 21. Delete .default/chrome helped, also tried downgraded to v39 seems to fix. Not first time I've had issues with Linux Chrome.


'sodo

Friday, April 12, 2013

i7 3930K (LGA2011) build: Asus P9X79

I spent a good few weeks researching and reading up on my latest monster video editing box.  Though it was expensive, I decided to go for the i7 3930K chip, a pricey $539 on sale from NewEgg.  Listed below are the parts that I assembled for the box.  The mainboard and the chipset were my primary concerns, but the other parts were chosen because they conformed to my build specs and they were on sale or discounted in one way or another during one of NewEgg's Build sales.

The cost of the items weren't bad, but they certainly added up:










1 x ($-75.00) DISCOUNT FOR AUTOADD #76165
$-75.00

1 x ($-85.80) DISCOUNT FOR PROMOTION CODE
$-85.80

Subtotal:$1707.10
Tax:$120.06
Shipping and Handling:$7.99
Total Amount:$1835.15


Here's a pic of them fresh out of the shipping box:
Because I don't build too often, it took about a day to assemble the main board and the components in the above picture.  It took another 1/2 day to port my four drive RAID 1+0 set from my old video editing workstation to this one.  Of course, I had to create a new RAID set on the new box.  I will no longer be using the trusty 3Ware 9650SE RAID card, as the new mobo has both Intel and Marvell RAID chipsets on board.  The Marvell only supports two drives, so I used the Intel to connect up my four 1.5TB Western Digital Green drives.

As all my content (photos/docs/videos/music/virtual machines/etc) is on this redundant RAID set, I made sure to backup the ext4 filesystem that sits on top it with fsarchiver.  Secondly, I bought a 3TB drive as a utility drive to try out my fsarchive restores.  This is a good system, as it confirms my backup is valid:
1) unmount content filesystem (the filesystem that's on top of RAID)
2) backup content using fsarchiver to a system drive with enough space to hold the 1.4TB of content
3) as my livelihood depends on my content, test the fsarchiver restore process by restoring the archive to a third drive, a 3TB Seagate partitioned with GPT and formatted using ext4
4) when the restore is validated as good, copy the files from the restore over to my new RAID 1+0 set. 

I love the Corsair 400R case.  With the nice cable tunnels, I was able to keep the mainboard area pretty free of cables, though it doesn't look like it from the below pic.  You can see the pipes to the Corsair H100i in the center of the photo.





































I ran most of the cables through the tunnels.  You can see how many cables were hidden using these tunnels:





































I'm not a great cabler and I just wanted most of the cables out of the way.  Given that there are five 3.5" drives, one 2.5" SSD and a DVD player in the box, I think I did alright.

The real test was firing the box up for the first time.  I was rather shocked when it did come up, mainly for the worry that the memory wouldn't be compatible.  But it was.  Also, I had invested a great deal of time before the build in reading the 176-page manual and watching a bunch of build videos listed at the bottom of this post.  So the base build with a single SSD hard drive powered up successfully.  Hooray!

The next hurdle was installing a basic operating system, Fedora 18 64-bit on my single SSD in the machine.  Again, surprisingly, this worked without a hitch.  I had spent a good deal of time reading the FedoraProject's list of UEFI bugs and I was suspect of problems, but was very happy that I didn't encounter any.

The final hurdle was migrating my four drives from my old workstation to run a RAID 1+0 configuration on the new box using the ASUS's Intel RAID chipset.  Once I moved the drives over, I  configured the BIOS in the Asus P9X79 to run RAID.  I then created the RAID set and rebooted the box.  I then saw three main screens on bootup:
1) The Marvell RAID BIOS bootup screen:


















2) The Intel RAID BIOS bootup screen:


















3) The American Megatrends BIOS screen:


















The American Megatrends BIOS and ASUS's UEFI BIOS screens are completely configurable and nicely laid out.  I won't be using many of the options, but it is just a pleasure to have a system that is so well stocked, but boots up quickly.  I'd say it takes about 30 seconds to get from cold start to my initial Fedora 18 grub2 prompt.

I haven't overclocked the mobo yet, but according to what I've been reading and the fact that I have good chip cooling via the H100i, I should be able to push the i7 from 3.2 to at least 4.6Ghz.

Wattage Used for Typical Tasks
Here is a chart of the tasks running in Fedora 18 x86-64 and the wattage used








Gnome System Monitor graphic
On the top row, the CPU History chart, you can see that my H264 video encode took about 40% of the CPU.  You can see all twelve CPUs being used.  On the bottom row, the Network History, you can see my upload to Vimeo.  The upload of my 530MB file took about 150s at a peak upload rate of 40Mbps.  That 40Mbps upload is courtesy of FIOS.





























Next up: installing Windows 7 Professional so that I can do some baseline performance measurements.

ciao!
TAG

UPDATE 2013/11/23
I've been so busy at work for the last six months that I haven't had time to use the new box.  Turns out that I made a mistake in copying over my files to my new drive..I hadn't preserved the time/date stamp of all my files, normally accomplished with a "cp -Rp .."!  This means that I then can no longer tell when I edited any of my scripts, took a picture, etc, etc.  Bollucks!  So I had to grab the timestamps from my original drive and apply them via "touch".  The procedure looked something like this:

sudo find  -printf "%t %h/%f\n" > ~/temp.txt
awk '{print "touch -d \""$1,$2,$3,$4,$5"\"",$6}' temp.txt > fixDate.sh

temp.txt looked like this:
Thu Nov 22 12:37:26.0000000000 2012 ./sodo
Sat Jan 22 10:29:32.0000000000 2011 ./sodo/.netbeans
Sat Jan 22 10:29:32.0000000000 2011 ./sodo/.netbeans/.superId
Sat Jan 22 11:58:29.0000000000 2011 ./sodo/.netbeans/6.7

fixDate.sh looked like this:
#!/bin/bash -xv
/usr/bin/touch -d "Thu Nov 22 12:37:26.0000000000 2012" ./sodo
/usr/bin/touch -d "Sat Jan 22 10:29:32.0000000000 2011" ./sodo/.netbeans
/usr/bin/touch -d "Sat Jan 22 10:29:32.0000000000 2011" ./sodo/.netbeans/.superId
/usr/bin/touch -d "Sat Jan 22 11:58:29.0000000000 2011" ./sodo/.netbeans/6.

Then I plopped a #!/bin/bash at the top of the shell script, chmod a+x fixDate.sh, and off I went.  But the script worked, thankfully!  Unfortunately, I wasted about two hours dealing with this today.  Super drag!

A second problem I see is when I use "mv" to move files to my new RAID set, the mv command gives me:
mv: setting attribute ‘security.selinux’ for ‘security.selinux’: Operation not permitted

Haven't figured out why tho.  Argh.
*** end update ***


References
ASUS P9X79 Home Page: https://www.asus.com/Motherboards/P9X79_DELUXE/
Manuals/Qualified Vendor Lists/Firmware Updates: http://usa.asus.com/Motherboards/Intel_Socket_2011/P9X79_DELUXE/#download

JJ of ASUS Republic of Gamers (asusrog) was immeasurably helpful in the builds.  In fact, I probably wouldn't have bought the board if I hadn't seen these videos.  Here are the core videos that helped me:
X79 Overview, Part I: http://www.youtube.com/watch?v=qGgQG3ANtaA
X79 Overview, Part II: http://www.youtube.com/watch?v=iE-YJafM65k
P9X79 Deluxe Hands-On Review: http://www.youtube.com/watch?v=xBPgv8aiL0Y
Build, Part I: http://www.youtube.com/watch?v=j9aY1HGYIyM
Build, Part II: http://www.youtube.com/watch?v=W8jogtOzw6Y

Overclocking on Sandy Bridge
Auto Overclocking: http://www.youtube.com/watch?v=Ct6tQaEsWYY
Part I: http://www.youtube.com/watch?v=Kx2z07sFM2I
Part II: http://www.youtube.com/watch?v=seVPIR06ZY4
Advanced Overclocking: http://www.youtube.com/watch?v=CZfOEs5n0jo

Non-JJ vid on overclocking: http://www.youtube.com/watch?v=8qz8olA8bRM

RAM Cache/SSD Cache
How to Setup a RAM Cache on a P7X79: http://www.youtube.com/watch?v=qGrqMllHVVY
RamCache/Ramdisk: http://www.youtube.com/watch?v=5cqfhZvyE80
SSD Caching: http://www.youtube.com/watch?v=uhCGo0LWaTY
SSD Caching (short version): http://www.youtube.com/watch?v=hvfiRA6hDhE


Cable Management
http://www.youtube.com/watch?v=5xKIiAu4rio

Sunday, March 17, 2013

backing up my systems: it ain't my day (or month)

OK.  I've been in three weeks of hardware hell, mainly due to the fact that I wanted to get my backups for all my machines (a MacBook Pro, my main Linux video editing workstation and an older Windows Vista digital audio workstation (DAW)) properly backed up.  I detailed my strategy for this in my last post.  This post is more of a rant than anything else, so please excuse the lack of any real mentorship on problem solving, except maybe "Google is Your Friend."

Issue #1: Drobo runs out of space
The Drobo has been a fine unit for me.  But as time goes on, you acquire more media and your available space runs out.  You'd think it would be a simple matter of buying a new disk, putting it in the Drobo and letting the BeyondRAID rebuild it's array.  Well, the first drive I bought, a Western Digital Green 1TB, died after the first rebuild.  That never happened to me before, where a drive failed out-of-the-box for me.  Never having that problem before, I didn't truly believe it was dead.

With my non-belief firmly in place, I tried to use the drive in different capacities.  So as a test, I formatted the disk using my Thermaltake BlacX connected to my Mac.  I was able to copy files over to it (though I didn't copy gigs and gigs worth as a true test).  But when I put the unit back in the Drobo, the Drobo gave an immediate "red" light for that drive bay, indicating the drive was bad.  I switched drives in the Drobo unit around, because I thought it could have been a faulty drive bay.  

Then, I had the bright idea to move the data off my 2TB system drive of my main Linux machine to the new Western Digital, put the 2TB in the Drobo and use the new 1TB (which I really thought was a good, error-free drive) as my Linux system drive. So still thinking that the 1TB drive was good, I would have to do some fancy footwork in order to make this possible as the system drive was a logical volume.  This entailed a week of work to figure out how to shrink a logical volume in order to fit the used space of the 2TB drive (which was less than a terabyte) onto the 1TB.

I learned a lot from that experience, to be detailed in a later post.  Suffice it to say that in the end, the 1TB was truly dead and I ended up getting a new 1TB (a Western Digital Black) from BestBuy and that solved my Drobo storage issue.  Kudos to BestBuy, as they were able to give me the Black at the same price as the Green for my trouble.

Issue #2: Mac Time Machine "the identity of this backup disk has changed" (Sparsebundle Problem)
This was an odd one.  After installing the new disk in the Drobo, Time Machine started showing the error "the identity of this backup disk has changed".  From the below post:

I executed the "chflags" command listed.  This ran for about four hours.  After, I tried to execute the "hdutil" command listed, but the Mac said it had already ran the command.  So testing the result of the chflags command, I shutdown and restarted the Drobo.  When Time Machine started backing up, it no longer gave me the error.  Hooray.  Another one down.

Issue #3: Windows Vista DAW crashes
So after a week spent on #1 and #2, I was ready to start work on a new musical project with some friends.  Firing up my old Dell 400SC running Windows Vista (OK, OK..I know I need to upgrade Win7, but I've got a recording session coming up soon and didn't want to change OS's yet), I was presented with this error:
c\windows\system32\config\system corrupt

Oh, wonderful.  So I popped in the Vista Ultimate DVD and selected "Repair".  After it ran, the system rebooted and I was pleasantly surprised to find that this fixed the problem and that I was able to get back into the system.

Getting back into the system, I reasoned that if the drive was going bad, I'd better make a backup.  So I ponied up $40 for Drobo's PC Backup product, the ugly step-brother of the seemless Drobo integration with Mac Time Machine.  Assuming the PC product worked the same way the Mac product did, I selected the defaults.  Well, the defaults do NOT backup the entire drive.  Only your user data.  My bad for not reading the fine print, but I believe that a Drobo product should be consistent between systems and the default should be to backup your entire drive with all system data included, as long as you have the space on your Drobo.  But that's just me.

The missing data would be crucial for what happened next.

Issue #4: Windows Vista DAW crashes again
After taking a two day hiatus from my backup shenanigans, I fired up the DAW again.  And guess what..a new error appears:
\Windows\system32\winload.exe is missing or corrupt (status 0xc000000f)

Oh great.  Going back to my ritual, I loaded in the Vista Ultimate DVD and selected "Repair".  However, after the reboot, no go..still the same "missing or corrupt" error.  I tried a number of times doing the repair, as the Vista repair process would show slightly different screens every time it booted and recognized the system.  This gave me false hope that the DVD was actually repairing something correctly.  Also, the frustrating part of this process that for whatever reason, the DVD would take 10 minutes to load on my Dell.  I'm not sure what the problem was there.  So I chewed up a few hours doing this multiple times.  

Finally, after reading some Google posts by people with the same issue, I decided to run "chkdsk /r" from the command line, rather than relying on the non-informative Windows Vista screen to run some unknown fix command.  I had to specifically boot into the System Recovery Options screen as shown in the below post:

Once I was there, I selected "Command Prompt" and typed in good ol' "chkdsk /r", the "repair" option to chkdsk.  This time, I was rewarded with an actual status screen that told me "bad clusters found", Windows was marking the clusters as bad and was moving the files located on those clusters to good sectors on the disk.  (Sectors and cluster primer here: http://t.co/DLFjrXAp5C).  This process took about three hours, unlike the half-hearted effort that Windows Vista attempted.  I wonder why Vista did not default to doing a real "chkdsk /r".  That doesn't help anyone who has a failing disk.  Bad default!

After the bad cluster identification and repair, I was really glad to see Vista boot up properly!  But since there were so many bad clusters, I had to make a full backup or clone of that drive but quick!  For this, I popped in an unused 500GB SATA I had lying around.  I repartitioned and formatted this drive.  It had been a second Vista system disk and one point, so I knew the drive's main partition was marked as bootable.  So I was good to go there.  I then dragged all the files from my C: onto the new E: (my DVD being the D:).  However, on bootup, Vista showed an error:
"System volume on disk is corrupt"

I suspected this was a problem with the NTFS boot files on the 500GB drive as they had links from the partition map from the old 256GB drive that was failing.  Luckily, when I ran Vista repair, Vista was able to fix this issue and the system started properly.

Issue #5: Windows Vista continually keeps "preparing your desktop"
After the system came up, I made sure all my applications (Reaper, Drobo PC Backup, etc) were working properly.  Unfortunately, they were not, as Vista continually kept giving me the message "Preparing Your Desktop" when I logged into my profile.  I tried a number of things from Google, but those suggestions did not work.  I didn't have any critical data in the old profile, so I figured I'd bit the bullet and create a new profile.  After doing this, the message disappeared and I was able to save my desktop settings and application preferences properly.

In Sum
Wow.  So this has been three weeks of hell.  I "think" I am back to steady state with my systems.  I was able to reset Drobo PC Backup to a full system backup of my Vista DAW to the Drobo.  The Drobo is backing up the Mac just fine and CrashPlan is encrypting my main Linux box backup to the Cloud.

Maybe now I can go outside and get some sun?
TAG

Saturday, March 09, 2013

protecting your data, locally and globally

I've spent a number of years trying various backup methods for my Linux box.  I think I finally have a pretty good one down.  The main idea is to setup my system in order to make backup and restore easier. This setup involves two components:
- a data source: my documents, videos, audio files and pictures are stored locally on a redundant  hardware RAID5 set
- the separation of system and data partitions on different physical devices (hard drives)

Backup Strategy
My actual backup strategy comes in three parts:
- an archive solution: fsarchiver to backup the system and data partitions
- network backup: a network backup device such as a NAS or in my case, a Drobo
- global backup storage solution: unlimited CrashPlan account

This backup strategy has been working well, though not without hiccups along the way.  It protects my important data by providing redundancy at multiple levels.  At a high level, here is how this is implemented:
- disk redundancy via RAID5 set
- local redundancy via network addressable storage
- global redundancy via CrashPlan if my house is destroyed

More specifically:
- my Linux system drive, Fedora 17, is one physical SATA drive
- my data drive is a hardware RAID5 unit using a 3Ware 9650SE with four physical SATA drives
- when I install a new OS, I use symbolic links (screen cap) in my user's home directory to point to my data, explained below

The bottom line is that no single backup method should be your entire backup strategy.  If you only have two of these methods implemented, you're better off than most people.

System Setup
Symbolic links are the key to segment the system partitions from your data partitions.  Segmenting is important because it separates your system from your data.  With this separation, it is much easier (from a Linux perspective), to upgrade and try different versions of Linux on your system drive, while your data drive stays essentially untouched and less prone to upgrade or experimentation tragedies.  Welcome to Linux!

Technically, here is how segmentation is implemented.  On my system drive, I mount my data partition.  In this example, I'm using /mnt as the mount point for my ext4 data partition:
[sodo@computer ~]$ cat /etc/fstab
/dev/mapper/vg_computer-lv_root /                    ext4    defaults        1 1
/dev/mapper/vg_computer-lv_home /home                ext4    defaults        1 2
/dev/mapper/vg_computer-lv_swap swap                 swap    defaults        0 0
/dev/mapper/vg_ogre-lv_root /mnt                     ext4    defaults        0 0

I have my content folders on the data partition that I will symbolically link from my system drive:
[sodo@computer mnt]$ ls -ltr /mnt
total 36
drwxr-xr-x. 16 sodo sodo 4096 Dec 21 19:04 MusicLibrary
drwxrwxr-x.  9 sodo sodo 4096 Jan 12 12:07 videos
drwxr-xr-x.  8 sodo sodo 4096 Feb  1 10:57 doc
drwxrwxr-x.  8 sodo sodo 4096 Mar  2 09:26 pictures

I then create symbolic links from my user's home directory to the equivalent directories that I've setup on my data partition:
[sodo@computer ~]$ ls -l | grep '^l'
lrwxrwxrwx.  1 sodo sodo    8 Oct 23  2011 Documents -> /mnt/doc
lrwxrwxrwx.  1 sodo sodo   18 May 30  2011 Music -> /mnt/MusicLibrary/
lrwxrwxrwx.  1 sodo sodo   14 Sep  2  2011 Pictures -> /mnt/pictures/
lrwxrwxrwx.  1 sodo sodo   12 May 28  2011 videos -> /mnt/videos/

With the symbolic links in place, I've made the link from my system to my data.

The Archive-Backup Process
I am going to use the terms "archive" and "backup" synonymously.  The overview is that I'll show how I back up my data partition using fsarchiver and then I'll copy those backups to both my local network and global storage solutions.  FSarchiver is a bit different than regular backup systems in that it archives entire filesystems only.  It is not a file-based backup method.  So when you go to save or restore a filesystem, you specify a filesystem to backup and have limited ability to exclude (but not include) directories or files with the "exclude" switch only (as of 5/2016).

Below, I show the archive process for the data partition.  Feel free to extrapolate the information herein to do the same for your system partition.

The Core Archive Process
1) check the used space on the source partition to be archived, as well as the available space on the destination/target for the backup (fill in missing info).  From the below example:
a. source filesystem (the data partition): vg_ogre-lv_root
b. destination partition (for backup storage): vg_computer-lv_home
[sodo@computer ~]$ df -H
Filesystem                       Size  Used Avail Use% Mounted on
/dev/sda1                        508M   80M  403M  17% /boot
devtmpfs                         5.3G     0  5.3G   0% /dev
/dev/mapper/vg_computer-lv_root   53G   15G   36G  30% /
/dev/mapper/vg_computer-lv_home  2.0T   .2T  1.8T  67% /home
/dev/mapper/vg_ogre-lv_root      4.5T  1.4T  2.9T  32% /mnt

2) verify available space on the destination filesystem
The source partition is using 1.4TB on vg_ogre-lv_root and I have 1.8TB available on the destination for the backup, lv_home.  So..good to go.

3) if there is enough space on the target filesystem, prepare to run fsarchiver and unmount the data partition.
In order to keep the filesystem from being updated during the archive process, fsarchiver asks to unmount the target filesystem before making the backup.  Like so:
[sodo@computer ~]$ sudo umount /mnt/

The nice thing about the split system-data partition setup is that it is unnecessary to load a Live CD in order to backup the data partition.  Normally, one has to boot with a LiveCD in order to backup the system partition.

4) Once the filesystem is unmounted, run fsarchiver.  As one of the destinations for the backup is the cloud, use the -c option to encrypt with a password:
[sodo@computer ~]$ sudo fsarchiver -j8 -c [password] -o savefs ~/f17backup/backup_lv_root.fsa /dev/mapper/vg_ogre-lv_root

The archive of my 1.2TB drive took five hours on my eight-core, 1.6Ghz Dell SC1430.
[sodo@computer ~]$ ll ~/backup/backup_lv_root.fsa 
-rw-r--r--. 1 root root 1186229328445 Mar  5 08:32 /home/sodo/backup/backup_lv_root.fsa

Copying the file to network-based storage
I have a 2.5TB CIFS (Windows share) created on my Drobo.  On my Linux box:
1) I mount the Drobo filesystem:
[sodo@computer ~]$ sudo mount -t cifs //drobo/Linux /mnt/drobo -o credentials=/home/sodo/smb.credentials

2) Copy the archive to it:
[sodo@computer ~]$ sudo cp -rp ~/f17backup/ /mnt/drobo/

Copying the file over my home network took about 16 hours.

3) Review the archive info (the -c switch allows you to enter a password for the archive):
[sodo@computer ~]$ fsarchiver -c - archinfo /mnt/drobo/f17backup/backup_vg_ogre-lv_root.fsa
Enter password: 
====================== archive information ======================
Archive type: filesystems
Filesystems count: 1
Archive id: 5131fa94
Archive file format: FsArCh_002
Archive created with: 0.6.15
Archive creation date: 2013-03-05_01-20-04
Archive label:
Minimum fsarchiver version: 0.6.4.0
Compression level: 3 (gzip level 6)
Encryption algorithm: blowfish

===================== filesystem information ====================
Filesystem id in archive: 0
Filesystem format: ext4
Filesystem label:
Filesystem uuid: 3ffe7328-8f96-4028-bd79-5f644a030fc2
Original device: /dev/mapper/vg_ogre-lv_root
Original filesystem size: 4.02 TB (4416677830656 bytes)
Space used in filesystem: 1.22 TB (1338969956352 bytes)


A Word About the Drobo
The Drobo has been one of the easiest storage and backup solutions that I've ever used.  It integrates seemlessly with Time Machine for my MacBook and I've created a Windows share on the device in order to copy my Linux archive.

Over the past few years, I've expanded the drives within it about three times now.  I went from four 500GB drives, to four 1TB drives and one 500GB to my configuration as it is today, five 1TB drives.  The drive upgrades were easy, though time consuming.  I removed each of the older drives one at a time and replaced them with the larger drives.  Each time a drive was upgraded, the Drobo would automatically and non-destructively rebuild it's storage protection.  The Drobo's storage protection is called BeyondRAID, Drobo's own custom algorithm on top of RAID.

The integration with Mac is seemless; however, the Windows/CIFS file share can be a bit wonky, as the share has a tendency to become unavailable for whatever reason.  The resolution is to shutdown and restart the Drobo and that seems to fix the problem.

Cloud-Based Storage
A last layer of protection above and beyond the local and network copy of my data is to copy the encrypted archive to a cloud-based solution.  The purpose is to protect my data in case of a natural disaster that destroys all my local storage media.  With the increasing amount of natural and man-made disasters happening these days, I've recently invested in a data protection plan with www.crashplan.com.  I got an unlimited plan to store my 1.2TB of data to the cloud.  Most of that data is audio, video and image files.

After tweaking the CrashPlan app to pump more data through my local and wide area network (from 1280KB and 2560KB, respectively, to about 6400KB for both), it took about two weeks to upload this amount of data to CrashPlan's cloud!

In sum, if you have a lot of data, all these procedures take time.  From backing up, local network copy and then cloud copy.  If you're using Linux, you probably have the stomach for all this.  In the end, though, you'll have a backup solution that is pretty solid and relatively easy to implement unlike custom scripted solutions.

Love to hear any comments on how you backup your systems.

ciao!
TAG

References
http://crazedmuleproductions.blogspot.com/2010/02/fsarchiver-good-backup-for-ext4.html
http://www.drobo.com/how-it-works/beyond-raid.php
http://support.crashplan.com/doku.php/recipe/stop_and_start_engine

Here are some of my earlier articles on fsarchiver and a review of the Drobo.

Feel free to drop me a line or ask me a question.