Problems with disk controler

TBouapi · Mar 21, 2019, 11:06 AM

Bonjour,
je rencontre actuellement un problème avec un nouveau type d’ordinateur que nous venons d’acquérir.
En effet, il me semble que le contrôleur de disque nvme n’est pas reconnu.

Le matériel en question est un Alienware aurora R7
il est équipé d’un disque nvme ainsi que d’un disque à plateaux.

J’arrive à capturer le disque à plateaux, cependant le disque nvme n’est pas capturé.
J’ai booté sur un live cd linux et je ne vois que le disque à plateaux.
Afin de voir les disques présents sur ma machine j’utilise la commande fdisk -l.

Hello,
I’ve actually a problem with the new type of computer that we have just buy.
Indeed, it seems the disk controler nvme is not recognized.

The device is an AlienWare Aurora R7.
This device have a classical hard disk and a nvme disk.

I can capture the classical hard disk of my machine, however the nvme disk are not captured.
I have booted on a live cd linux and i can only see the classical hard disk. The nvme disk does not appear.
To see the hard disk present on my device i use the command fdisk -l.

george1421 · Mar 26, 2019, 9:32 AM

@nsmer Ok since you have a dell and I noticed the disk controller is in Raid-On mode, will you look in the bios settings? Look for a setting that says disk controller. There are typically 2 or 3 modes (On Dell Latitude models) One is AHCI and the other is Raid-On. If you see this setting change the disk mode to ahci mode for testing. See if both clonezilla and FOG see the disk then. There is a known problem with the target computer being in uefi mode with Raid-On and linux.

george1421 · Mar 21, 2019, 11:46 AM

Greetings,

Can you tell me

What version of FOG you are using?
What FOS kernel are you using?
Can you tell me the results of this action?
a. Schedule a image deployment to this computer. Before you click on the schedule task button select the debug option then schedule the task.
b. PXE boot the target computer. After a few keyboard Enter key presses you will arrive at a linux command prompt.
c. At the FOS command prompt key in lsblk. Post the results here. A clear picture taken with a mobile phone is good.
d. Also on the FOS command prompt key in grep nvme /var/log/messages (I guessed at the log file name, it may be syslog instead of messages). Post the results here.

nsmer · Mar 25, 2019, 7:30 AM

Hi I’m working with TBouapi

the fog version is the 1.5.5
what is FOS ?
waiting to know what is FOS to do it

some more informations if it can help

on the lastest clonezilla the return of fdisk -l

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-75W
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 37131568-7109-4D43-A130-6E9E0DF159DE

Device      Start        End    Sectors   Size Type
/dev/sda1    2048     264191     262144   128M Microsoft reserved
/dev/sda2  264192 1953523711 1953259520 931.4G Microsoft basic data




Disk /dev/sdb: 982 MiB, 1029701632 bytes, 2011136 sectors
Disk model: MEMUP           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe32ae32a

Device     Boot Start     End Sectors   Size Id Type
/dev/sdb1  *       63 2008124 2008062 980.5M  b W95 FAT32


Disk /dev/sdc: 1.4 MiB, 1474560 bytes, 2880 sectors
Disk model: MEMUP           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x69737369

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdc1       1869771365 2038460886  168689522  80.4G 69 unknown
/dev/sdc2       1701519481 3571400945 1869881465 891.6G 73 unknown
/dev/sdc3             2573       2573          0     0B 74 unknown
/dev/sdc4                0 3435113471 3435113472   1.6T  7 HPFS/NTFS/exFAT

Partition table entries are not in disk order.


Disk /dev/loop0: 220.8 MiB, 231530496 bytes, 452208 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

and uname -a of the same live clonezilla

Linux debian 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux

and the lspci command results

00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:01.1 PCI bridge: Intel Corporation Skylake PCIe Controller (x8) (rev 07)
00:02.0 Display controller: Intel Corporation UHD Graphics 630 (Desktop)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
00:15.0 Signal processing controller: Intel Corporation 200 Series PCH Serial IO I2C Controller
00:15.1 Signal processing controller: Intel Corporation 200 Series PCH Serial IO I2C Controller
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI
00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode]
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port (rev f0)
00:1c.2 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port (rev f0)
00:1c.3 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port (rev f0)
00:1e.0 Signal processing controller: Intel Corporation 200 Series/Z370 Chipset Family Serial IO UART Controller
00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev e7)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
03:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
05:00.0 Ethernet controller: Qualcomm Atheros Killer E2500 Gigabit Ethernet Controller (rev 10)

I think th NVME SSD is not seen peharps because of a lack of drivers

george1421 · Mar 25, 2019, 8:37 PM

@nsmer Well lets start with the question what is FOS?

FOS is (Fog Operating System), its the customized linux OS that runs on the target computer. If you schedule a debug capture/deploy then pxe boot the target computer you will get access to the (FOS) linux console on the target computer.

If I understand correctly you are saying that clonezilla can see the nvme disk? From your listing which drive is the nvme drive?

Sebastian Roth · Mar 25, 2019, 9:51 PM

@nsmer said in Problems with disk controler:

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-75W

Looks like a normal SATA disk to me.

Disk /dev/sdb: 982 MiB, 1029701632 bytes, 2011136 sectors
Disk model: MEMUP

Possibly a USB memory key for booting the live Linux System?!

Disk /dev/sdc: 1.4 MiB, 1474560 bytes, 2880 sectors
Disk model: MEMUP

I have no idea what that might be whatsoever. Looks like a floppy disk telling form the size. But device name “sdc” definitely points to Linux seeing it as a disk block device. By the way, the partition layout on that disk looks totally screwed. Maybe that points us to this disk being not properly recognized by Linux?!?

nsmer · Mar 26, 2019, 3:29 AM

@george1421 said in Problems with disk controler:

@nsmer Well lets start with the question what is FOS?

FOS is (Fog Operating System), its the customized linux OS that runs on the target computer. If you schedule a debug capture/deploy then pxe boot the target computer you will get access to the (FOS) linux console on the target computer.

If I understand correctly you are saying that clonezilla can see the nvme disk? From your listing which drive is the nvme drive?

sorry no clonezilla didn’t see it too

nsmer · Mar 26, 2019, 9:29 AM

@Sebastian-Roth said in Problems with disk controler:

@nsmer said in Problems with disk controler:

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-75W

Looks like a normal SATA disk to me.

Disk /dev/sdb: 982 MiB, 1029701632 bytes, 2011136 sectors
Disk model: MEMUP

Possibly a USB memory key for booting the live Linux System?!

Disk /dev/sdc: 1.4 MiB, 1474560 bytes, 2880 sectors
Disk model: MEMUP

I have no idea what that might be whatsoever. Looks like a floppy disk telling form the size. But device name “sdc” definitely points to Linux seeing it as a disk block device. By the way, the partition layout on that disk looks totally screwed. Maybe that points us to this disk being not properly recognized by Linux?!?

sda is the traditional HDD no problem with it
sdb & sdc are my live usb disk
and the nvme ssd is not displayed

george1421 · Mar 26, 2019, 9:32 AM

@nsmer Ok since you have a dell and I noticed the disk controller is in Raid-On mode, will you look in the bios settings? Look for a setting that says disk controller. There are typically 2 or 3 modes (On Dell Latitude models) One is AHCI and the other is Raid-On. If you see this setting change the disk mode to ahci mode for testing. See if both clonezilla and FOG see the disk then. There is a known problem with the target computer being in uefi mode with Raid-On and linux.

nsmer · Mar 26, 2019, 9:55 AM

@george1421 said in Problems with disk controler:

@nsmer Ok since you have a dell and I noticed the disk controller is in Raid-On mode, will you look in the bios settings? Look for a setting that says disk controller. There are typically 2 or 3 modes (On Dell Latitude models) One is AHCI and the other is Raid-On. If you see this setting change the disk mode to ahci mode for testing. See if both clonezilla and FOG see the disk then. There is a known problem with the target computer being in uefi mode with Raid-On and linux.

thank’s a lot you’re right

I’ve changed the disk controller mode from the default mode : RAID to mode : AHCI

and now the nvme is seen by both FOG & clonezilla.

TBouapi · Mar 26, 2019, 10:03 AM

@george1421 Thanks you for your answering, the problem was here. We have change the mode of the disk controler. Way Of Raid-On to AHCI we have succesful to capture the computer.
Thank’s for your help you are very nice.

george1421 · Mar 26, 2019, 11:45 AM

@Sebastian I need to look into something I found over the weekend. I installed Linux Mint 19.1 on a test Dell computer that was in uefi mode and had raid-on mode configured. LM 19 installed correctly and ran. There was some strangeness with the network adapter so I reloaded LM in bios mode. But then it hit me, why was LM working in uefi mode…?? I need to find out if the linux kernel developers addressed the Intel Raid controller issue in Raid-On mode.

Problems with disk controler

172

12.0k

17.3k

155.2k