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

    Hard Drive, SSD, & M.2

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    6
    39
    4.8k
    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.
    • B
      BREIT
      last edited by BREIT

      I think that I may have found a bug but wanted to see if anyone else was having this same issue. I have captured an image from a M.2 hard drive and it will install fine on other M.2 hard drives, but when I attempt to install the same image on a SSD or SATA HDD, I get “It appears the hard drive is empty. This may cause problems” , to which the clone of the image to fails. I’ve done this on 3 different computers as soon as put an M.2 Hard drive in the computer it images without any issues. Would the type of the hard drive cause this issue?

      Edit: Running on 1.5.0

      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
      • Wayne WorkmanW
        Wayne Workman @BREIT
        last edited by

        @breit FOG Version please.

        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/

        B 1 Reply Last reply Reply Quote 0
        • B
          BREIT @Wayne Workman
          last edited by

          @wayne-workman 1.5.0

          1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator
            last edited by george1421

            Also for the developers. Can you post the contents of d1.partitions and d1.fixed_size_partitions of the source image?

            I can say that the naming convention between a sata and m.2 interfaces are different. I’m not sure if that would cause the error you mentioned. I might expect the target disk size to be an issue before naming.

            I can also say its best practices to use a VM to create your reference images. That way it removes all hardware dependencies. But I also understand that circumstances dictate how you can do things.

            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!

            B 1 Reply Last reply Reply Quote 0
            • B
              BREIT @george1421
              last edited by

              @george1421

              d1.partitions

              label: gpt
label-id: F68C4898-B2D7-470A-920F-086D2F844D71
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/nvme0n1p1 : start=        2048, size=     1024000, type=C12A7328-F81F-11D2$
/dev/nvme0n1p2 : start=     1026048, size=      262144, type=E3C9E316-0B5C-4DB8$
/dev/nvme0n1p3 : start=     1288192, size=   240150076, type=EBD0A0A2-B9E5-4433$
/dev/nvme0n1p4 : start=   479285248, size=     1742848, type=DE94BBA4-06D1-4D40$
/dev/nvme0n1p5 : start=   481028096, size=    19087360, type=DE94BBA4-06D1-4D40$

              d1.fixed.size.partitions

              :1:2
              george1421G 1 Reply Last reply Reply Quote 1
              • george1421G
                george1421 Moderator @BREIT
                last edited by

                @breit said in Hard Drive, SSD, & M.2:

                So for clarity you are capturing a ~256GB NVMe disk and deploying to a SATA disk of a larger size?

                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!

                B 1 Reply Last reply Reply Quote 0
                • B
                  BREIT @george1421
                  last edited by

                  @george1421

                  Yes that is correct. The image is 81GB.

                  george1421G 1 Reply Last reply Reply Quote 0
                  • george1421G
                    george1421 Moderator @BREIT
                    last edited by george1421

                    @breit That’s not exactly what I was asking (but good info none the less). I wanted to ensure that the target drive is larger than the nvme drive where you captured the image to. I understand you picked single disk resizable, I want to ensure that you’ve tried to deploy the image to a SATA disk larger than the source 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!

                    1 Reply Last reply Reply Quote 0
                    • B
                      BREIT
                      last edited by

                      Yes, sorry I was confirming what you asked and added the image size for reference as well. I tired on a 1TB drive with the same results. It was a SATA HDD.

                      Tom ElliottT 1 Reply Last reply Reply Quote 1
                      • Tom ElliottT
                        Tom Elliott @BREIT
                        last edited by

                        @breit if I had to guess, the bios sata operation mode is set as raid rather than ahci

                        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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                        B 1 Reply Last reply Reply Quote 0
                        • S
                          Sebastian Roth Moderator
                          last edited by Sebastian Roth

                          Either that or we have different block size disks, 512 vs. 4096

                          @BREIT Please schedule a deploy or capture task as debug and run fdisk -l /dev/nvme0n1 when you get to the shell. Do this with all the different types of disk you have, take pictures and post those here.

                          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                          1 Reply Last reply Reply Quote 2
                          • george1421G
                            george1421 Moderator
                            last edited by george1421

                            slighly off point post, but recording for reference.

                            MBR 512n

                            Disk /dev/sda: 17.2 GB, 17179869184 bytes, 33554432 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00006e8c

                            GPT 512n

                            Disk /dev/sda: 36003.6 GB, 36003637100544 bytes, 70319603712 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
Disk identifier: 3DAC1844-EDDA-43CD-9334-E0F3515F0AC7

                            MBR 512e

                            Disk /dev/sda: 1098.4 GB, 1098437885952 bytes, 2145386496 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

                            4Kn

                            Disk /dev/sda: 999.0 GB, 998997229568 bytes, 243895808 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: gpt
Disk identifier: 4CD4D7DC-B85C-47B5-A8D0-BCFA2345A58D

                            I’m sure there is a better way…

                            fdisk -l /dev/sda|grep -e "Sector size"|awk '{print $4, $7}'

                            There is

                            fdisk -l /dev/sda|awk '/Sector size/{print $4, $7}'

                            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 1
                            • B
                              BREIT @Tom Elliott
                              last edited by

                              @tom-elliott

                              It was set to ACHI. I even tried ATA for kicks on one of my older computers. All but that one test was in ACHI.

                              @Sebastian-Roth

                              I’ll start on that now and get back with you all.

                              1 Reply Last reply Reply Quote 0
                              • B
                                BREIT
                                last edited by

                                So after some more testing. It seems its something with the micro form factor m.2 is causing the issues. @george1421 suggested using VMs to build our images. Something honestly I hadn’t thought of. Since changing to that methodology we haven’t had any issues imaging. It is defiantly something hardware based that wasn’t jiving with the different computers hard drives and imaging with fog.

                                1 Reply Last reply Reply Quote 1
                                • B
                                  BREIT
                                  last edited by

                                  Just when I that all was fine it, it is not. We have received new computers Precision 5820’s from Dell. They have a SAS type ssd in them. Fog is unable to locate the hard drive it seems. I did update the server to 1.5.2 yesterday. Any ideas? The image was built in a VM.

                                  0_1524058745760_9298e059-bede-4bf8-abcd-7390fd02b86b-image.png

                                  pretty rad looking ssd. I haven’t seen one of these before. Sharpie is for size reference.

                                  0_1524058968196_760229ca-f41c-4707-8ae6-23d0b1fdab36-image.png

                                  1 Reply Last reply Reply Quote 0
                                  • B
                                    BREIT
                                    last edited by

                                    Let me add that prior to the update to 1.5.2 this was the error I was getting

                                    failed to set aspt feature -19 FOG
                                    george1421G 1 Reply Last reply Reply Quote 0
                                    • george1421G
                                      george1421 Moderator @BREIT
                                      last edited by

                                      @breit This bleeding edge stuff is going to be the death of the developers.

                                      We need to collect some information on that system. It would be quicker if I could do it over teamviewer (if you have that option). If not you can do it.

                                      1. Register this computer with fog (already done I suspect)
                                      2. Schedule a capture or deploy doesn’t matter, but before you hit submit, select the debug check box and submit the task.
                                      3. pxe boot the target computer
                                      4. After a few enter key presses you will be dropped to a linux console on the target computer.
                                      5. Key in ip addr show to get the IP address of the target computer, record that for the following steps.
                                      6. Reset root’s password by issuing this command passwd and then give it a simple password like hello
                                      7. Now use putty and connect to the target computer using the IP address you collected in #5. Login using user root and the password you set in #6.
                                      8. Once logged in then issue the lsblk cmd. (hint: because we putty you can copy a paste text between FOS and your computer).
                                      9. Post the results of lstblk command here.
                                      10. Key in the following command lspci -nn and post the results here.
                                      11. Now review the log file /var/log/message You need to look for messages related to the disk controller.

                                      We need to collect as much information as possible. Just be aware that the fog project is limited on hardware support because of the linux kernel. That’s not a negative thing, its just FOG can’t clone where there isn’t a drive created yet in the Linux kernel. The info you collect here will allow us to monitor the linux project to see when they add support for this new NVME (SAS) disk (my words not what they are officially called just yet).

                                      Also could you collect from the bios what this disk is called or a manufacturer part number (not dells)? That would help us back track into what that device is.

                                      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
                                      • B
                                        BREIT
                                        last edited by

                                        @george1421

                                        lsblk :
                                        Returned nothing
                                        lspci -nn:

                                        00:00.0 Host bridge [0600]: Intel Corporation Device [8086:2020] (rev 04)
00:04.0 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
00:04.1 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
00:04.2 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
00:04.3 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
00:04.4 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
00:04.5 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
00:04.6 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
00:04.7 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
00:05.0 System peripheral [0880]: Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers [8086:2024] (rev 04)
00:05.2 System peripheral [0880]: Intel Corporation Device [8086:2025] (rev 04)
00:05.4 PIC [0800]: Intel Corporation Device [8086:2026] (rev 04)
00:08.0 System peripheral [0880]: Intel Corporation Sky Lake-E Ubox Registers [8086:2014] (rev 04)
00:08.1 Performance counters [1101]: Intel Corporation Sky Lake-E Ubox Registers [8086:2015] (rev 04)
00:08.2 System peripheral [0880]: Intel Corporation Sky Lake-E Ubox Registers [8086:2016] (rev 04)
00:14.0 USB controller [0c03]: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller [8086:a2af]
00:14.2 Signal processing controller [1180]: Intel Corporation 200 Series PCH Thermal Subsystem [8086:a2b1]
00:16.0 Communication controller [0780]: Intel Corporation 200 Series PCH CSME HECI #1 [8086:a2ba]
00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA controller [AHCI mode] [8086:a282]
00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #1 [8086:a290] (rev f0)
00:1c.6 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #7 [8086:a296] (rev f0)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a2d3]
00:1f.2 Memory controller [0580]: Intel Corporation 200 Series PCH PMC [8086:a2a1]
00:1f.3 Audio device [0403]: Intel Corporation 200 Series PCH HD Audio [8086:a2f0]
00:1f.4 SMBus [0c05]: Intel Corporation 200 Series PCH SMBus Controller [8086:a2a3]
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (5) I219-LM [8086:15e3]
02:00.0 PCI bridge [0604]: Texas Instruments XIO2001 PCI Express-to-PCI Bridge [104c:8240]
16:05.0 System peripheral [0880]: Intel Corporation Device [8086:2034] (rev 04)
16:05.2 System peripheral [0880]: Intel Corporation Sky Lake-E RAS Configuration Registers [8086:2035] (rev 04)
16:05.4 PIC [0800]: Intel Corporation Device [8086:2036] (rev 04)
16:08.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:08.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:08.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:08.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:08.4 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:08.5 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:08.6 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:08.7 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:09.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:09.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
16:0e.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:0e.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:0e.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:0e.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:0e.4 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:0e.5 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:0e.6 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:0e.7 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:0f.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:0f.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
16:1d.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2054] (rev 04)
16:1d.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2055] (rev 04)
16:1d.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2056] (rev 04)
16:1d.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2057] (rev 04)
16:1e.0 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2080] (rev 04)
16:1e.1 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2081] (rev 04)
16:1e.2 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2082] (rev 04)
16:1e.3 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2083] (rev 04)
16:1e.4 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2084] (rev 04)
16:1e.5 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2085] (rev 04)
16:1e.6 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2086] (rev 04)
64:00.0 PCI bridge [0604]: Intel Corporation Sky Lake-E PCI Express Root Port A [8086:2030] (rev 04)
64:05.0 System peripheral [0880]: Intel Corporation Device [8086:2034] (rev 04)
64:05.2 System peripheral [0880]: Intel Corporation Sky Lake-E RAS Configuration Registers [8086:2035] (rev 04)
64:05.4 PIC [0800]: Intel Corporation Device [8086:2036] (rev 04)
64:08.0 System peripheral [0880]: Intel Corporation Device [8086:2066] (rev 04)
64:09.0 System peripheral [0880]: Intel Corporation Device [8086:2066] (rev 04)
64:0a.0 System peripheral [0880]: Intel Corporation Device [8086:2040] (rev 04)
64:0a.1 System peripheral [0880]: Intel Corporation Device [8086:2041] (rev 04)
64:0a.2 System peripheral [0880]: Intel Corporation Device [8086:2042] (rev 04)
64:0a.3 System peripheral [0880]: Intel Corporation Device [8086:2043] (rev 04)
64:0a.4 System peripheral [0880]: Intel Corporation Device [8086:2044] (rev 04)
64:0a.5 System peripheral [0880]: Intel Corporation Device [8086:2045] (rev 04)
64:0a.6 System peripheral [0880]: Intel Corporation Device [8086:2046] (rev 04)
64:0a.7 System peripheral [0880]: Intel Corporation Device [8086:2047] (rev 04)
64:0b.0 System peripheral [0880]: Intel Corporation Device [8086:2048] (rev 04)
64:0b.1 System peripheral [0880]: Intel Corporation Device [8086:2049] (rev 04)
64:0b.2 System peripheral [0880]: Intel Corporation Device [8086:204a] (rev 04)
64:0b.3 System peripheral [0880]: Intel Corporation Device [8086:204b] (rev 04)
64:0c.0 System peripheral [0880]: Intel Corporation Device [8086:2040] (rev 04)
64:0c.1 System peripheral [0880]: Intel Corporation Device [8086:2041] (rev 04)
64:0c.2 System peripheral [0880]: Intel Corporation Device [8086:2042] (rev 04)
64:0c.3 System peripheral [0880]: Intel Corporation Device [8086:2043] (rev 04)
64:0c.4 System peripheral [0880]: Intel Corporation Device [8086:2044] (rev 04)
64:0c.5 System peripheral [0880]: Intel Corporation Device [8086:2045] (rev 04)
64:0c.6 System peripheral [0880]: Intel Corporation Device [8086:2046] (rev 04)
64:0c.7 System peripheral [0880]: Intel Corporation Device [8086:2047] (rev 04)
64:0d.0 System peripheral [0880]: Intel Corporation Device [8086:2048] (rev 04)
64:0d.1 System peripheral [0880]: Intel Corporation Device [8086:2049] (rev 04)
64:0d.2 System peripheral [0880]: Intel Corporation Device [8086:204a] (rev 04)
64:0d.3 System peripheral [0880]: Intel Corporation Device [8086:204b] (rev 04)
65:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107GL [Quadro P600] [10de:1cb2] (rev a1)
65:00.1 Audio device [0403]: NVIDIA Corporation GP107GL High Definition Audio Controller [10de:0fb9] (rev a1)
b2:02.0 PCI bridge [0604]: Intel Corporation Sky Lake-E PCI Express Root Port C [8086:2032] (rev 04)
b2:03.0 PCI bridge [0604]: Intel Corporation Sky Lake-E PCI Express Root Port D [8086:2033] (rev 04)
b2:05.0 System peripheral [0880]: Intel Corporation Device [8086:2034] (rev 04)
b2:05.2 System peripheral [0880]: Intel Corporation Sky Lake-E RAS Configuration Registers [8086:2035] (rev 04)
b2:05.4 PIC [0800]: Intel Corporation Device [8086:2036] (rev 04)
b2:12.0 Performance counters [1101]: Intel Corporation Sky Lake-E M3KTI Registers [8086:204c] (rev 04)
b2:12.1 Performance counters [1101]: Intel Corporation Sky Lake-E M3KTI Registers [8086:204d] (rev 04)
b2:12.2 System peripheral [0880]: Intel Corporation Sky Lake-E M3KTI Registers [8086:204e] (rev 04)
b2:15.0 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04)
b2:16.0 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04)
b2:16.4 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04)
b2:17.0 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04)

                                        The SSD is a NVMe SED Samsung 512GB. Its just an M2 in a fancy case.

                                        george1421G 1 Reply Last reply Reply Quote 0
                                        • george1421G
                                          george1421 Moderator @BREIT
                                          last edited by

                                          @breit said in Hard Drive, SSD, & M.2:

                                          SATA controller [0106]: Intel Corporation 200 Series PCH SATA controller [AHCI mode] [8086:a282]

                                          Well this tells me that you have the disk controller in ahci mode. If this is a standard m.2 nvme disk it should see it.

                                          I assume that fdisk -l also returns nothing?

                                          Is this nvme disk behind a raid controller or something we are not expecting?

                                          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
                                          • george1421G
                                            george1421 Moderator
                                            last edited by

                                            I’m also wondering if we had you live boot a bleeding edge OS like fedora, can fedora see the disk in this system?

                                            Can we assume that the disk is functional (yes I know its new)? We are missing something here…

                                            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
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post

                                            162

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project