[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...

[ich777]

9 minutes ago, fargotto48 said:

Problem software (letter disk changes)

That‘s not an issue at all since Unraid doesn‘t assign disks with drive letters, it assigns them based on their UUID.

As said this is most likely a driver issue.

 

On my system the Kernel also reasigns sdX for the disks sometimes when I adr or remove a disk but that‘s not the issue!

 

Please post your Diagnostics when only 3 disks show up (since there will be most likely only three disks be showing up in the system and if thats the case then it‘s a driver issue).

I bet the driver has something to do with that, you have to wait for an answer on GitHub.

[fargotto48]

2 hours ago, ich777 said:

Please post your Diagnostics when

Wow, I'm finally home.

Here's my data archive.

olips-nas01-diagnostics-20241004-2025_.zip

[fargotto48]

Here's another one. Immediately after the reboot

hpsa_update_device_info: inquiry failed, device will be skipped hpsahba

olips-nas01-diagnostics-20241004-2044.zip

Edited 13 hours ago by fargotto48

[ich777]

24 minutes ago, fargotto48 said:

Here's my data archive.

As you can see here only three disks are recognized:

 

Here is also something in the logs which indicate a driver issue:

Oct  4 05:36:03 Tower kernel: hpsa can't handle SMP requests
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: aborted: LUN:000000c000000001 CDB:12000000310000000000000000000000
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: hpsa_update_device_info: inquiry failed, device will be skipped.
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: aborted: LUN:000000c000000101 CDB:12000000310000000000000000000000
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: hpsa_update_device_info: inquiry failed, device will be skipped.
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: aborted: LUN:000000c000000201 CDB:12000000310000000000000000000000
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: hpsa_update_device_info: inquiry failed, device will be skipped.
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: aborted: LUN:000000c000000301 CDB:12000000310000000000000000000000
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: hpsa_update_device_info: inquiry failed, device will be skipped.
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: aborted: LUN:000000c000000401 CDB:12000000310000000000000000000000
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: hpsa_update_device_info: inquiry failed, device will be skipped.
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: scsi 3:0:0:0: added RAID              HP       P410             controller SSDSmartPathCap- En- Exp=1
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: scsi 3:0:1:0: masked Direct-Access     ATA      MM1000GFJTE      PHYS DRV SSDSmartPathCap- En- Exp=0
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: scsi 3:0:2:0: masked Direct-Access     ATA      MM1000GFJTE      PHYS DRV SSDSmartPathCap- En- Exp=0
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: scsi 3:0:3:0: masked Direct-Access     ATA      MM1000GFJTE      PHYS DRV SSDSmartPathCap- En- Exp=0
Oct  4 05:36:03 Tower kernel: hpsa 0000:06:00.0: scsi 3:0:4:0: masked Enclosure         PMCSIERA  SRC 8x6G        enclosure SSDSmartPathCap- En- Exp=0
Oct  4 05:36:03 Tower kernel: hpsa can't handle SMP requests

 

 

As I thought this is not a software issue this is a driver issue.

[fargotto48]

5 minutes ago, ich777 said:

As I thought this is not a software issue this is a driver issue.

So, the plugin itself is buggy?


 

And this is NOT a problem with the disks.

It feels like the plugin only sees 3 disks bay out of 8.

I didn't find out which ones exactly. But it's definitely not a problem with the disks, since other disks will be visible if I swap them (3 pieces)

Edited 13 hours ago by fargotto48
disk

[ich777]

20 minutes ago, fargotto48 said:

So, the plugin itself is buggy?

Maybe, but again, I can‘t help with that since my plugin is only installing the precompiled driver for Unraid for the correct Kernel version and does nothing more.

 

You should definitely post the output from above on the GitHub issue that you‘ve created.

 

Maybe the firmware from your controller is outdated or something like that but these are only assumptions since I really can’t tell what‘s going on, again, I have no hardware to test and I did this plugin on request.

 

You should really ask your questions on GitHub.

[fargotto48]

7 minutes ago, ich777 said:

You should really ask your questions on GitHub.

You're a cool dude) Maybe in the future it will be possible to buy you this garbage from ebay for $ 10?))

for any tests

Edited 12 hours ago by fargotto48

[ich777]

@fargotto48 you should also look at this thread (a simple Google search have brought that up, the tread is in German hut I think you can translate it) :

 

Please also note that he linked a Youtube video and he also said that his firmware on the controller was outdated.

[ich777]

8 minutes ago, fargotto48 said:

Maybe in the future it will be possible to buy you this garbage from ebay for $ 10?))

No thank you… 😂

I‘m happy with my ASM1166 controller… I really try to avoid such problematic hardware…

 

I really don‘t need such a controller and AFAIK these are usually only found in HP servers.

[fargotto48]

16 minutes ago, ich777 said:

and AFAIK these are usually only found in HP servers.

I downloaded the proprietary utility HP Smart Array Assistant. But the problem starts EARLIER than the system loads.

That is, the program itself "sees" only 3 disks (bed 6,7,8). In fact, it only sees beds 6,7,8.

And my firmware is the latest. I don't know, I'll try to do a clean slate according to the guide

[fargotto48]

That is, the problem is much deeper. After rebooting, most likely the controller itself sees that "something is wrong". And goes crazy.

After all, the HBA mode is not actually officially supported on the p410 and p410i

 

On Monday, when I come to work, I will try to remove the 1GB cache board and the super capacitor.

Edited 50 minutes ago by fargotto48