Start a Conversation

Unsolved

This post is more than 5 years old

R

3425

March 16th, 2018 20:00

PE R420 w/Perc H310 RAID 5 with 3 990GB SAS slow boot b4 kernel messages in Fedora 27 replaced SSD

Our PE R420, with a Perc H310, came with one 100 GB SSD, and I replaced it with three 990 GB SAS and I configured it as RAID 5 via the H310; the S130 just says no hard drives found. Side question, is there a way to disable that?

I removed the RHGB and quiet options in the kernel line of grub2, as we are running Fedora Server 27, and it takes about 20 minutes for each reboot to start showing the kernel boot logs. I changed the Embedded SATA setting from AHCI to RAID. Once the kernel kicks in boot time is less than a minute. I got a suggestion to run modprobe on either the driver for the hard drive or H310. Dell's downloads page has a driver for the H310 but only for Red Hat. Is the Embedded SATA setting incorrect? Do I try the mod probe route?

Here's an lshw, interesting that the command reveals the true manufacturer, not Dell:

lshw|grep -i raid
           *-raid
                description: RAID bus controller
                product: MegaRAID SAS 2008 [Falcon]
                capabilities: raid pm pciexpress vpd msi msix bus_master cap_list rom
                configuration: driver=megaraid_sas 

Look at systemd-analyze:

systemd-analyze blame | tee detailed-boot-time.log
         22.229s ypbind.service
         16.923s plymouth-quit-wait.service
         11.674s NetworkManager-wait-online.service
         11.480s udisks2.service
          6.921s dkms.service
          4.094s firewalld.service
          2.760s mariadb.service
          2.449s lvm2-monitor.service
          2.246s sssd.service
          2.207s mongod.service
          2.096s x2gocleansessions.service
          1.886s systemd-udev-settle.service
          1.788s initrd-switch-root.service
          1.543s ModemManager.service
          1.511s dev-mapper-fedora_newerdos\x2droot.device
          1.494s chronyd.service
          1.456s switcheroo-control.service
          1.438s abrtd.service
          1.384s rsyslog.service
          1.311s home.mount
          1.274s nscd.service
          1.068s rtkit-daemon.service
          1.026s dracut-initqueue.service
           613ms polkit.service
           568ms rolekit.service
           563ms usr-local.mount
           562ms systemd-journald.service
           522ms systemd-journal-flush.service
           517ms lvm2-pvscan@8:2.service
           489ms NetworkManager.service
           462ms systemd-vconsole-setup.service
           453ms dev-mqueue.mount
           438ms packagekit.service
           431ms autofs.service
           412ms kmod-static-nodes.service
           400ms auditd.service
           379ms dev-hugepages.mount
           359ms sysroot.mount
           338ms fedora-readonly.service
           333ms dnf-makecache.service
           283ms colord.service
           281ms var.mount
           259ms rpcbind.service
           241ms systemd-udevd.service
           239ms proc-fs-nfsd.mount
           220ms systemd-fsck@dev-disk-by\x2duuid-5efe2fed\x2d7ec9\x2d49c2\x2dbf31\x2dc5be6daf3d4b.service
           213ms systemd-sysctl.service
           207ms sshd.service
           191ms nfs-config.service
           161ms dracut-pre-pivot.service
           159ms systemd-remount-fs.service
           156ms accounts-daemon.service
           155ms systemd-logind.service
           153ms nfs-server.service
           139ms upower.service
           133ms sys-kernel-debug.mount
           132ms systemd-tmpfiles-setup-dev.service
           130ms systemd-udev-trigger.service
           126ms dracut-cmdline.service
           124ms fedora-import-state.service
           123ms initrd-parse-etc.service
            93ms systemd-tmpfiles-clean.service
            87ms plymouth-switch-root.service
            87ms systemd-tmpfiles-setup.service
            85ms nfs-idmapd.service
            83ms plymouth-read-write.service
            79ms rpc-statd.service
            74ms initrd-cleanup.service
            59ms dracut-shutdown.service
            59ms systemd-user-sessions.service
            54ms user@6105.service
            54ms systemd-fsck@dev-mapper-fedora_newerdos\x2dhome.service
            49ms wpa_supplicant.service
            48ms boot.mount
            47ms dracut-pre-udev.service
            43ms dev-mapper-fedora_newerdos\x2dswap.swap
            42ms systemd-random-seed.service
            40ms nfs-mountd.service
            36ms user@42.service
            32ms tmp.mount
            27ms systemd-fsck-root.service
            22ms cockpit.socket
            20ms var-lib-nfs-rpc_pipefs.mount
            19ms initrd-udevadm-cleanup-db.service
            17ms systemd-update-utmp.service
            17ms plymouth-start.service
            13ms rpc-statd-notify.service
            12ms gdm.service
             9ms systemd-update-utmp-runlevel.service
             8ms gssproxy.service
             3ms sys-kernel-config.mount

Moderator

 • 

8.7K Posts

March 19th, 2018 09:00

Hi,

Can you private message me your service tag so I can get some additional information?

 

We replied to you on Twitter.

10 Posts

March 19th, 2018 11:00

I sent a PM on Twitter. So for now, when I go to the RAID configuration, what drop downs should I select to get better performance?

Will a H710 or H710P fit and not require a reinstall?

Moderator

 • 

8.7K Posts

March 19th, 2018 11:00

For the H310 the options are more limited and not anything that will dramatically effect performance. Switching controllers is the best option.

Moderator

 • 

8.7K Posts

March 19th, 2018 11:00

You can replace the H310 with an H710 or H710P and it will import the virtual disk without a reinstall. RAID 1 or 10, should provide better performance on the H310, but that would require a reinstall.

10 Posts

March 19th, 2018 11:00

When in the config for the RAID can you tell me the optimal drop downs I should choose for gaining some read/write performance? 

10 Posts

March 20th, 2018 07:00

I see in the Advanced Options of the controller BIOS is grayed out and Read Policy is set to No Read Ahead and Write Policy is set to Write Through. Is there a way to edit this or did that need to happen when I initialized the disks and created the array?

Moderator

 • 

8.7K Posts

March 20th, 2018 08:00

Those features require an H710. The H310 doesn’t have cache on the controller to use them.

10 Posts

March 28th, 2018 10:00

Looks like only the other s110 controller shows. I'm having my colleague reseat the h710 as I'm off site. Thanks so much for the quick reply.

10 Posts

March 28th, 2018 10:00

We replaced the controller with a h710 but now the BIOS does not pick it up and error with no boot disk found. Lifecycle controller is set to automatically detect new hardware. Anything else to check?

Moderator

 • 

8.7K Posts

March 28th, 2018 10:00

What does it show in ctrl+r under pd mgmt?

No Events found!

Top