Fedora :: After Cloning To Bigger Hdd / Can Boot Only Over Super Grub Disk CD
Mar 21, 2011
I cloned F14 with Clonezilla from 80GB to 320GB hdd(both sata disks), and then resized the partitions with GParted.But I can not boot into fedora on the new/bigger disk, it stops and the display writes "Loading stage 1.5" if I remember corectly,I tried to fix it with the live cd but with no efect.
Then i found Super Grub Disk live CD, and with that i tried to use their fix, which was the same as with the Fedora live cd i tried before, again no efect.Then i played around with Super Grub, and found the option to boot GNU/Linux indirectly, and with that metod i got results, found my menu.lst file and chose the kernel i wanted and it boots into desktop.
But i would need a more permanent solution, because now i allways have to use the same procedure with Super Grub Disk CD to boot into my Fedora 14.
When I first switched from windoze to Fedora I trimed a bit of space off the end of the HDD, formatted it to ext3 and installed Fedora 14 there. I have now completely rebuilt the machine and put a 2TB drive in. My intention was to upgrade to Fedora 15, but after a few weeks trying to get the new gnome to anything resembling useful, I gave up and decided to go back to the reliable 14.
I tried the old drive, and everything worked great, so I though no problem, clone that over to the new drive, and job done, no need to mess about for weeks getting all my settings back. I booted from the old drive with both connected and ran gparted, It sees both drives but won't let me copy the old partition. It complains about 'LMV is not yet supported' I tried booting from a gparted ISO with the same result.
How can I get this sorted? I've got work needing done, I don't have time to start from scratch (*AGAIN*),
If I use the super grub disk I can get to my ubuntu partition otherwise my windows partition boots automatically. I spent over an hour in the community documentation using the live cd to reinstall grub and nothing has fixed it. I think that grub is installed and the windows bootloader is just taking precedence.
my computer screwed up and the MBR or GRUB was screwed up, so I got my Windows 7 repair disk and repaired the MBR. Then I needed grub back so I could boot into Ubuntu so I went and looked for something to just install grub and found this Auto Super GRUB Disk (ASGD) thing. So I installed it and then it appeared on the windows boot manager menu when I started up and I went into it and installed grub again. Then when I booted back into windows, it asked me if I wanted to remove ASGD and I clicked yes. Ever since, the ASGD entry has not been removed from my boot menu for some stupid reason. What happens is the computer starts and goes into GRUB which is what I want and then if I go into Windows 7, it will then come up with another menu asking whether to boot into Windows 7 or the ASGD, even though ASGD isn't there anymore. I can still boot into windows, but this extra menu that comes up every time is starting to **** me off. I've tried EasyBCD and the entry does not come up on there.
I have read several manuals and online html on how to clone a partition to a greater one, I am still not sure about what to do.
Code: Select all# df -k /srv /usr Filesystem 1K-blocks Used Available Use% Mounted on /dev/md5 38445384 195236 36297128 1% /srv /dev/md3 8648896 1088016 7121540 14% /usr
What is the recommended procedure to clone i.e. /dev/mdx (/usr) partition to a greater one, say /dev/mdy, to accommodate for growth, whilst preserving attributes including timestamps (and yes, that means also including ctime).All of # cp -ax SOURCE DEST, # rsync -ax SOURCE DEST and # cpio modify ctime.Some sites recommend dd, i.e.:
URL....However, I am not sure what will dd copy do with end of partition, and will it see the remaining space on /srv (it's contents are dummy and will be overwritten).
My grub boot menu keeps getting bigger I assume after updates I started off originally with 2 options for ubuntu & one for win 7, how can I delete the one's that are not used. Pic attached.
So I have seen several super boot disks based on winpe(Like Bartpe super boot disk) out there and I am wondering if anyone can happen to point me to one that is based off open source software.
Super Boot Disk = A single boot disk that accomplishes a great many common tasks needed to rescue a system.some things that I am looking for in this would be: Virus scan, memory test, bootloader recovery, hard disk drive recovery/testing, gparted, clonzilla.and whatever else you could think of.I see that gparted and clonzilla both have live cd's available..but im looking to only carry one disk.
a windows installation on a fake-raid, /dev/mapper/ddf1_AR01p1 and an xtra penguinFS on ddf1_AR01p2. I simply tried to boot "Super Grub Virus" from a usb stick ... and the $%!($ER hosed the array. Luckily, my day to day OS and important data is on a different set of disks ... but my BIOS boot target is set to the fake-raid, so it did not kill anything genuinely important ... I just got lucky.
I would really like to restore the windoZe partition as it WAS. I actually use it a couple of times each year. I would just reinstall the OS ... really NOTHING important on those 2 disks, but I have no idea where my XP disk can be found ... but I know the xp installation is hiding in /dev/null ....
I used proprietary software (acronis trueimage) to clone an Opensuse 11.1 machine, onto another machine with somewhat distinct hardware (different motherboard, less memory). I expected to have to change entries in /boot/grub/menu.lst, /etc/fstab, etc. I was told a good way to do this was to use the Opensuse DVD's "repair installed system" feature.
When I ran the repair, I was informed that "bootloader configuration file contains errors". I attempted to re-install the bootloader, but received this unhelpful error: "An error occurred during boot loader installation. Retry boot loader configuration?". When I boot the system, I just see the text "GRUB ", followed by a flashing underscore character.
just wanting to know if anyone has implemented Fog (fogproject.org) on openSUSE. We use it at work throughout our enterprise for reimaging machines and it works very well.
I've spent the better part of an afternoon looking for a solution to a problem: backing up my installation of 10.10 as an image file to an external hard drive. My research has yielded a lot of suggestions for clonezilla, dd, and partimage/particlone, but those don't seem very appealing, due to a number of issues (can't backup live, copies free space as well, doesn't handle ext4, etc). Also why is clonezilla 150mb?
I'd like a simple solution that can clone an entire disk (used space only) to an explorable image file on a separate hard drive and be able to do it while the operating system is running on the disk. I used to use apricorn ez gig to do this on windows and it worked like a charm, but I can't seem to find a similar solution that creates and explorable .iso image file with linux. I've used superduer on osx, which is awesome and i wish there was something like that for ubuntu/linux.
I have my Mythbuntu 9.10 environment installed on an old 160GB PATA disk and have just purchased a new 64GB SSD that I want to transfer my installation to.In the past I've just used ddrescue to clone disks, however in this case the source disk is larger than the destination disk so it won't work. I only have a few GB of actual data on the 160GB disk, so the 64GB SSD is definitely going to be enough for me.
I guess I need someway of either cloning so that only the actual data and not the partition is brought across, or possible shrinking the partition(s) first on the source drive and then using the same ddrescue method I've used in the past.Just looking for some assistance on what method is the best/most reliable?
Recently my had disk crashed. It has taken me over a day to install and setup the drive - time I can't really afford. I'd like to know how I can clone a second as a bootable copy of the main hard drive and update from time to time. Therefore if the main hd fails again, I can simple boot from the second drive.How can I do this? I have two sata drives in the box, running 10.10 desktop.
Recently my had disk crashed. It has taken me over a day to install and setup the drive - time I can't really afford.I'd like to know how I can clone a second as a bootable copy of the main hard drive and update from time to time. Therefore if the main hd fails again, I can simple boot from the second drive.
I use dd in its simplest form to clone a hard drive dd if=INPUT of=OUTPUT However, I read in the manpage that dd knows a blocksize parameter. I was wondering whether there is an optimal value for the blocksize parameter that will speed up the cloning procedure?
I'd like to have a bootable cd which then allows me to clone a hard drive, much like the "Ghost" application. I need to copy Fat32, NTFS, as well as the various Linux formats. I've not created a bootable cd before, so a step-by-step would be rather handy.
I need to clone a laptop drive to a desktop drive. The laptop drive disk is 150 gb, however, only about 8 gb is used. Is it possible to clone this disk to a smaller drive?
I just invested nearly 12 hours configuring a CCTV system using CentOS 5.5 Server and Zoneminder. I have it setup just the way I want it. I would like to make a clone image of the drive just in case disaster strikes (lightning strike, failed hard disk, etc). In the Windows PC world, I use a program called Ghost to make a mirror image of a hard disk. I power the computer down, run Ghost to make a block level clone of the drive, then power it back up. Can I assume that will work with CentOS without problem?
In the computer now is a 320GB SATA drive. One partition on it is swap, and the other is ext3. There is no raid setup on the drive. I have an identical 320GB drive I could use and keep it in the computer unplugged from the power and not spinning. That way if anything ever happens, I can power down, move the power and data cable to the new drive and power it back up. Granted, I will lose any new config and database changes, but it will be a lot better than starting back at square 1 and reconfiguring the entire OS and software.
I want to mount a 'super floppy' which is listed in the disk utility as /dev/sdb.
I am unsure of the sequence here. Should I first mount: mount /mnt/floppy ...or something similar And next edit the /etc/fstab file....or is this step not necessary.
Finally, this is vfat formatted. Should I try to reformat it in ext or leave it as is?
To make a full backup I run a live Knoppix DVD and clone the computer's HDD to an external HDD using the dd command. Is there a possible problem with the source being copied onto bad sectors on the destination disk? If so is there a way to prevent this from happening? A typical dd command I use looks like: dd if=/dev/sda of=/dev/sdb bs=4096 conv=notrunc,noerror. Is this the recommended command for cloning to a disk of equal size?
I have a sata 320 gb with mandriva linux 2009.1 on it.And it is what curently atached to my cpu. It is shown as 'sda' in the partition table.I also have another 40gb hard disk with windows xp installed on it.It is shown as 'hda' in the partition table . Now what i want to do is attach this 40gb hard disk to my pc and configure grub on my 320gb hard disk('sda') so as to boot windows xp(which is residing on the second hard disk,'hda')Can anyone tell me if what im doing is feasible or not? If it is feasible,can anyone suggest me how to get it working. I know i just need to add 2-3 lines to my grub.conf, but dont know what exactly i need to write.
Edit: This is somewhat inaccurate, please see post #16 on page 2 for my actual situation
I'm more than a little confused by this. A little while back I had to reinstall my machine because I had a hard disk failure and I replaced my primary drive.Everything went perfectly smoothly, but then a couple of weeks after that when I rebooted, it dumped my into the grub rescue console
Code:
error: out of disk. grub rescue>
So, I found a solution to the problem on these forums, rebooted perfectly fine, and thought everything was fine. Until the next time I rebooted, when it happened again. And now, every single time I reboot, I get the same issue.I have to do the following, each and every time I want to reboot - and i'm at a loss to explain why grub is borking itself every time.Boot off a live cd.Open a konsole window
Code:
sudo su - mount /dev/sda6 /mnt mount /dev/sda1 /mnt/boot mount --bind /dev /mnt/dev
I'm still kinda new to linux. I've been learning my way around the command line and been experimenting with linux on a couple computers of mine. Occasionally after trying a few things, grub or linux won't load right. I've done some research on possible tools to help but I was wondering if any of the more experienced users had some recommendations for boot disk or tools to help repair grub and/or linux desktop/server editions.
p.s. I would also be interested in any fun and interesting tools, programs, and/or repository's that other users have found beneficial.
how to use the <Super>ButtonX (<Super>Button1 for example for the enabled Compiz Screenshot plugin)? I also notice there is configurable buttons 1 throught 20 under the various options. At first I thought the ButtonX was a mouse button. Maybe it is with some anticipation of there being eventually being a possible 20 buttons on the mouse. I know the Super key is the Key with the Windows logo on it. But I don't know what to do to get the needed Super Key / Button combination. After having enabled Compiz's Screenshot plugin by its default, I don't get an image after hitting any of the Super key and mouse button combinations. I'm running Ubuntu 11.04.
After completing the installation of Fedora-FEL edition, I cant boot from my hard disk. "No bootable device found " error appears.
I have one Windows XP & 2 Linux installation in my disk. I tried to restore grub using "setup (...)" command.but same error repeats. Even I cant restore Windows XP using "fxmbr" command in... recovery console .
But I can boot from that drive by "chainloader" command in grub. code...
Running above command in grub terminal boots my hard disk ("hd1" is my "unbootable disk")
my Fedora 11 system is not starting anylonger. It stops with the message:
Code:
VFS: Can't find ext4 filesystem on dev dm-0
The system told me since a while, that a lot of the sectors of one disk of the (software) RAID compound are failed already. So tried to disconnect each of the disks and start them separately. Unfortunaltly this is not working (for one its is not working at all, the other wents the same far as with both), when I tried to recover the system with the Fedora DVD, it said no distribution found. I am quite new and do not know so much about linux system, so i do not know what further information you could need. Maybe it can be important, that both disks are encryped (the system wents so far, that I can type in the password).
I am running a 14 disk RAID 6 on mdadm behind 2 LSI SAS2008's in JBOD mode (no HW raid) on Debian 7 in BIOS legacy mode.
Grub2 is dropping to a rescue shell complaining that "no such device" exists for "mduuid/b1c40379914e5d18dddb893b4dc5a28f".
Output from mdadm: Code: Select all # mdadm -D /dev/md0 /dev/md0: Version : 1.2 Creation Time : Wed Nov 7 17:06:02 2012 Raid Level : raid6 Array Size : 35160446976 (33531.62 GiB 36004.30 GB) Used Dev Size : 2930037248 (2794.30 GiB 3000.36 GB) Raid Devices : 14
[Code] ....
Output from blkid: Code: Select all # blkid /dev/md0: UUID="2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb" TYPE="xfs" /dev/md/0: UUID="2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb" TYPE="xfs" /dev/sdd2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="09a00673-c9c1-dc15-b792-f0226016a8a6" LABEL="media:0" TYPE="linux_raid_member"
[Code] ....
The UUID for md0 is `2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb` so I do not understand why grub insists on looking for `b1c40379914e5d18dddb893b4dc5a28f`.
**Here is the output from `bootinfoscript` 0.61. This contains alot of detailed information, and I couldn't find anything wrong with any of it: [URL] .....
During the grub rescue an `ls` shows the member disks and also shows `(md/0)` but if I try an `ls (md/0)` I get an unknown disk error. Trying an `ls` on any member device results in unknown filesystem. The filesystem on the md0 is XFS, and I assume the unknown filesystem is normal if its trying to read an individual disk instead of md0.
I have come close to losing my mind over this, I've tried uninstalling and reinstalling grub numerous times, `update-initramfs -u -k all` numerous times, `update-grub` numerous times, `grub-install` numerous times to all member disks without error, etc.
I even tried manually editing `grub.cfg` to replace all instances of `mduuid/b1c40379914e5d18dddb893b4dc5a28f` with `(md/0)` and then re-install grub, but the exact same error of no such device mduuid/b1c40379914e5d18dddb893b4dc5a28f still happened.
[URL] ....
One thing I noticed is it is only showing half the disks. I am not sure if this matters or is important or not, but one theory would be because there are two LSI cards physically in the machine.
This last screenshot was shown after I specifically altered grub.cfg to replace all instances of `mduuid/b1c40379914e5d18dddb893b4dc5a28f` with `mduuid/2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb` and then re-ran grub-install on all member drives. Where it is getting this old b1c* address I have no clue.
I even tried installing a SATA drive on /dev/sda, outside of the array, and installing grub on it and booting from it. Still, same identical error.
I accidently deleted my ubuntu partition, and when boot I get this message:GRUB loading.error:unknown filesystemgrub rescue>I can't get into my bios options either... I just see the MSI splash screen and it cuts right to this error message.
