Lets Try This Again
Re: Well lets try this again
A human later on my own eye. That's one of the most graceful and elegant descriptions I think I've e'er seen.
Originally Posted past JKyleOKC
Sounds like my ain flim-flam for learning something new: I look for the most authoritative volume on the subject that I can find, and of course information technology contains all sorts of assumptions that I know nothing about -- but that steers me in the correct direction to get the background for the subject, and keeps me from wasting a lot of time on things that won't help at all.
That's how it starts for me. I'chiliad bored or there is some inkling of an idea floating around in my head - so, when I start "browsing effectually," it begins to take shape until POOF the light seedling goes off and I have something very specific I just need to know.
Sometimes, though, I merely browse around to discover something that sounds interesting. On the forums here, 1 that I hit fairly often is "Tips and tutorials" which frequently gives me ideas of things I ought to try...
And then things similar your renaming thread really help a lot. I had almost no cognition of "sed" except its existence, when I suggested that information technology might assistance. That example you mention really helped me a lot to see how it's used! And that, my friend, is how nosotros learn all that stuff -- similar eating an elephant: 1 byte at a time.
That's such an encouraging affair to hear yous say and it means a lot to me. I spend a lot of time writing things in these posts (similar finishing a thread with a summary post and describing my process and results) but in the hope someone will benefit from it. Even if that benefit is something modest or something I don't come across the connexion in. Sometimes I feel pretty dumb while I'm writing it and I'thousand not certain what others call up of me when they read that stuff. I do information technology anyway though because I believe it is important.Sunday's coming my friend. Clone my os time is near. I might exist able to practise information technology today though - and that would be awesome! I accept a couple things to attend to merely I'm going to try and squeeze it in.
By the way, there is this business programme I've been working on (a web site thought). Is this something you would be interested in reviewing? Maybe, if it interests yous, there is some role you could play in it. Might be a real money maker . . .
Let me know. PM me if you lot'd like to talk almost it.
Last edited by ClientAlive; June 12th, 2011 at 07:ten PM.
� The all-time method for accelerating a computer is the one that boosts it past 9.viii chiliad/s2. �
- Bearding
Re: Well lets attempt this again
Ok, and then I have an prototype of my electric current os, made with clonezilla, saved on my usb drive - except that information technology seems this may not play out the way I had initially idea.I gather there are two ways that doing something like this could play out:
(i) The image y'all create is created in such a way that it can exist installed in Virtual Box the aforementioned way any other standard install is. I think that in order to do it like that, 1 would have to obtain an image of their system that includes the installer and such - however they accomplished it.
(2) Apply a regular backup image and restore the backup, not to the regular system, but to the right place so it is in Virtual Box.
Now, from what I observed while using clonezilla this morining, I call back it is #2 that I will be stuck with - if I use clonezilla. At present I don't want to abandon the clonezilla route too hastily every bit I have an investment into information technology already and I am at least a niggling familiar with using it. what I demand to figure out is where to restore this backup to and a better idea of the rest of the procedure in order/ sequence.
And so, with regard to the procedure order/ sequence, I'chiliad thinking it would become:
(one) Use Virtual Box's gui to create a virtual motorcar only do non install anything into it.
(2) Reboot the system with the clonezilla live cd in the bulldoze. Employ clonezilla to restore the epitome I created this morning but direct the restoration to the advisable place - so information technology goes into the virtual machine non the regular organisation.
?? And what/ which place would that be ?? And how would I "straight" such a thing in clonezilla anyway ??
(iii) I wonder if there would be another obstruction that could ascend. Namely symbolic links within the virtual auto. Perhaps there would exist broken links after step ii and they would need to exist stock-still? This is a complete approximate though - as I have no thought how that stuff works inside the virtual motorcar.
(4) Reboot the figurer, say brusque prayer that all has worked as it should; and, with any luck, bask my new vm version of my cloned os.
By the mode, the reason I marked this post with the exclamation mark symbol is that I've been planning this project for a week now. Biding my fourth dimension until today, Sunday, when I actually accept fourth dimension to do this. I'm afraid if I don't get it done today it could be another week before I'll have time to come up back to it. Now that's a gut wrenching thought.
Last edited by ClientAlive; June 12th, 2011 at 07:30 PM.
� The best method for accelerating a computer is the one that boosts information technology past 9.8 m/s2. �
- Anonymous
Re: Well lets try this again
Virtually, but not quite. Step 1 is expert. Withal you don't need to reboot your system at step 2. Instead, when creating the VM, set it up to boot from CD, and attach your actual bulldoze as its CD. Put the clonezilla cd into the drive and and so start the VM.
(ane) Use Virtual Box's gui to create a virtual machine merely exercise not install anything into it.
(ii) Reboot the system with the clonezilla alive cd in the drive. Apply clonezilla to restore the prototype I created this morn but direct the restoration to the appropriate place - so it goes into the virtual machine not the regular organisation.
?? And what/ which identify would that be ?? And how would I "direct" such a thing in clonezilla anyhow ??
(3) I wonder if there would be another obstacle that could arise. Namely symbolic links within the virtual motorcar. Perhaps in that location would be broken links after pace 2 and they would demand to be fixed? This is a consummate judge though - as I have no idea how that stuff works within the virtual machine.
(4) Reboot the computer, say curt prayer that all has worked as it should; and, with any luck, relish my new vm version of my cloned os.
Information technology should boot into clonezilla.
Distressing simply I can't assist with how to tell clonezilla where to do the restore, since I've never really used the program. The "where" will be the virtual drive of the VM, only I don't know the clonezilla menus, nor exercise I know how that drive will exist identified. I'd guess, notwithstanding, that it will be chosen /dev/sda1 or /dev/hda1. Simply it may, since at this betoken information technology's totally blank with not even an MBR sector, but be identified as something else. Nevertheless information technology should exist the only HD shown for the VM, and since clonezilla is running in the VM rather than in the host, it should just show that unmarried HD as a potential target.
For point 3, symbolic links ought not be a problem. If they exist, they ought to still exist valid, specially if your clonezilla paradigm includes your home directory. They are symbolic subsequently all, which ways there's nothing absolute such equally inode numbers in them.
For point 4, after the restore completes, squirt the cd from the bulldoze and restart the VM, not the host figurer. It should come up with a re-create of your host -- but equally I mentioned much earlier the differences in hardware might requite you trouble, and nosotros can't know most that until you try it.
Re: Well lets try this once again
About, but not quite. Stride 1 is good. However you don't need to reboot your system at step 2. Instead, when creating the VM, fix it upwardly to kick from CD, and adhere your actual drive every bit its CD. Put the clonezilla cd into the drive and and so showtime the VM.
It should boot into clonezilla.
Sorry merely I tin't help with how to tell clonezilla where to practise the restore, since I've never really used the programme. The "where" will be the virtual drive of the VM, but I don't know the clonezilla menus, nor do I know how that drive will be identified. I'd guess, notwithstanding, that it will exist chosen /dev/sda1 or /dev/hda1. But it may, since at this point information technology's totally blank with non even an MBR sector, just be identified as something else. Nevertheless it should exist the only HD shown for the VM, and since clonezilla is running in the VM rather than in the host, it should merely show that unmarried HD as a potential target.
For point 3, symbolic links ought not be a trouble. If they be, they ought to still be valid, especially if your clonezilla epitome includes your abode directory. They are symbolic afterward all, which means in that location's nothing absolute such as inode numbers in them.
For point 4, after the restore completes, eject the cd from the drive and restart the VM, not the host figurer. It should come up with a copy of your host -- but as I mentioned much before the differences in hardware might give you trouble, and nosotros tin can't know well-nigh that until you try it.
Oh wow this is going to exist a real trip! Until just this moment I was thinking that if I made a error and information technology restored to the regular organisation information technology could crusade me all kind of grief - break the thing basically. Actually though, all that would happen is it would replace my current organisation with my electric current system - I hope - and there would exist no more harm than 20 min or so of wasted time and attempt. Well, sort of wasted. I wouldn't have reached my goal just I would have learned something. Hmmm . . . remember I'll giver er' a try and come across what happens. Wish me luck!
� The best method for accelerating a estimator is the ane that boosts information technology by nine.8 m/s2. �
- Anonymous
Re: Well lets try this again
Almost, but non quite. Step 1 is proficient. Notwithstanding you lot don't need to reboot your arrangement at step 2. Instead, when creating the VM, fix it up to kick from CD, and adhere your actual bulldoze as its CD. Put the clonezilla cd into the drive and and so start the VM.
It should boot into clonezilla.
Sorry but I can't help with how to tell clonezilla where to do the restore, since I've never actually used the program. The "where" volition exist the virtual bulldoze of the VM, just I don't know the clonezilla menus, nor do I know how that drive will be identified. I'd guess, yet, that it will be chosen /dev/sda1 or /dev/hda1. But it may, since at this point it's totally bare with non even an MBR sector, just exist identified equally something else. Nevertheless it should exist the only HD shown for the VM, and since clonezilla is running in the VM rather than in the host, it should merely bear witness that single Hd as a potential target.
For signal iii, symbolic links ought non exist a problem. If they be, they ought to withal be valid, especially if your clonezilla image includes your domicile directory. They are symbolic after all, which means there'south nada absolute such as inode numbers in them.
For point 4, after the restore completes, eject the cd from the drive and restart the VM, not the host computer. It should come upwardly with a copy of your host -- but equally I mentioned much before the differences in hardware might give you lot trouble, and nosotros can't know most that until you endeavor it.
Ok. And so I did just like you mentioned and all seemed to go well. I also establish some details here: http://jlorenzen.blogspot.com/2010/0...age-using.html which I was careful to pay attention to. Such as enabling the usb drive my image is on. I didn't need to utilise a second usb like the guy in that commodity because my clone is minor and I do have plenty space on my local disk for information technology. When I got to that point in clonezilla information technology was as you had supposed - the simply pick for where to restore to is the virtual disk (and, it turns out, information technology is named in such a style that it'south clear that's what it is). When I moved past that step and the restoration procedure began I got an error message from clonezilla. Plainly information technology doesn't like the partitions structure on that virtual disk (or lack thereof). I've fastened a movie of that fault screen. There was more to it than what shows upwards in the moving picture but I couldn't become the screen to coil up to show the rest.Based on what I run across I think that one of two things needs to happen.
(i) The virtual disk needs to take a partition structure created in it that is the aforementioned equally my local disk. The same every bit the prototype that came from information technology. I don't encounter any way that could happen though. And for a couple different reasons also.
(ii) Something in the clonezilla image, some file or something, needs to be edited to lucifer the way the virtual disk is. Something renamed, perchance more.
There is a reference to this editing of files in clonezilla here: http://forums.linuxmint.com/viewtopic.php?f=42&t=67140 merely they seem to be doing it for a unlike reason/ dissimilar outcome.
What I don't get is that the guy in the first link in this post - didn't seem to have any trouble with doing this.
So, I guess I'll keep looking around and see what I tin find or what to do to become past this betoken.
--------------------Edit: I just idea of this, merely, function of what I call back happens in a standard install is that a sectionalisation construction is created. I would have thought that clonezilla deals with this when restoring. If it does, that leaves only one other option that I tin can think of. That because it is a virtual disk and not a regular hard drive it's somehow unlike and won't let clonzilla create the sectionalisation table. This doesn't brand sense though because if that were the case it wouldn't let a standard install exercise it either.
There is a tertiary possibility:
The size of the virtual disk is smaller than the total size of my local hard drive (evidently). Hither's what I observe odd about this possibility though:
(1) I thought we covered this effect further back in this thread. We determined that clonezilla merely uses the used space on the disk and so the virtual disk didn't need to be the same size as my whole hard drive.
(two) I looked at the size of my used space before creating the image with clonezilla this morning. It said it was five.5 gig. The virtual drive I created is 8 gig.
If, for some odd reason, this is the problem - I tin can only think of one possible solution. Something in the clonezilla epitome needs to be edited to match, non the size of my local disk (what information technology probably recorded when it created the paradigm), but the size of the virtual disk. So, if part of what clonezilla does when it restores is create a partition table, doing this would be like to using an application to create partitions on my bulldoze. Merely, in this case, it would be telling whatever utility clonzilla uses the data you want it to accept for the sectionalisation tabular array when it makes it. Kind of like a back door or something.
If the size of the used space is just five.5 gig and the size of the virtual disk it is to get onto is eight gig - and then in that location shouldn't be any problem with doing something like that.
Any ideas people??
--------------------------------Edit 2: I just looked at the pic I attached more closely. It says: Error: /dev/sda: unrecognized disk characterization." I think what it'south saying is something in the virtual disk is labeled /dev/sda and that doesn't line up with what is in the image I want information technology to restore.
I'1000 stumped.
Last edited past ClientAlive; June 13th, 2011 at 12:00 AM.
� The best method for accelerating a figurer is the i that boosts information technology past 9.eight one thousand/s2. �
- Anonymous
Re: Well lets try this again
The virtual drive has to be the same "physical" size as the physical drive.500GB drives needs to be restored to a 500GB virtual drive.
You can use a dynamic sized disk and so that it only uses 5GB of space, but the VM sees that whole 500GB.
Re: Well lets endeavor this again
The virtual drive has to be the same "physical" size equally the physical drive.
500GB drives needs to be restored to a 500GB virtual drive.
You tin use a dynamic sized disk so that it simply uses 5GB of space, but the VM sees that whole 500GB.
I see. Well, even if I never really employ all the infinite (I couldn't) it still seems pretty hoakey. There isn't a way to change some configurations in the paradigm to make it call up it's smaller? I hateful, the used space is smaller. Just that I don't know how that data is spread out across the disk. Just because the used space is only v.5 gig doesn't mean information technology's all together in one identify I suppose. Is that thinking on the right rail?And what about the fault in the picture? what it's lament most there is the disk label. Unless I'm not understanding what is meant by "disk label."
---------------------Edit: Ok, but what about this . . .
I just looked at the backdrop of the paradigm I created this morining. It says the size is 2.half-dozen gig. I remember clonezilla compresses the file when it saves it. At present . . .
The size of my entire local hard disk drive is very roughly 40 gig. Is a standard/ default installation with nothing special almost the partitions and Ubuntu is the only organisation on this machine (so that whole 40 gig is existence used by my 1 and merely Ubuntu organization - that's how things are prepare).
Here'southward the readout from Applications > Deejay Usage Analyzer:
Total File Organisation Capacity: 35.ane GB (used: 5.5 GB available: 29.half-dozen GB)
So here's the thing - I can see an epitome size of 2.6 gig from a used space of v.5 gig, merely I can't motion-picture show an paradigm size of 2.vi gig from a total size of 35.1 gig. You tin can compress 5.five gig downwardly to 2.6 gig (especially if a lot of it is text), at that place's no manner you can compress 35.1 gig downward to 2.six gig though. I'grand not sure how this works?
Last edited by ClientAlive; June 13th, 2011 at 12:37 AM.
� The best method for accelerating a reckoner is the one that boosts information technology by 9.8 g/s2. �
- Anonymous
Re: Well lets attempt this again
Yep, it only copies the used data and compresses it.
Re: Well lets try this once more
As CharlesA said, define your virtual disk to exist 40 GB and "dynamic" so that information technology volition actually use only plenty infinite to hold your 5.half dozen GB. I concord that it's a bit hokey to do it this mode, merely then Clonezilla is a complimentary package and doing information technology this style eliminates lots of potential problems in dealing with mismatched disk sizes. As information technology is, the program only needs to expect at the disk to be assured that there's plenty room -- even if, as in this case, none of that "enough" space actually exists before it'southward really needed!When you restore from Clonezilla, it will effectively defrag your files and so that they are all up at the front. This is implicit in the way that information technology compresses and decompresses without storing whatsoever unused disk infinite.
As for non having a characterization, you may need to dig into the VBox manual affiliate on VBoxManage to see if there's a way to create the virtual disk with a label -- and through the Clonezilla docs to meet if they tell yous anything most what kind of characterization information technology'south looking for! My experience is that the MBR for a partition contains its label, then no label would be present until the drive was partitioned.
Still, information technology's also quite possible that this error bulletin is a carmine herring acquired by the size mismatch. Quite frequently, a subtle error volition confuse a plan into taking a wrong path and so displaying a totally unrelated message a bit later. I've had it happen many times!
Terminal edited by JKyleOKC; June 13th, 2011 at 05:26 AM.
Re: Well lets effort this over again
Every bit CharlesA said, ascertain your virtual disk to be 40 GB and "dynamic" so that information technology will actually apply but enough space to hold your 5.half-dozen GB. I agree that information technology's a bit hokey to do information technology this mode, merely then Clonezilla is a free package and doing it this way eliminates lots of potential problems in dealing with mismatched disk sizes. Equally it is, the program only needs to await at the deejay to exist assured that in that location's enough room -- fifty-fifty if, as in this case, none of that "enough" space really exists before information technology's really needed!
When y'all restore from Clonezilla, it volition effectively defrag your files so that they are all up at the front. This is implicit in the way that it compresses and decompresses without storing any unused disk space.
Every bit for non having a label, you may need to dig into the VBox manual chapter on VBoxManage to see if there's a way to create the virtual disk with a characterization -- and through the Clonezilla docs to see if they tell you anything near what kind of label information technology'southward looking for! My experience is that the MBR for a partition contains its label, so no label would be present until the drive was partitioned.
However, information technology's also quite possible that this fault message is a cherry herring caused by the size mismatch. Quite ofttimes, a subtle error will confuse a program into taking a wrong path then displaying a totally unrelated message a bit later on. I've had it happen many times!
I just tried doing it with a larger deejay size and got another, different, fault message this time.I deleted the other vm. Looked in gparted to see the size of the entire disk to more than sig digits than deejay usage analyzer will tell yous and it said 35.69 GiB. I created a virtual machine with a disk size of 35.69 GB (now I have heard there is a divergence between GiB and GB but I don't know the detail or what the conversion is). So so I go through the procedure with clonezilla again. I become to the point where I've made all my selections and tell information technology to go ahead with the restore. Right away it gives me an error saying two things that stand up out. (1) Information technology says "cannot create sectionalisation exterior the local disk. And then (2) It poses the question, is the disk the right size (or something of that nature).
I had found a thing about resizing/ shrinking the size of the virtual disk here: http://forums.virtualbox.org/viewtop...asc&highlight= and had intended to do that at the very cease if I could get this installed and working. Now I wonder if I can't do that to the clonzilla image first, and then try again to install it.
� The all-time method for accelerating a estimator is the one that boosts it by ix.8 m/s2. �
- Anonymous
Source: https://ubuntuforums.org/showthread.php?t=1774895&page=4
0 Response to "Lets Try This Again"
Post a Comment