Joeh

I've gone to do my upgrade. 7.2.6 -> 7.3.0 On system reboot im greeted withn a "failed to allocate initramfs memory" on each unraid option Anyone got any suggestions?

Done

I've followed this method to install sedutil but when i got to use it i get a command not found. Not massively familair with linux and not sure whats wrong.

Hi all, I've just acquired a new drive and just hoping to get some further info from people. Sas Drive (Hooked up through my HBA) but unmountable. Looked at the logs and noted Read Capacity (16) failed. but the Sense Key was coming back as: 0x2 with ASC=0x4 ASCQ=0x1 From checking this up it looks like Not Ready - Becoming Ready. I'm new to dealing with Sas Drives and had 1 success and one unlucky failure. This seems promising but can anyone with more knowledge shed some light.. How long should this take to become ready and does anything else need to be done on my part? I've attached a picture of the drive log as well as Diag if it helps. soja-diagnostics-20250129-2121.zip

Since updating my system crashed so i've had to hard reset which is now causing my system to parity check and my docker system is failing to start.. but its working cause i can access Plex. But my manually activated services i can't see or touch.

Thanks for this. A wealth of information here. However i'm now left with a bigger question. Thanks to to Wody's reply i looked at the ASC and ASCQ lines.. However the ASCQ indicates that the drive is ready and needs to be spun up. However when i spin up the drive it fails to read capacity. "Nov 30 11:56:31 Soja kernel: sd 44:0:0:0: [sdf] Spinning up disk... Nov 30 11:58:12 Soja kernel: ..................................................................................................not responding... Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] Sense Key : 0x2 [current] [descriptor] Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] ASC=0x4 ASCQ=0x2 Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] Sense Key : 0x2 [current] [descriptor] Nov 30 11:58:12 Soja kernel: sd 44:0:0:0: [sdf] ASC=0x4 ASCQ=0x2" ANy idea?

I've got the same issue as yourself at this point. I've got a drive showing the same start info. How did you get it to spin up? *Edit - My start info isn't exactly the same.. its ASC=0x4 ASCQ=0x2, which from my understanding means the drives needs to be spun up.

So dead drive then?

soja-diagnostics-20241130-0956.zip Here you go. Hope this helps.

Hi Guys. I've got an issue were i've purchased a HGST sas drive (preowned) and its showing up as all 0's on the unassigned devices. I've checked my HBA (LSISAS9300) and its flashed to firmware 16 I'm not sure what to do. I've seen some people say to sg_format as it might be byte size.. but that comes up with "format unit command: device not ready, type sense key" any help would be greatful *Edit - This is my first and only SAS drive in the system. everything else is sata via mobo or sata card

I just ordered this case and was about to make this request. You, good sir, are a true hero

Don't know if anyone else is experiencing this but im finding that the latest version of Kavita (0.6.0.0) is causing my server to spike to 80% cpu usage by just the container being active. I don't know why this is happening but it is consistently happening and i can stop the container and see my cpu usage drop straight away.

No idea.. Like i said.. It works inside of 6.10.3 but not 6.11 which tells me its something to do with a change in this update. Its not a huge issue for myself as im getting a PCIE 10gbe card soon but other people might find this issue and unless someone reports this.. It won't be fixed.

MSI MAG b460 Tomahawk