Clonezilla does not work with Windows 8.1 in cloning disk(disk-to-disk clone)

Discussion in 'PC Hardware' started by RayLopez99, Oct 27, 2014.

  1. RayLopez99

    RayLopez99 Guest

    On Thursday, November 27, 2014 1:50:17 AM UTC+8, RayLopez99 wrote:
    !
    I did a clean reinstall today...I decided to stick to 32 bit Windows 8 since I only have 4 GB RAM and more margin for error with 32 vs x64 bit Windows..

    After the clean reinstall, chkdsk found no errors, even on reboot.

    I think I figured out why the original installation went bad. It is hintedin various forums. It is because with my SATA drives the "Disk 0" was originally the smaller Western Digital HDD, that I cloned into a larger Seagate drive that was "Disk 1". However, I did not switch the SATA cables, hence Disk 1 (the Seagate drive) was the bootable drive yet it showed up in Windows as "Disk 1" not Disk 0. This is NOT a problem EXCEPT if you have a cold power off or some sort of problem (my speculation, but that was a hint from another poster who said 'log' information is automatically stored in Disk 0 by Windows 7 or 8). So, the first time I had some small hickup, like a hard power shutdown (which is rare since I use UPS but it happens once every few months due to a variety of factors, typically programs that hang and I can't terminate them),Windows wrote something on "drive disk 0" which was in fact the old, now non-bootable, "Drive D". So the problems began.

    Solution: clean reinstall, then switch the SATA cables so "drive disk 0" is in fact on the bootable drive (the Seagate) while the Sata cable for disk1 is on the old, formerly bootable, but now just used for data and backup Western Digital drive.

    BTW, in all of this I decided--at the spur of the moment, and there were some hairy moments--to update my BIOS by downloading the latest BIOS and frominside the BIOS reading the file. Supposedly this AMI MegaTrends BIOS hada stability issue involving 4096? byte file size for NTFS and hard drives,so perhaps this was also a contributing factor.

    So at the moment my system is back to being stable, and all's well except for the two days I will waste reinstalling all the programs I use...but maybe it is good since I can avoid installing out some of the old programs I never used.

    RL
     
    RayLopez99, Nov 27, 2014
    #21
    1. Advertisements

  2. RayLopez99

    Dustin Guest

    LOL... Well, that's one way of fixing the issue.
    hehehehehe.. that isn't what happened. but, i'm totally okay with you
    thinking it, ray.
    An okay solution, if you like clean reinstalling. If not, a poor
    solution. Likely your last resort.
    In other words, you really don't have the foggiest idea what the
    problem was.
    Ayep. Something good has come of it. The system will be cleaner for
    awhile now. Wasn't actually necessary for a reload though. [g]
     
    Dustin, Nov 27, 2014
    #22
    1. Advertisements

  3. RayLopez99

    pedro1492 Guest

    Clonezilla does not work with Suse enterprise linux, but that is the fault
    of Suse - they use disk by id (model and serial number) instead of label,
    so the clone will not boot.
     
    pedro1492, Nov 29, 2014
    #23
  4. RayLopez99

    RayLopez99 Guest

    Thanks Dustin. If I didn't know you better, I'd think you're trying to be helpful, though it's clear you have no idea what you're talking about! [g]

    RL
     
    RayLopez99, Nov 29, 2014
    #24
  5. RayLopez99

    Dustin Guest

    You're welcome, Ray. However, I do infact know exactly what I'm
    talking about. You couldn't be more off in your diagnosis and posted
    reports of what you think went wrong with the system. I wouldn't let
    you anywhere near any machine I'm responsible for. You're too much of
    an idiot. You actually think you know WTF you're doing, when it's
    clear as day by reading your own posts, you don't have the foggiest
    idea.

    Initially, I was trying to help you out, but I remember you as the
    same snot nosed little prick from alt.comp.anti-virus,
    asking/trolling more like about virus writing. You kept trying to
    tell me I didn't know what I was talking about concerning them;
    despite the fact I've written quite a few and some are very well
    known to this day. You'd post asking some dumbass malware related
    question. One of the regulars (sometimes including myself) would try
    and answer and you'd claim we didn't know what we were talking about.

    I asked you if you knew what a prepender was on several occasions and
    I heard crickets for a response to that one. Someone who's supposed
    to know virus and other forms of malware as you profess should easily
    be able to answer that question. Shouldn't require source code
    showing how it's done, if you were actually a coder of any sort.

    I've noticed your brown nosing the hell out of a couple of
    knowledgeable posters here, though. Turns out by reading your posts,
    you're a fucking lousy troubleshooter and hardware guy too.
    Seriously. You suck. I don't know why you kept going on about
    compiling code, jeeze... You probably don't have enough original
    source code to fill a floppy diskette.

    I even provided you a url or two describing some of them from known
    antivirus database sites; and you claimed I wasn't the author. I
    challenged you to find it's source code someplace online (as I never
    released it and so I'm the only person to have it), you couldn't do
    so. I posted a section of it, you accused me of stealing it; but when
    asked where I stole it from, you couldn't provide a single fucking
    url! Not a single one. Impossible!

    I didn't steal it, I wrote it. It's all original code and it's all my
    original work.

    I also remember you asking me to prove I could code in assembler by
    writing a simple hello world program. I wrote you one that would
    print a message for you on the screen as well as write the same
    message inside a file called ray.txt created in the current directory
    if possible.

    You claimed to know asm, and, demanded I comment the same source to
    prove I really 'knew it'. So I did. You wrote that int21 had
    something to do with an integer and I was trying to bullshit you
    again. You didn't like my commentation efforts. Although I took the
    time to explain what every single line in the source code actually
    did, you still claimed it wasn't assembler and I didn't know WTF I
    was doing.

    You even accused me of stealing it from someplace; but when I asked
    you several times to cite the original source code on some website,
    you could not do so.


    I did however do you a solid and provide source to two very old and
    easily contained viruses. I've never seen a response from you to any
    of the source code. Ones a prepender, one's an overwriter and you
    can't even tell me the fucking difference. You probably still don't
    understand how either of them work, and I took the liberty of
    disabling both source files. If you were ever able to actually
    compile either of them, they wouldn't replicate. You couldn't use
    them to do any harm.

    If you could actually write code worth a shit though, you could take
    those sources and learn how an overwriter works as well as a simple
    prepender. Then again, if you could code worth a shit, you wouldn't
    need to see somebody elses work (like mine in this case) to learn how
    to do it.

    You're a damn brown nosing poseur troll, that's for sure.
     
    Dustin, Nov 30, 2014
    #25
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.