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

    Hard Drive, SSD, & M.2

    Scheduled Pinned Locked Moved Unsolved
    FOG Problems
    6
    39
    4.4k
    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

      @george1421

      fdisk -l returns all the ram. no ssd.

      Im not sure about the raid yet. I’m still looking into if there is one built in. There is no stand alone card as far as I can tell.

      The disk is functional it has windows 10 pre installed which I am able to boot into.

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

        Integrated Intel AHCI SATA chipset controller (8x 6.0Gb/s), SW RAID 0,1,5,10

        Looks like a software raid controller which all my current dells have.

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

          @breit I guess the next step here is for you to download fedora and “burn” to a flash drive. Boot it live (no install needed) then open a command window and do the lsblk bit. You should see the usb flash drive, but hopefully also the nvme drive.

          One other thought, I know you just purchased them, but is the firmware up to date.

          Also if you put the device in legacy(bios) mode do we have any better luck with seeing the nvme disk.

          Sorry about all of these random thoughts, but the issue has to be somewhere. So we need to find out where it isn’t to narrow it down to where it might be.

          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 i appreciate the help the firmware is upto date. I will try fedora and get back to you. even with legacy mode same error message.

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

              I can confirm that Fedora does see the drive

              0_1524078010423_ac7674cc-38e7-475e-b192-0a18ecdfbd7c-image.png

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

                @breit Well on the plus side, we now know its possible to image that computer. The down side is understanding why is going to take a bit more time to decipher.

                On your fog server, from a linux console change to /var/www/html/fog/service/ipxe directory. Then key in file bzImage this will tell us the version of the linux kernel you are sending to that target computer.

                Also under fedora if you could run the lspci command with this syntax lspci -knn This will list all pci devices with the linux kernel driver that talks to the hardware. Lastly if you could upload the file /var/log/messages to a google drive so I could review it, that would be handy.

                I would also like to see the /var/log/messages (or /var/log/syslog) from FOS booted in debug mode from this hardware too. This will allow us to compare what fedora is doing vs what FOS is doing during boot time regarding that hardware.

                I’m pretty sure we can get this working for you, we just need to understand why is there a difference between fedora (with an older linux kernel) and FOS.

                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
                  BzImage info:

                  bzImage: Linux kernel x86 boot executable bzImage, version 4.15.2 (builder@c38bc 0acaeb4) #5 SMP Tue Feb 13 18:30:08 UTC 20, RO-rootFS, swap_dev 0x7, Normal VGA

                  lspci -knn info:

                  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake-E DMI3 Registers [8086:2020] (rev 04)
	Subsystem: Dell Device [1028:0738]
00:04.0 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: ioatdma
	Kernel modules: ioatdma
00:04.1 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: ioatdma
	Kernel modules: ioatdma
00:04.2 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: ioatdma
	Kernel modules: ioatdma
00:04.3 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: ioatdma
	Kernel modules: ioatdma
00:04.4 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: ioatdma
	Kernel modules: ioatdma
00:04.5 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: ioatdma
	Kernel modules: ioatdma
00:04.6 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: ioatdma
	Kernel modules: ioatdma
00:04.7 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: ioatdma
	Kernel modules: ioatdma
00:05.0 System peripheral [0880]: Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers [8086:2024] (rev 04)
	Subsystem: Dell Device [1028:0738]
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)
	Subsystem: Dell Device [1028:0738]
00:08.0 System peripheral [0880]: Intel Corporation Sky Lake-E Ubox Registers [8086:2014] (rev 04)
	Subsystem: Dell Device [1028:0738]
00:08.1 Performance counters [1101]: Intel Corporation Sky Lake-E Ubox Registers [8086:2015] (rev 04)
	Subsystem: Dell Device [1028:0738]
00:08.2 System peripheral [0880]: Intel Corporation Sky Lake-E Ubox Registers [8086:2016] (rev 04)
	Subsystem: Dell Device [1028:0738]
00:14.0 USB controller [0c03]: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller [8086:a2af]
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller [1180]: Intel Corporation 200 Series PCH Thermal Subsystem [8086:a2b1]
	Subsystem: Dell Device [1028:0738]
00:16.0 Communication controller [0780]: Intel Corporation 200 Series PCH CSME HECI #1 [8086:a2ba]
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA controller [AHCI mode] [8086:a282]
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #1 [8086:a290] (rev f0)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.6 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #7 [8086:a296] (rev f0)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a2d3]
	Subsystem: Dell Device [1028:0738]
00:1f.2 Memory controller [0580]: Intel Corporation 200 Series PCH PMC [8086:a2a1]
	Subsystem: Dell Device [1028:0738]
00:1f.3 Audio device [0403]: Intel Corporation 200 Series PCH HD Audio [8086:a2f0]
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1f.4 SMBus [0c05]: Intel Corporation 200 Series PCH SMBus Controller [8086:a2a3]
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (5) I219-LM [8086:15e3]
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: e1000e
	Kernel modules: e1000e
02:00.0 PCI bridge [0604]: Texas Instruments XIO2001 PCI Express-to-PCI Bridge [104c:8240]
	Kernel modules: shpchp
16:05.0 System peripheral [0880]: Intel Corporation Device [8086:2034] (rev 04)
	Subsystem: Dell Device [1028:0738]
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)
	Subsystem: Dell Device [1028:0738]
16:08.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:08.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:08.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:08.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:08.4 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:08.5 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:08.6 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:08.7 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:09.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:09.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0e.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0e.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0e.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0e.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0e.4 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0e.5 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0e.6 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0e.7 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0f.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:0f.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1d.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2054] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1d.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2055] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1d.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2056] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1d.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2057] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1e.0 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2080] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1e.1 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2081] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1e.2 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2082] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1e.3 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2083] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1e.4 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2084] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1e.5 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2085] (rev 04)
	Subsystem: Dell Device [1028:0738]
16:1e.6 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2086] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:00.0 PCI bridge [0604]: Intel Corporation Sky Lake-E PCI Express Root Port A [8086:2030] (rev 04)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
64:05.0 System peripheral [0880]: Intel Corporation Device [8086:2034] (rev 04)
	Subsystem: Dell Device [1028:0738]
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)
	Subsystem: Dell Device [1028:0738]
64:08.0 System peripheral [0880]: Intel Corporation Device [8086:2066] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
64:09.0 System peripheral [0880]: Intel Corporation Device [8086:2066] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
64:0a.0 System peripheral [0880]: Intel Corporation Device [8086:2040] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0a.1 System peripheral [0880]: Intel Corporation Device [8086:2041] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0a.2 System peripheral [0880]: Intel Corporation Device [8086:2042] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
64:0a.3 System peripheral [0880]: Intel Corporation Device [8086:2043] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0a.4 System peripheral [0880]: Intel Corporation Device [8086:2044] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0a.5 System peripheral [0880]: Intel Corporation Device [8086:2045] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0a.6 System peripheral [0880]: Intel Corporation Device [8086:2046] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
64:0a.7 System peripheral [0880]: Intel Corporation Device [8086:2047] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0b.0 System peripheral [0880]: Intel Corporation Device [8086:2048] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0b.1 System peripheral [0880]: Intel Corporation Device [8086:2049] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0b.2 System peripheral [0880]: Intel Corporation Device [8086:204a] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
64:0b.3 System peripheral [0880]: Intel Corporation Device [8086:204b] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0c.0 System peripheral [0880]: Intel Corporation Device [8086:2040] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0c.1 System peripheral [0880]: Intel Corporation Device [8086:2041] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0c.2 System peripheral [0880]: Intel Corporation Device [8086:2042] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
64:0c.3 System peripheral [0880]: Intel Corporation Device [8086:2043] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0c.4 System peripheral [0880]: Intel Corporation Device [8086:2044] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0c.5 System peripheral [0880]: Intel Corporation Device [8086:2045] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0c.6 System peripheral [0880]: Intel Corporation Device [8086:2046] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
64:0c.7 System peripheral [0880]: Intel Corporation Device [8086:2047] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0d.0 System peripheral [0880]: Intel Corporation Device [8086:2048] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0d.1 System peripheral [0880]: Intel Corporation Device [8086:2049] (rev 04)
	Subsystem: Dell Device [1028:0738]
64:0d.2 System peripheral [0880]: Intel Corporation Device [8086:204a] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
64:0d.3 System peripheral [0880]: Intel Corporation Device [8086:204b] (rev 04)
	Subsystem: Dell Device [1028:0738]
65:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107GL [Quadro P600] [10de:1cb2] (rev a1)
	Subsystem: Dell Device [1028:11bd]
	Kernel driver in use: nouveau
	Kernel modules: nouveau
65:00.1 Audio device [0403]: NVIDIA Corporation GP107GL High Definition Audio Controller [10de:0fb9] (rev a1)
	Subsystem: Dell Device [1028:11bd]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
b2:02.0 PCI bridge [0604]: Intel Corporation Sky Lake-E PCI Express Root Port C [8086:2032] (rev 04)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
b2:03.0 PCI bridge [0604]: Intel Corporation Sky Lake-E PCI Express Root Port D [8086:2033] (rev 04)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
b2:05.0 System peripheral [0880]: Intel Corporation Device [8086:2034] (rev 04)
	Subsystem: Dell Device [1028:0738]
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)
	Subsystem: Dell Device [1028:0738]
b2:12.0 Performance counters [1101]: Intel Corporation Sky Lake-E M3KTI Registers [8086:204c] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
b2:12.1 Performance counters [1101]: Intel Corporation Sky Lake-E M3KTI Registers [8086:204d] (rev 04)
	Subsystem: Dell Device [1028:0738]
	Kernel driver in use: skx_uncore
b2:12.2 System peripheral [0880]: Intel Corporation Sky Lake-E M3KTI Registers [8086:204e] (rev 04)
	Subsystem: Dell Device [1028:0738]
b2:15.0 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04)
	Subsystem: Dell Device [1028:0738]
b2:16.0 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04)
	Subsystem: Dell Device [1028:0738]
b2:16.4 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04)
	Subsystem: Dell Device [1028:0738]
b2:17.0 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04)
b3:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 [144d:a804]
	Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
	Kernel driver in use: nvme
	Kernel modules: nvme
                  1 Reply Last reply Reply Quote 0
                  • B
                    BREIT
                    last edited by

                    /var/log/message Here

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

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

                      b3:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 [144d:a804]
                      Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
                      Kernel driver in use: nvme
                      Kernel modules: nvme

                      I haven’t done a full comparison of the two lspci files yet but just a quick look the last line above is missing from the FOG lspci data. Maybe its not loading that controller and Fedora is?

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

                        @george1421

                        Any ideas on how to get this working?

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

                          The times that I’ve hard of this the sata operation mode was setup as raid. From what I’m gathering, your sata operation mode is setup for AHCI? So I am really at a loss.

                          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

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

                            After even more digging. There is something hardware related that FOG doesn’t like or isn’t seeing. I put the SED drive into a MMF Dell 7050 and it started imaging without any issues. Maybe its the new quick swap device on it?

                            I will add due to hardware differences the image crashed upon loading into windows 7 (Yeah I know windows 7)

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

                              @BREIT Well then I’d expect the controller being the issue here - not the disk itself. Can you please try setting nvme_load=YES as kernel option in the client’s host settings and try again?

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

                                @sebastian-roth said in Hard Drive, SSD, & M.2:

                                nvme_load=YES

                                Sorry I need a little clarification, I go to the host on the web interface and type in nvme_load=YES in the Host Kernel Arguments?

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

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

                                  I go to the host on the web interface and type in nvme_load=YES in the Host Kernel Arguments?

                                  Yeah, exactly. Then try booting the client again and see if it can find the drive.

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

                                    @Sebastian-Roth

                                    That did not work. Same error message comes up.

                                    I did notice this line when booting kernel

                                    populating /dev using udev: udevd[[3096]: error creating epoll fd: Function not implemented
                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      BREIT
                                      last edited by BREIT

                                      Hey guys. So I’ve attempted to register a computer this morning with a m.2 hard drive and got the same error message. Just wanted to pass that information along.

                                      I overlooked switching to ACHI on this computer. DOH!

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

                                        @breit What model of hardware is in question?

                                        Also fog is at 1.5.2 with the kernels at 4.16.6. I’m not suggesting that either will fix your issues. Just letting you know there is newer stuff out there. I might hold off on updating FOG until 1.5.3 is released since there are a few annoyances in 1.5.2, but see if the newer kernel finds this nvme drive.

                                        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
                                        • T
                                          Taspharel
                                          last edited by

                                          Just throwing this out there, might absolutely not be related and me just missunderstanding whats actually happening here.

                                          I had problems Imaging a computer at point when switching from a hdd machine as image-source to an ssd.

                                          I had to change the host primary disk to the correct one - I think from sda to sda2 or something along those lines - for this to work.

                                          Rereading again I suppose this is in another direction, but just in case.

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

                                          179

                                          Online

                                          11.7k

                                          Users

                                          17.2k

                                          Topics

                                          154.7k

                                          Posts
                                          Copyright © 2012-2024 FOG Project