May 18, 20242 yr Greetings running latest version of UnRaid (6.12.10) on a HP Gen8 MicroServer with a HP HAB card. The Gen8 has a SAS compatible backplane. The system runs well. I have added two SAS Seagate drives but they are not recognised. See as follows. Not recognised during boot either. System hangs for a while with errors - below. Any thoughts? Thanks in advance. IOMMU group 1: [8086:0151] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) [103c:323b] 07:00.0 RAID bus controller: Hewlett-Packard Company Smart Array Gen8 Controllers (rev 01) [1:0:1:0] disk ATA ST4000VN008-2DR1 CV11 /dev/sdb 4.00TB [1:0:2:0] disk ATA ST4000VN000-1H41 SC46 /dev/sdc 4.00TB [1:0:3:0] disk SEAGATE ST4000NM0043 0006 /dev/sdd - [1:0:4:0] disk SEAGATE ST4000NM0023 E007 /dev/sde - [1:0:5:0] disk ATA ST2000DL003-9VT1 CC3C /dev/sdf 2.00TB [1:0:6:0] disk ATA WDC WD30EFRX-68E 0A80 /dev/sdg 3.00TB May 15 21:49:58 HomeNas emhttpd: device /dev/sdd has size zero May 15 21:49:58 HomeNas emhttpd: device /dev/sde has size zero May 15 21:50:00 HomeNas emhttpd: device /dev/sdd has size zero May 15 21:50:00 HomeNas emhttpd: device /dev/sde has size zero
May 18, 20242 yr Community Expert 2 hours ago, kiwipaul said: Greetings running latest version of UnRaid (6.12.10) on a HP Gen8 MicroServer with a HP HAB card. The Gen8 has a SAS compatible backplane. The system runs well. I have added two SAS Seagate drives but they are not recognised. See as follows. Not recognised during boot either. System hangs for a while with errors - below. Any thoughts? Thanks in advance. IOMMU group 1: [8086:0151] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) [103c:323b] 07:00.0 RAID bus controller: Hewlett-Packard Company Smart Array Gen8 Controllers (rev 01) [1:0:1:0] disk ATA ST4000VN008-2DR1 CV11 /dev/sdb 4.00TB [1:0:2:0] disk ATA ST4000VN000-1H41 SC46 /dev/sdc 4.00TB [1:0:3:0] disk SEAGATE ST4000NM0043 0006 /dev/sdd - [1:0:4:0] disk SEAGATE ST4000NM0023 E007 /dev/sde - [1:0:5:0] disk ATA ST2000DL003-9VT1 CC3C /dev/sdf 2.00TB [1:0:6:0] disk ATA WDC WD30EFRX-68E 0A80 /dev/sdg 3.00TB May 15 21:49:58 HomeNas emhttpd: device /dev/sdd has size zero May 15 21:49:58 HomeNas emhttpd: device /dev/sde has size zero May 15 21:50:00 HomeNas emhttpd: device /dev/sdd has size zero May 15 21:50:00 HomeNas emhttpd: device /dev/sde has size zero Post diagnostics or have a look at smartctl for those as may be wrong sector size or encryted
May 18, 20242 yr Author OK === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST4000NM0043 Revision: 0006 Compliance: SPC-4 LU is fully provisioned Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000c50085831dbb Serial number: Z1ZADZTS0000R642JST3 Device type: disk Transport protocol: SAS (SPL-4) Local Time is: Sun May 19 07:30:39 2024 NZST device is NOT READY (e.g. spun down, busy) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. homenas-diagnostics-20240519-0734.zip
May 19, 20242 yr Community Expert to use sas controlled in unraid they should be set to IT mode. to use unraids software raid via linux. That SAS controller appears to have a previous raid configuration that can be entered at boot to configure hardware raid to the disk connected...
May 19, 20242 yr Author Thanks. I went through the steps of putting into IT mode but I will check again. Where in the diagnostics did you see this?
May 19, 20242 yr Author I booted into the HP gui programme for managing this server / controller (HPSSA) which confirms that the controller is in HBA mode, but there is no sign of the 2 SAS drives in any of the menus. I got into the command line equivalent (ssacli) hoping to see more but no joy. The drives are not listed. I am starting to think that the drives (second hand) are faulty but why then does UnRaid see them? Puzzled and open to suggestions
May 19, 20242 yr Community Expert 1 hour ago, kiwipaul said: I booted into the HP gui programme for managing this server / controller (HPSSA) which confirms that the controller is in HBA mode, but there is no sign of the 2 SAS drives in any of the menus. I got into the command line equivalent (ssacli) hoping to see more but no joy. The drives are not listed. I am starting to think that the drives (second hand) are faulty but why then does UnRaid see them? Puzzled and open to suggestions For some reason the drives are not ready, but I cannot tell why. === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST4000NM0043 Revision: 0006 Compliance: SPC-4 LU is fully provisioned Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000c50085831dbb Serial number: Z1ZADZTS0000R642JST3 Device type: disk Transport protocol: SAS (SPL-4) Local Time is: Sun May 19 07:34:23 2024 NZST device is NOT READY (e.g. spun down, busy) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
May 19, 20242 yr Author root@HomeNas:~# sdparm -C sense /dev/sdc /dev/sdc: ATA ST4000VN000-1H41 SC46 root@HomeNas:~# sdparm -C sense /dev/sdd /dev/sdd: SEAGATE ST4000NM0043 0006
May 19, 20242 yr Community Expert ? Thoughts? - https://www.instructables.com/How-to-Fix-the-33V-Pin-Issue-in-White-Label-Disks-/ The disk may be part of the new 3.3 volt line. Did the drives come with a power sata cable? did you use the power sata cable? that 3.3 volt line would power the drive to use but not start up the chip for allocation as the hba at boot to touch and acquire guid is stopped before the unraid grub boot menu. This is only if these drives are using the new sas/satapoer3.3vot pin. Otherwise a live Linux distor like Ubuntu to pull up the disk in gpart / disk to see what on them delete existing data and partion the whole drives with xfs then boot into unraid.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.