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

Fatclone.C: Filesystem isn't in a valid state

Scheduled Pinned Locked Moved Solved
FOG Problems
4
23
7.9k
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.
  • A
    abos_systemax @george1421
    last edited by Dec 15, 2016, 12:11 PM

    @george1421

    This concerns a Lenovo M900 Desktop (ThinkCentre) - Type 10FLS4BD00
    The Windows 7 image can boot successfully, but the FS is NTFS, not FAT.
    I performed a chkdisk /F, but that did not resolve anything

    Q 1 Reply Last reply Dec 15, 2016, 12:13 PM Reply Quote 0
    • Q
      Quazz Moderator @abos_systemax
      last edited by Dec 15, 2016, 12:13 PM

      @abos_systemax Can you please post a picture of Disk management with the partition layout.

      Fatclone.c shouldn’t run if there’s no FAT partition, so I can only assume there is a hidden one.

      1 Reply Last reply Reply Quote 0
      • A
        abos_systemax @Quazz
        last edited by Dec 15, 2016, 12:17 PM

        @Quazz

        The output from Fdisk is as below:

        Disk label type: gpt

        Device | Start | End |Sectors |Size | Type
        /dev/sda1 | 2048 | 206847 | 204800 | 100M | EFI System
        /dev/sda2 | 206848 | 468991 | 262144 | 128M | Microsoft Reserved
        /dev/sda3 | 468992 | 168353297 | 167884306 | 80.1G | Microsoft Basic data
        /dev/sda4 | 467146752 | 500117503 | 32970572 | 15.7G | Microsoft Basic data

        the Partclone fails on Sda1

        Q G 2 Replies Last reply Dec 15, 2016, 12:23 PM Reply Quote 0
        • Q
          Quazz Moderator @abos_systemax
          last edited by Dec 15, 2016, 12:23 PM

          @abos_systemax So, it IS an EFI system, alright, that brings us one step closer.

          Boot into Windows

          Disk management

          Right click System Reserved (100M in size) and choose change letter and paths

          Click on add

          Choose a letter (doesn’t matter, we’ll take K for the example)

          Open command prompt (administrator)

          Now type chkdsk K: /f

          After it’s done you can remove the letter again through disk management

          Linux has dosfsck, but I wouldn’t trust it with the boot partition of a EFI windows installation personally.

          A 1 Reply Last reply Dec 15, 2016, 2:26 PM Reply Quote 0
          • G
            george1421 Moderator @abos_systemax
            last edited by Dec 15, 2016, 12:41 PM

            @abos_systemax My intuition is telling me this is a half breen win10/win7 installation setup.
            I see bits of both OSs in the partition table For Win7 You would normally have a boot partition (my guess /dev/sda2) and then an OS partition (/dev/sda3). With Win10 you would have a boot partition (/dev/sda1), an OS partition (/dev/sda3) and a system recovery partition (/dev/sda4).

            My guess is this system came with Win10 on it, then you reloaded Win7 over the top of the win10 install??

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            G 1 Reply Last reply Dec 15, 2016, 12:57 PM Reply Quote 0
            • G
              george1421 Moderator @george1421
              last edited by Dec 15, 2016, 12:57 PM

              @george1421 I just looked at a fresh win10 uefi install and there are 4 partitions on that disk
              sda1: EFI System 100M
              sda2: MS Reserved 16M
              sda3: OS 232GB
              sda4: Windows Recovery 450M

              I’m thinking the 15G partition in your layout is the OEM windows recovery stuff.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              1 Reply Last reply Reply Quote 0
              • A
                abos_systemax @Quazz
                last edited by Dec 15, 2016, 2:26 PM

                @Quazz
                After that, I receive an I/O error:4 from fatclone.c

                message: Fatclone.c: I/O error:4

                Q 1 Reply Last reply Dec 15, 2016, 2:27 PM Reply Quote 0
                • Q
                  Quazz Moderator @abos_systemax
                  last edited by Dec 15, 2016, 2:27 PM

                  @abos_systemax Imo, this indicates that the drive itself has issues, bad sectors most likely.

                  A 1 Reply Last reply Dec 16, 2016, 7:26 AM Reply Quote 1
                  • W
                    Wayne Workman
                    last edited by Dec 16, 2016, 1:00 AM

                    I’m thinking the same thing Quazz is. Often it is very helpful to try with a different machine, a different drive, a fresh build of an image, even starting out with a zeroed-out hdd would help. FOG has a normal-wipe feature built-in that would do the job of blanking a disk.

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                    Daily Clean Installation Results:
                    https://fogtesting.fogproject.us/
                    FOG Reporting:
                    https://fog-external-reporting-results.fogproject.us/

                    1 Reply Last reply Reply Quote 0
                    • A
                      abos_systemax @Quazz
                      last edited by Dec 16, 2016, 7:26 AM

                      @Quazz There are options to capture only certain partitions; is there a method to SKIP certain partitions?
                      I am able to capture SDA2,SDA3 and SDA4 with no problem

                      W 1 Reply Last reply Dec 16, 2016, 2:11 PM Reply Quote 0
                      • W
                        Wayne Workman @abos_systemax
                        last edited by Dec 16, 2016, 2:11 PM

                        @abos_systemax You could capture each of those partitions to their own image, then via terminal you could put them all together into a new image’s directory manually. The required support files for it can be copied from another similar image and then modified. Final step being to create an image definition for it in the web interface and trying it out.

                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                        Daily Clean Installation Results:
                        https://fogtesting.fogproject.us/
                        FOG Reporting:
                        https://fog-external-reporting-results.fogproject.us/

                        A 1 Reply Last reply Dec 21, 2016, 11:04 AM Reply Quote 0
                        • A
                          abos_systemax @Wayne Workman
                          last edited by Dec 21, 2016, 11:04 AM

                          @Wayne-Workman can I just use the MBR that is created on the image?

                          A W 2 Replies Last reply Dec 21, 2016, 12:48 PM Reply Quote 0
                          • A
                            abos_systemax @abos_systemax
                            last edited by Dec 21, 2016, 12:48 PM

                            @abos_systemax

                            Meh, too bad… if I only restore partitions 2,3, and 4, I receive a Windows needs to be repared error because the Win10 EFI Boot manager still thinks it boots Windows 10…

                            The FOG screen displays a message about formatting and settingup the new MBR/GPT… but it doesnt seem to do that; is that correct?

                            1 Reply Last reply Reply Quote 0
                            • W
                              Wayne Workman @abos_systemax
                              last edited by Dec 21, 2016, 2:09 PM

                              @abos_systemax said in Fatclone.C: Filesystem isn't in a valid state:

                              @Wayne-Workman can I just use the MBR that is created on the image?

                              That’s what I would try first. It’s just a file in the image’s directory, easy enough to replace.

                              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                              Daily Clean Installation Results:
                              https://fogtesting.fogproject.us/
                              FOG Reporting:
                              https://fog-external-reporting-results.fogproject.us/

                              A 1 Reply Last reply Dec 21, 2016, 3:23 PM Reply Quote 0
                              • A
                                abos_systemax @Wayne Workman
                                last edited by abos_systemax Dec 21, 2016, 10:39 AM Dec 21, 2016, 3:23 PM

                                @Wayne-Workman I tried, but Windows is unable to launch.
                                I am wiping the disk now to ensure that the EFI partition is removed before the image is applied

                                But alas, it is still unable to find the OS disk

                                W 1 Reply Last reply Dec 21, 2016, 11:13 PM Reply Quote 0
                                • W
                                  Wayne Workman @abos_systemax
                                  last edited by Dec 21, 2016, 11:13 PM

                                  @abos_systemax 7 days into this, I would recommend cutting the losses and rebuilding the image. Don’t go 100% on the new image, just install base-windows only and try capturing. Adjust the firmware settings as needed until you get the image to capture. Once you can successfully capture, then complete your image and capture again.

                                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                                  Daily Clean Installation Results:
                                  https://fogtesting.fogproject.us/
                                  FOG Reporting:
                                  https://fog-external-reporting-results.fogproject.us/

                                  A 1 Reply Last reply Dec 22, 2016, 7:07 AM Reply Quote 0
                                  • A
                                    abos_systemax @Wayne Workman
                                    last edited by Dec 22, 2016, 7:07 AM

                                    @Wayne-Workman Problem is: our customers build their images and we have to work with it… Ill still try to figure things out; but this thread can be closed. Apparently it’s not a FOG issue, it’s a hardware (or software) related issue; which doesn’t fall into Fog’s domain…

                                    Thanks for the support anyway; you did point me in the right direction: at least now I know what the problem is.

                                    W 1 Reply Last reply Dec 22, 2016, 4:52 PM Reply Quote 0
                                    • W
                                      Wayne Workman @abos_systemax
                                      last edited by Dec 22, 2016, 4:52 PM

                                      @abos_systemax Well as a last resort, use the RAW image type. But beware it takes a complete and uncompressed image. So if you capture a 2TB disk, you get a image that is 2TB in size.

                                      But I do think there is an issue with the image and I do believe that zero-ing the disk prior to a re-install would most likely work.

                                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                                      Daily Clean Installation Results:
                                      https://fogtesting.fogproject.us/
                                      FOG Reporting:
                                      https://fog-external-reporting-results.fogproject.us/

                                      A 1 Reply Last reply Dec 23, 2016, 7:24 AM Reply Quote 0
                                      • A
                                        abos_systemax @Wayne Workman
                                        last edited by Dec 23, 2016, 7:24 AM

                                        @Wayne-Workman

                                        I kind-a-fixed it by booting to Windows PE, clean the disk with diskpart, create a 100MB parititon and a ‘the rest’ partition; then restoring only partition 2 with FOG, then rebooting to Windows PE to create a bootstore… now Windows can Boot.

                                        I now face another issue, but I’ve posted that in the Windows Issues forums (https://forums.fogproject.org/topic/9177/windows-partition-size)

                                        A 1 Reply Last reply Dec 23, 2016, 10:02 AM Reply Quote 0
                                        • A
                                          abos_systemax @abos_systemax
                                          last edited by Dec 23, 2016, 10:02 AM

                                          @abos_systemax said in Fatclone.C: Filesystem isn't in a valid state:

                                          @Wayne-Workman

                                          I kind-a-fixed it by booting to Windows PE, clean the disk with diskpart, create a 100MB parititon and a ‘the rest’ partition; then restoring only partition 2 with FOG, then rebooting to Windows PE to create a bootstore… now Windows can Boot.

                                          I now face another issue, but I’ve posted that in the Windows Issues forums (https://forums.fogproject.org/topic/9177/windows-partition-size)

                                          — fixed that issue as well…

                                          1 Reply Last reply Reply Quote 0
                                          • 1
                                          • 2
                                          • 1 / 2
                                          1 / 2
                                          • First post
                                            13/23
                                            Last post

                                          190

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project