• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Restoring to a single hard drive in a multi hard drive system

Scheduled Pinned Locked Moved
General
4
5
2.1k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N
    Nethfel
    last edited by Jun 13, 2013, 12:49 AM

    Hi all,

    I’m experimenting with FOG on a specific system and had an odd issue I’m hoping someone can help me with.

    The target machine has 2 hard drives (sda and sdb)

    Process:

    Setup a basic install of windows 7 on sda. Formatted sdb to act as extra storage

    Image created using Single drive method that recorded all partitions of sda

    Normal wipe pushed and performed on sda

    Image deploy to the machine.

    I expected the image to be deployed to the sda drive (as I didn’t remove the drive from the system and it was the drive that the image was originally made from) but instead it imaged to the sdb drive. This is NOT a good thing as I would like to be able to have a second drive in this system that would contain data that if the OS was corrupted and needed to be re-deployed that the data drive would remain untouched, but FOG seemed to completely ignore the wiped drive and instead installed on the drive that would be designated for data.

    Granted this wasn’t a production setting (had it been, this would have been REALLY bad) - I was wondering if anyone had any tips on how to make sure that sda is restored to sda even if the sda drive was wiped…

    1 Reply Last reply Reply Quote 0
    • B
      Bjorn Jentoft
      last edited by Jun 13, 2013, 6:49 AM

      When booting from a non-disk media like pxe boot, the Linux kernel sometimes will choose drives for sda and sdb differently than you expect, depending on BIOS settings and actual ports used. Perhaps this is the case here. You could do a debug boot and check that your primary disk is actually determined to be sda by the fog kernel.

      1 Reply Last reply Reply Quote 0
      • M
        madeyem
        last edited by Jun 13, 2013, 6:52 AM

        I always unplug additional HDDs before deploying/imaging, because I would assume FOG to act like that (i.e. not always take the first HDD for deploying/imaging). Maybe someone else has a real solution to this.

        1 Reply Last reply Reply Quote 0
        • X
          x23piracy
          last edited by Jun 13, 2013, 7:39 AM

          Hi,

          ever tried that option?

          [IMG]http://i.imgur.com/PBsZmim.png[/IMG]

          Regards X23

          ║▌║█║▌│║▌║▌█

          1 Reply Last reply Reply Quote 0
          • N
            Nethfel
            last edited by Jun 13, 2013, 1:54 PM

            x23: Thanks, using that seemed to solve my problem - I appreciate the info - I hadn’t even noticed that entry, I’m still really new to FOG 🙂

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            1 / 1
            • First post
              3/5
              Last post

            176

            Online

            12.1k

            Users

            17.3k

            Topics

            155.3k

            Posts
            Copyright © 2012-2024 FOG Project