hi folks. Im trying a new setup to use an old hardware i have to create my first unraid server. Im totally new to this OS and a complete dummie in linux. So please i would appreciate a little detailed explanation to solve this.

 

Hardware specs

Quote

Model:Custom

M/B:MSI Z170A GAMING M5 (MS-7977) Version 1.0 s/n GA16799695

BIOS:American Megatrends Inc. Version 1.I0 Dated 06/26/2018

CPU:Intel® Core™ i7-7700 CPU @ 3.60GHz

HVM:Enabled

IOMMU:Disabled

Cache:L1 Cache: 256 KiB, L2 Cache: 1 MiB, L3 Cache: 8 MiB

Memory:8 GiB DDR4 (max. installable capacity 64 GiB)

Network:bond0: fault-tolerance (active-backup), mtu 1500

Kernel:Linux 6.1.79-Unraid x86_64

OpenSSL:1.1.1v

Uptime:10 minutes

Chasis: Norco RPC-4224 24 bay sata/sas hotswap. Back-planes have six total SFF-8087 connectors

HBA: HighPoint RocketRAID 3560 1Gb ram 24 ports. (I think it uses intel chipset, )

2x1rb Nvme for cache drives

21 drives. Mainly hitachi 2tb, 3tb and wd 2tb.

 

I successfully created an array using the nvme drives (attached to the mobo). unraid detect the and format them, all fine.

 

The inferno comes with the spinning drives. System boots fine but only 1 of 21 drives is available to use in the array. If i disconnect the usable drive and reboot another drive will be available but only ONE.

 

I tried change the 3560 card to all the pcie ports in the mobo with no luck

i tried the run the 3560 in no raid mode (at bios startup in the internal card bios software you can select raid, mixed mode or non-raid). I ried the three options with no luck.

I take out 3 disks 2 tb attached via sata (motherboard) to another machine and format them in windows. They are detected. formatted and totally usable. I put them back in unraid and same behavior.

 

I realize unraid is loading rocketraid 3560 drivers just fine

Quote

hptiop HighPoint RocketRAID 3xxx/4xxx Controller Driver Inuse scsi

 

My system log are flooded with theese

Quote

May 31 07:02:22 NAS-UNRAID emhttpd: device /dev/sdc problem getting id May 31 07:02:22 NAS-UNRAID emhttpd: device /dev/sds problem getting id May 31 07:02:22 NAS-UNRAID emhttpd: device /dev/sdn problem getting id May 31 07:02:22 NAS-UNRAID emhttpd: device /dev/sdq problem getting id May 31 07:02:22 NAS-UNRAID emhttpd: device /dev/sdo problem getting id May 31 07:02:22 NAS-UNRAID emhttpd: device /dev/sdl problem getting id May 31 07:02:22 NAS-UNRAID emhttpd: device /dev/sdi problem getting id May 31 07:02:22 NAS-UNRAID emhttpd: device /dev/sdp problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdm problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdj problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdk problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdh problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdg problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdd problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdt problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sde problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdu problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdb problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdr problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdf problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdc problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sds problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdn problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdq problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdo problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdl problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdi problem getting id May 31 07:02:23 NAS-UNRAID emhttpd: device /dev/sdp problem getting id

log shows drive detection

Quote

May 31 07:08:14 NAS-UNRAID kernel: scsi host1: RocketRAID 3xxx/4xxx Controller driver May 31 07:08:14 NAS-UNRAID kernel: scsi 1:0:0:0: Direct-Access HPT DISK 1_0 4.00 PQ: 0 ANSI: 5 May 31 07:08:14 NAS-UNRAID kernel: alx 0000:03:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [4c:cc:6a:af:47:11] May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) May 31 07:08:14 NAS-UNRAID kernel: nvme nvme0: allocated 128 MiB host memory buffer. May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] Write Protect is off May 31 07:08:14 NAS-UNRAID kernel: scsi 1:0:1:0: Direct-Access HPT DISK 1_1 4.00 PQ: 0 ANSI: 5 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] Mode Sense: 2f 00 00 00 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 31 07:08:14 NAS-UNRAID kernel: nvme nvme0: 8/0/0 default/read/poll queues May 31 07:08:14 NAS-UNRAID kernel: nvme nvme1: allocated 128 MiB host memory buffer. May 31 07:08:14 NAS-UNRAID kernel: scsi 1:0:1:0: Attached scsi generic sg2 type 0 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:1:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:1:0: [sdc] Write Protect is off May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:1:0: [sdc] Mode Sense: 2f 00 00 00 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 31 07:08:14 NAS-UNRAID kernel: nvme nvme1: 8/0/0 default/read/poll queues May 31 07:08:14 NAS-UNRAID kernel: scsi 1:0:3:0: Direct-Access HPT DISK 1_3 4.00 PQ: 0 ANSI: 5 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] Attached SCSI disk May 31 07:08:14 NAS-UNRAID kernel: nvme1n1: p1 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:3:0: Attached scsi generic sg3 type 0 May 31 07:08:14 NAS-UNRAID kernel: nvme0n1: p1 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:3:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:3:0: [sdd] Write Protect is off May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:3:0: [sdd] Mode Sense: 2f 00 00 00 May 31 07:08:14 NAS-UNRAID kernel: scsi 1:0:4:0: Direct-Access HPT DISK 1_4 4.00 PQ: 0 ANSI: 5 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:1:0: [sdc] Attached SCSI disk May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:3:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:4:0: Attached scsi generic sg4 type 0 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:4:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) May 31 07:08:14 NAS-UNRAID kernel: scsi 1:0:5:0: Direct-Access HPT DISK 1_5 4.00 PQ: 0 ANSI: 5 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:4:0: [sde] Write Protect is off May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:4:0: [sde] Mode Sense: 2f 00 00 00 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:4:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:5:0: Attached scsi generic sg5 type 0 May 31 07:08:14 NAS-UNRAID kernel: sd 1:0:5:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.82

but also shows errors on initialization i think

 

Quote

May 31 07:08:25 NAS-UNRAID kernel: ZFS: Loaded module v2.1.14-1, ZFS pool version 5000, ZFS filesystem version 5
May 31 07:08:25 NAS-UNRAID emhttpd: shcmd (6): /sbin/modprobe md-mod super=/boot/config/super.dat
May 31 07:08:25 NAS-UNRAID kernel: md: unRAID driver 2.9.27 installed
May 31 07:08:26 NAS-UNRAID emhttpd: Trial key detected, GUID: 346D-5678-FCD5-998325136AA8 FILE: /boot/config/Trial.key
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdm problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdj problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdk problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdh problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdg problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: Device inventory:
May 31 07:08:26 NAS-UNRAID emhttpd: ADATA_LEGEND_840_2N422L197QRW (nvme1n1) 512 2000409264
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdd problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdt problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: DISK_1_4_200193c0000000000 (sde) 512 3907029168
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdu problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdb problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdr problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdf problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdv problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdc problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sds problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdn problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdq problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: ADATA_LEGEND_840_2N422LAKK121 (nvme0n1) 512 2000409264
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdo problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdl problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdi problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: device /dev/sdp problem getting id
May 31 07:08:26 NAS-UNRAID emhttpd: General_USB_Flash_Disk_FCD5998325136AA8-0:0 (sda) 512 60620800

 

I can see this under system devices:

Quote

[0:0:0:0]disk General USB Flash Disk 2.00 /dev/sda 31.0GB

[1:0:0:0]disk HPT DISK 1_0 4.00 /dev/sdb 3.00TB

[1:0:1:0]disk HPT DISK 1_1 4.00 /dev/sdc 3.00TB

[1:0:3:0]disk HPT DISK 1_3 4.00 /dev/sdd 3.00TB

[1:0:4:0]disk HPT DISK 1_4 4.00 /dev/sde 2.00TB

[1:0:5:0]disk HPT DISK 1_5 4.00 /dev/sdf 2.00TB

[1:0:6:0]disk HPT DISK 1_6 4.00 /dev/sdg 2.00TB

[1:0:7:0]disk HPT DISK 1_7 4.00 /dev/sdh 2.00TB

[1:0:8:0]disk HPT DISK 1_8 4.00 /dev/sdi 2.00TB

[1:0:9:0]disk HPT DISK 1_9 4.00 /dev/sdj 2.00TB

[1:0:10:0]disk HPT DISK 1_10 4.00 /dev/sdk 2.00TB

[1:0:11:0]disk HPT DISK 1_11 4.00 /dev/sdl 2.00TB

[1:0:12:0]disk HPT DISK 1_12 4.00 /dev/sdm 2.00TB

[1:0:13:0]disk HPT DISK 1_13 4.00 /dev/sdn 2.00TB

[1:0:15:0]disk HPT DISK 1_15 4.00 /dev/sdo 3.00TB

[1:0:16:0]disk HPT DISK 1_16 4.00 /dev/sdp 2.00TB

[1:0:17:0]disk HPT DISK 1_17 4.00 /dev/sdq 2.00TB

[1:0:18:0]disk HPT DISK 1_18 4.00 /dev/sdr 2.00TB

[1:0:19:0]disk HPT DISK 1_19 4.00 /dev/sds 2.00TB

[1:0:21:0]disk HPT DISK 1_21 4.00 /dev/sdt 2.00TB

[1:0:22:0]disk HPT DISK 1_22 4.00 /dev/sdu 2.00TB

[1:0:23:0]disk HPT DISK 1_23 4.00 /dev/sdv 2.00TB

[N:0:0:1]disk ADATA LEGEND 840__1 /dev/nvme0n1 1.02TB

[N:1:0:1]disk ADATA LEGEND 840__1 /dev/nvme1n1 1.02TB

 

But in my main tab only these drives are available to use in the array

Quote

Dev 2DISK_1_4_200193c0000000000 - 2 TB (sde)*000

Dev 3ADATA_LEGEND_840_2N422LAKK121 - 1 TB (nvme0n1)23 C5400

Dev 1ADATA_LEGEND_840_2N422L197QRW - 1 TB (nvme1n1)26 C5400

as you can see th 2xNvme drives and only 1 spinning drive.

 

I cannot buy a new 24 port HBA at this time. I would like to use my existing hardware.

 

I will really appreciate any help on this

 

nas-unraid-diagnostics-20240531-1135.zip

8 minutes ago, Ronald Q said:

problem getting id

RAID controllers are not recommend for multiple reasons, and this happens when the same device is being detected multiple times, in this case the RAID controller is using the same ID for all the disks, Unraid requires a unique ID/SN for each device.

 

 

There is any workaround? configuration parameter for the controller? driver? or any other way to make it work.

 

I cannot pay for a SF-8087 x24 non-raid port HBA at this time

 

Quote

May 31 10:31:06 NAS-UNRAID kernel: scsi 1:0:0:0: Direct-Access     HPT      DISK 1_0         4.00 PQ: 0 ANSI: 5
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
May 31 10:31:06 NAS-UNRAID kernel: scsi 1:0:1:0: Direct-Access     HPT      DISK 1_1         4.00 PQ: 0 ANSI: 5
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] Write Protect is off
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:1:0: Attached scsi generic sg2 type 0
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] Mode Sense: 2f 00 00 00
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:1:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:1:0: [sdc] Write Protect is off
May 31 10:31:06 NAS-UNRAID kernel: scsi 1:0:3:0: Direct-Access     HPT      DISK 1_3         4.00 PQ: 0 ANSI: 5
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:1:0: [sdc] Mode Sense: 2f 00 00 00
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:3:0: Attached scsi generic sg3 type 0
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:3:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:3:0: [sdd] Write Protect is off
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:3:0: [sdd] Mode Sense: 2f 00 00 00
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:3:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 31 10:31:06 NAS-UNRAID kernel: nvme nvme0: allocated 128 MiB host memory buffer.
May 31 10:31:06 NAS-UNRAID kernel: scsi 1:0:4:0: Direct-Access     HPT      DISK 1_4         4.00 PQ: 0 ANSI: 5
May 31 10:31:06 NAS-UNRAID kernel: sd 1:0:3:0: [sdd] Attached SCSI disk
May 31 10:31:06 NAS-UNRAID kernel: nvme nvme0: 8/0/0 default/read/poll queues

In the logs shows diferent id numbers for each drive for example

1:0:0:0:

1:0:1:0:

1:0:3:0:

 

 

Edited May 31, 20242 yr by Ronald Q

13 minutes ago, Ronald Q said:

configuration parameter for the controller?

I'm not familiar with that controller, but look for an option to enable disk passthrough or similar, 

 

15 minutes ago, Ronald Q said:

In the logs shows diferent id numbers for each drive for example

Those are not the IDs, the disks are being detected as

 

2 hours ago, Ronald Q said:

DISK_1_4_200193c0000000000

 

Note all the 0s in the end, Unraid considers that the serial number, so they will all have the same.

i understand now. thank you very much. 

 

In the drivers section i can pass additional parameters to the controller. May be, we can use that. Unfortunately the raid controller is very old and highpoint support is less than terrible. Only hope is someone with experience on highpoint controllers and commands to do it. Lets wait is someone had solve this issue or similar.