Edit: new cable fixed it. The otherone wasnt crossover.

I have a problem.

I have an (Intertech 2U 2412)[https://www.inter-tech.de/productdetails-144/2U-2412_EN.html]. I have some old desktop hardware in it to build a SAN. The OS I’m running is currently Proxmox 7.

Now I have the problem i’m having is that the drives I put in the hotswap bay are not showing up in the OS. The lights on the bays light up, I can hear the disks spinning so they seem to have power.

The connection splits from SAS to 4 times SATA to a PCIE expansion card. This card is confirmed to work: If I put my bootdrive in it, the pc boots normally and the bootdrive shows up in the OS. The splitter cable could be the problem, granted, but the manual of the case specified this type of cable and I triple checked that this is correct.

When I look in /var/log I see kern.log files with loads of these messages in them. This is where things get murky for me. In my linux journey I haven’t yet been this deep into the OS/kernel before. Can anyone help me debug what is happening in my system? Or at least help me understand what is happening in these logs?

[1378464.033553] ata14.00: status: { DRDY }
[1378464.033555] ata14.00: failed command: WRITE FPDMA QUEUED
[1378464.033556] ata14.00: cmd 61/08:a8:b0:ed:a0/00:00:0e:00:00/40 tag 21 ncq dma 4096 out
[1378464.033556]          res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

EDIT: New cable fixed it! Turns out the other one wasnt crossover.

  • SK4nda1OP
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Hey thanks!

    This is a great idea! I’ll try it this weekend. I’ll let you know.