Can not detect disks.

[kylian]

@george1421 I am runing version: 1.5.9. am am booting back to the fos linux command prompt now.

[kylian]

@george1421 the output of uname -a is as folllowd.

[george1421]

@kylian Hmm, I don’t understand this. It should be working.

I think I have an R310 on a shelf here. I think it has a PERC 6i/r or something like that in it. I have a perc H700 in my Precision 7810 at home I could also test to boot into FOS Linux with.

[kylian]

@george1421 I dont get it because the other R710s (3 of them) work fine with it also 2 R610 with the perc H700 work fine. just this stubborn one not.

[george1421]

@kylian I remembered I have a P3610 here with a H700 in it, FOS Linux sees the raid controller.

[Thu Feb 18 root@fogclient ~]# uname -a
Linux fogclient.localdomain 4.19.64 #1 SMP Thu Sep 5 18:11:38 CDT 2019 x86_64 GNU/Linux

[Thu Feb 18 root@fogclient ~]# lspci  -nnk | grep -i raid
lspci: Unable to load libkmod resources: error -12
01:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] [1000:0079] (rev 05)
        Kernel driver in use: megaraid_sas

[Thu Feb 18 root@fogclient ~]# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   2.7T  0 disk
`-sda1   8:1    0   2.7T  0 part
sdb      8:16   0 119.2G  0 disk
`-sdb1   8:17   0 119.2G  0 part
sdc      8:32   1    15G  0 disk
`-sdc1   8:33   1   121M  0 part

sda is the raid, sdb is a flash drive in the server and sdb is the FOS Linux usb boot drive. The FOS Linux kernel on this flash drive is even older than the one you have.

So now to this unique computer, it appears its not loading the megaraid_sas kernel drive. So when you are booted into debug mode on this suspect computer ensure that lspci -nnk | grep -i raid still doesn’t list the kernel driver then review the file /var/log/messages search for megaraid and PERC to see if there are any messages where the kernel has a disagreement with the raid controller (like the raid controller is using super old firmware). Maybe that will give us a clue to why this one computer has issues.

As I said, it should be working…

[kylian]

@george1421 well it looks like the driver is there just has problems loading. also i do see megaraid on that log but there is no PERC in there. the firmware of that raid controller is the last available .

[Sebastian Roth]

megaraid_sas ... Failed to init firmware - no idea but doesn’t sound good. I’d start searching the web on this message…

[george1421]

@kylian I will give you a hint on helping debug.

1. You should have pxe booted into the debug console of FOS Linux
2. Issue the command ip a s and get the IP address of the target computer.
3. Give root a password, something simple like hello with passwd
4. Now you can use putty/ssh and remote into the target computer using the IP address and root/password you defined.

Now you can use vi and view messages, and via putty copy and paste text so you can post it here. I will boot back up that P3610 I have here and copy out that section of the messages so we can compare and contrast. But I would surely validate the version of firmware on that H700 controller. You need to have the latest anyway if you wan to use larger than 4GB disks anyway. I think I saw the firmware version when I searched for PERC in the messages log. But you can also get that info during bootup too because its displayed on the console.

[george1421]

This is the output from my P3510

[Thu Feb 18 root@fogclient /var/log]# grep PERC messages
Feb 18 19:00:26 fogclient user.notice kernel: scsi 0:2:0:0: Direct-Access     DELL     PERC H700        2.10 PQ: 0 ANSI: 5

[Thu Feb 18 root@fogclient /var/log]# grep LSI messages
Feb 18 19:00:26 fogclient user.info kernel: LSI 3ware SAS/SATA-RAID Controller device driver for Linux v3.26.02.000.
Feb 18 19:00:26 fogclient user.info kernel: Copyright (c) 1999-2008 LSI Corporation

[Thu Feb 18 root@fogclient /var/log]# grep megaraid messages
Feb 18 19:00:26 fogclient user.info kernel: megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
Feb 18 19:00:26 fogclient user.info kernel: megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: FW now in Ready state
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: 64 bit DMA mask and 32 bit consistent mask
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: firmware supports msix   : (0)
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: current msix/online cpus : (1/8)
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: RDPQ mode        : (disabled)
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: controller type  : MR(512MB)
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: Online Controller Reset(OCR)     : Enabled
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: Secure JBOD support      : No
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: NVMe passthru support    : No
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: FW provided TM TaskAbort/Reset timeout   : 0 secs/0 secs
Feb 18 19:00:26 fogclient user.notice kernel: megaraid_sas 0000:01:00.0: megasas_init_mfi: fw_support_ieee=67108864
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: INIT adapter done
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: Jbod map is not supported megasas_setup_jbod_map 5152
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: pci id           : (0x1000)/(0x0079)/(0x1028)/(0x1f17)
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: unevenspan support       : no
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: firmware crash dump      : no
Feb 18 19:00:26 fogclient user.info kernel: megaraid_sas 0000:01:00.0: jbod sync map            : no

The firmware loaded on the H700 is version 12.10.007

If you don’t need the array currently on that server it may also add value to reset the controller back to factory defaults then rebuild the array.

FWIW many of the current main stream linux distros have removed support for the H700 disk controllers (they are 10 years old already). I know centos 8 has an “extras” kernel that still has the driver in it. I’m sure if your final OS for this system is windows there are drivers for it. Its just if your final OS for these servers is linux be aware the driver may not be included out of the box.

[kylian]

@george1421 al ride will do. for now i have plugged in a different perc h700 card see if that makes any difference.

[kylian]

@george1421 this is indeed a lot more easy using SSH. for now i swaped the raid card for the same one just a other one. the firmware is the latest 12.10.007. the OS i run is ubuntu server and as of yet it has always worked fine. (20.04 seems to run even better then 18.04 on them in my experience )

[kylian]

@sebastian-roth well having put in a new PERC H700 card and updated it (as it had really old fimware) i seem to have the exact same problem

[kylian]

@george1421 seems like root is not allowd to ssh in to it? wen i try to ssh in to the FOS linux i get Permission denied, please try again. password is corect

[george1421]

@kylian If the password is blank “default” you can’t ssh into fos linux. But if you set the password with passwd then you can remote into it. This is by design.

[kylian]

@george1421 i know i have set a password multiple times with passwd. i did check and root login is set to permit so that shut be fine.

[Sebastian Roth]

@kylian Sure you got the right IP address of this host you set the password? Just trying to rule out possible issues. I am fairly sure we had people use SSH access with FOG 1.5.9 working so I would not expect this to be an issue in the FOS inits.

[kylian]

@sebastian-roth Yes i am sure. also for now i am using 2 clonezilla live USBs which seems to work perfectly fine and does recognize the disks/raid card. cloning over the network with these 2 USB sticks seems to work.