LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 04-22-2016, 12:00 PM   #1
ThatGuywiththeComputer
LQ Newbie
 
Registered: Apr 2016
Posts: 10

Rep: Reputation: Disabled
Cannot boot after cloning system


I am relatively new to anything beyond user level and basic package management in linux so hopefully this will be an easy answer.

I was recently tasked with moving a RedHat 6.7 instance to a new drive. the original system is a "snowflake" so a reinstall and reconfigure was out of the question. the system is being moved from a raid 0 array to a solid state drive.

Here is what I have done so far and where I stand now:
1) created identical partitions on the new solid state drive
2) rsynced all of the data to the drive while running on a live cd
3) swapped out the hard drives
4) updated the drive info and UUIDs in device.map, grub.conf, and etc/fstab
5) booted to a live cd again chrooted to the system partition
6) ran grub-install

Here is my problem: when I boot the computer I see my grub options, it seems to load the kernel (I see all the messages about starting the different daemons / services)
then I go one to a screen with just a small spinning circle in the upper left corner of the screen. the circle will spin for about 10 minutes and then the screen will go black. If I press the power button i see all the normal shutdown messages and it powers off gracefully.

So far i haven't noticed anything obvious in /var/log/messages or dmesg

What am I missing?


edit: digging into boot.log has shown my that HAL failed to start for some reason. I will try digging in there.

Advice is still appreciated

Last edited by ThatGuywiththeComputer; 04-22-2016 at 12:01 PM. Reason: new information
 
Old 04-22-2016, 05:07 PM   #2
jefro
Moderator
 
Registered: Mar 2008
Posts: 15,372

Rep: Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198
This is why I hate clones. Not sure I'm a fan of your clone method either.

Do any virtual terminals work ctrl-alt-Fx?
 
Old 04-25-2016, 09:51 AM   #3
ThatGuywiththeComputer
LQ Newbie
 
Registered: Apr 2016
Posts: 10

Original Poster
Rep: Reputation: Disabled
no, none of the virtual terminals work. just the small spinning black wheel in the upper left hand corner until i press the power button.
 
Old 04-25-2016, 03:26 PM   #4
jefro
Moderator
 
Registered: Mar 2008
Posts: 15,372

Rep: Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198Reputation: 2198
Not sure where to go. We haven't proven much here. Is clone bad or is config bad?

Can you start in single user?

What does everything look like on live cd boot? All data there? Check filesystem?

I get the feeling some issue with the old raid is still there.

When I attempt this stuff I usually play with an image of the system within virtual machines. Seems to make peeking and playing more safe.
 
Old 04-25-2016, 11:27 PM   #5
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 2,318
Blog Entries: 1

Rep: Reputation: 447Reputation: 447Reputation: 447Reputation: 447Reputation: 447
# rsync -aRXHv ./* /mnt/partition/

If the system isn't the currently running system. Double check /etc/fstab and grub.cfg. The UUID is partition specific. And is more reliable IMO that /dev/ or label names.

# blkid /dev/sda2
(or whatever applies)

And for grub... vmlinuz root=UUID=########-####-####-####-############... versus root=/dev/????. When you create a new partition, it get's a different UUID. I have an early UEFI machine that only boots usb with dos partitions, not the newer GPT.
 
Old 04-26-2016, 09:31 AM   #6
ThatGuywiththeComputer
LQ Newbie
 
Registered: Apr 2016
Posts: 10

Original Poster
Rep: Reputation: Disabled
I appear to have solved my own problem. but first a few things I learned:

- the small black circle i was seeing in the upper left hand corner should have been the mouse cursor but there was no movement or response from keyboard (I am assuming) because the HAL daemon was failing to start.

- when I add the emergency flag to the kernel options in grub i could get to command line and interact with the local file system

- it is running grub version 0.97 (which some sites indicate does not play well with ext4 partitions i believe it was because of 128 vs 256 inode size). for this reason I chose to restart fresh with the clone, creating the partitions from within a redhat 6 installation disk.

on my initial attempt I had used a CentOS 7 live CD as my working environment. after recreating the partition from the RedHat 6.5 disk the partitions show as ext4 (version 1) in the disk utility.

I rsynced the data from both the boot and system partitions to the new solid state
mounted the new partitions and updated device.map, grub.conf, and etc/fstab
powered down and replaced the drive in the system
powered the machine on
disabled the raid controller on the system
full reboot brought me to a normal login prompt.
add discard option to etc/fstab (because solid state)


things i do not know for sure:

was it the inode size of the partitions causing the problem or was it a transfer error?
were there any issues downstream of the failed HAL after 5the first attempt?
how the hell did i forget to pour a glass of whiskey when i finished?
 
Old 04-26-2016, 10:01 AM   #7
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 14,832

Rep: Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820
Quote:
Originally Posted by ThatGuywiththeComputer View Post
was it the inode size of the partitions causing the problem or was it a transfer error?
were there any issues downstream of the failed HAL after 5the first attempt?
how the hell did i forget to pour a glass of whiskey when i finished?
i) the inode size in all likelihood. grub legacy needed a patch to handle that, but e2fsprogs also needed to be at an appropriate level.
ii) probably not
iii) a good Islay I trust ...

You cloning procedure looks fine as a general methodology.
 
Old 04-26-2016, 10:34 AM   #8
ThatGuywiththeComputer
LQ Newbie
 
Registered: Apr 2016
Posts: 10

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by syg00 View Post
iii) a good Islay I trust ...
My latest affair has been a different flavor.

https://glenmorangie.com/us/glenmorangie-quinta-ruban
 
Old 04-26-2016, 12:46 PM   #9
ThatGuywiththeComputer
LQ Newbie
 
Registered: Apr 2016
Posts: 10

Original Poster
Rep: Reputation: Disabled
Apparently I am not done

I powered down the system to take care of some other issues and now the system will not boot again. the root file system seems to be mounting as read only now. I have made no changes since my last successful boot so I am perplexed.

Edit: curiouser and curiouser. after sorting through the boot log it said there were errors in fstab on each line with partition information. i removed the discard option and was able to boot again. not sure how i was able to get through two boot cycles with no problem only to be locked down later.


should I be using any special options in fstab besides defaults? I'm not quite sure what just happened.

Last edited by ThatGuywiththeComputer; 04-26-2016 at 01:51 PM.
 
Old 04-26-2016, 07:32 PM   #10
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 14,832

Rep: Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820
Given you are running grub classic and the old small inodes, I would doubt discard is supported. Would expect it to be flagged as an unknown option though.
Is fsck running automatically at boot ?. Let's see fstab and relevant messages.
 
Old 04-27-2016, 08:58 AM   #11
ThatGuywiththeComputer
LQ Newbie
 
Registered: Apr 2016
Posts: 10

Original Poster
Rep: Reputation: Disabled
fsck is running automatically at boot on both the boot and root partitions. I have removed the discard option and added noatime, at this point i have put it through about 20 boot cycles with no new issues. it is probably for the best since this SSD has been added to the blacklist for TRIM support (Samsung Evo 850 series). the drive may die faster, but I am comfortable with It's current state. Thank you all for your help and insights.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
How to protect system from cloning? dynamicpointer Linux - Security 16 09-11-2014 01:34 AM
Just Finished Cloning my Dual Boot Setup, but Linux OS won't boot kuyalfinator Linux - Virtualization and Cloud 8 03-08-2011 12:38 AM
Cloning the Linux System pras123 Linux - Server 6 06-03-2008 12:17 PM
Cloning Linux System from PC->PC ALInux Linux - General 4 07-26-2006 06:09 PM
cloning both partitions, dual boot system, master boot record, logical volume manager saranga2000 Linux - Hardware 3 01-10-2005 12:04 PM


All times are GMT -5. The time now is 10:39 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration