nvm, I figured it out after my whole day :) The BIOS was automatically updated and moved the OS drive down from the 1st boot drive to the last boot drive. sheesh, so simple! Thanks anyways!
On Thu, May 20, 2010 at 2:15 PM, Jeff Sadino jsadino.queens@gmail.comwrote:
Hello,
I have a GridEngine setup with 5 subnodes and two RAIDS attached. I backed up the OS drive - 120GB - to an external hard drive - 500GB - using ddrescue. The OS drive is partitioned as: sda1 has the OS and is about 7 GB sda2 has /var and is about 4 GB sda3 has swap and is about 1 GB
After backing up, there were 4KB of errors, but all at the end of the disk around 118GB. This used to be a partition back in the day, but I deleted it accidentally. I want to back up to this new larger disk b/c the original 120GB disk is discontinued. I boot from a live cd - SystemRescue CD - and run e2fsck -c -c -C 0 y on sda1 and sda2 on the backup drive, and it seems to finish fine. Then I replaced the OS drive with the backup drive, and it goes to boot, then Grub Loading Stage 1.5; Error 22.
Here's the important stuff from fstab: # This file is edited by fstab-sync - see 'man fstab-sync' for details LABEL=/1 / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 /dev/md0 /export ext3 defaults 0 0
none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 LABEL=/var /var ext3 defaults 1 2 LABEL=SWAP-sda3 swap swap defaults 0 0 /dev/sdb1 swap swap defaults 0 0 # The ram-backed filesystem for ganglia RRD graph databases. tmpfs /var/lib/ganglia/rrds tmpfs size=252709000,gid=nobody,uid=nobody,defaults 1 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
I boot up from the live cd, and then tell it to search for bootloaders on the drives, and it finds one, and it goes through, and then throws errors b/c it is mounting the OS /sda1 drive and then trying to run fsck on it. I tried setting the error-check values to 0 for /1 and /var, but it is still trying to error check it.
My blkid says that sda1, sda2, and sda3 all have different UUIDs. sdc1, sdd1, and md0 all have the same UUID. md0 is a RAID1 comprised of sdc1 and sdd1. sdc and sdd are identical drives.
This used to happen, and I would just restart a couple of times, and it would sneak on past the error eventually, but to no avail this time. Does anyone have any ideas? Thank you so much!
And thank you to the dozen people who offered advice on the best backup option. After reading all of the replies and the links, I think I will prob go with the rsync-backup suggestion.
Mahalo, Jeff