search

PartialVolume / shredos.x86_64

Shredos Disk Eraser 64 bit for all Intel 64 bit processors as well as processors from AMD and other vendors which make compatible 64 bit chips. ShredOS - Secure disk erasure/wipe
Other
1.28k stars 52 forks source link

unable to create qla2xxx trace instance, instance logging will be disabled #257

Open melodyka opened 1 month ago

melodyka commented 1 month ago

Hello, I tried to erase the hard disks at the HP DL388 gen9, but they have different errors. I can not enter the Shredos.

BIOS setting: UEFI mode, secure boot: disable

Error messages:

  1. MSI-X: Failed to enable support, giving up
  2. Unable to create qla2xxx trace instance, instance logging will be disabled

Anybody with the same issue? Thank you.

Using the key with Rufus and shredos-2023.08.2_25.0_x86-64_0.35_20231110.img

PartialVolume commented 1 month ago

If I send you a link to the new version of ShredOS (.img) that I'm currently testing. Would you be willing to try it?

melodyka commented 1 month ago

If I send you a link to the new version of ShredOS (.img) that I'm currently testing. Would you be willing to try it?

Of course，let's do it！

PartialVolume commented 1 month ago

Here's the rc1 version of 26.0

2024.02.2_26.0_x86-64_0.37-rc1

sha1sum checksum

d2bed390ae04db0d9c4b8dd6e61fcf11739680c0

melodyka commented 1 month ago

Here's the rc1 version of 26.0

2024.02.2_26.0_x86-64_0.37-rc1

sha1sum checksum

d2bed390ae04db0d9c4b8dd6e61fcf11739680c0

Nice to get this version, it can work on PC or laptop. But for the server, it can not enter the OS page after completing loading. This time it did not provide any errors.

PartialVolume commented 1 month ago

Is your server connected to a network? It may be working in the background, it's just that graphics are not working.

Try putting nomodeset on the kernel command line to stop it switching from simple framebuffer mode to DRM graphics mode.

Alternatively telnet into ShredOS as described in the readme.md about running in headless mode.

PartialVolume commented 1 month ago

https://github.com/PartialVolume/shredos.x86_64#how-to-wipe-drives-on-headless-systems-or-systems-with-faulty-display-hardware-for-use-on-secure-lans-only

It would be useful if it works using either of the two methods above, i.e headless or nomodeset, as once in you can run lspci and paste the output here which will show what graphics hardware is installed.

PartialVolume commented 1 month ago

Also just to clarify, ShredOS will need a DHCP server or router on the server network so it can obtain it's IP address. You can't currently set a static IP address.

melodyka commented 1 month ago

Is your server connected to a network? It may be working in the background, it's just that graphics are not working.

Try putting nomodeset on the kernel command line to stop it switching from simple framebuffer mode to DRM graphics mode.

Alternatively telnet into ShredOS as described in the readme.md about running in headless mode.

Thanks for your quick reply, actually whether laptop or server, I run it without the network. Does it support this mode?

Let me try to get this version [ShredOS .iso x86_64bit for CD/DVD, Ventoy nomodeset NoDRM].

PartialVolume commented 3 weeks ago

@melodyka Is this working with the new version? v2024.02.2_26.0_x86-64_0.37

APoorDev commented 3 weeks ago

I have the same issue only on my HP machine (I have a lot of different HP laptops/desktops I can test on). It works fine on my Dell and Asus machines and I will try a few older HP machines later if I can (Currently testing on an 845 G8 and a 865 G10) I am going to do some tinkering with BIOS settings once I get home to see if I can get it to boot.

For the v2024.02.2_26.0_x86-64_0.37 image it just hangs on 100% or a solid black screen with no cursor.

For the older v2023.08.2_25_x86-64_0.35 image it hangs on the "unable to create qla2xxx trace instance, instance logging will be disabled" error.

I have tried booting both images with nomodeset and will try noapic when I get home.

PartialVolume commented 3 weeks ago

@APoorDev Thanks, much appreciated. HP systems do seem more problematic than other makes. I have a HP desktop machine that won't boot via USB but will boot if you use the .iso and boot via CD/DVD. With that particular model, xW4400 I think it was, quite an old core2Duo model. I believe the problem was an issue or limitation with the bios.

APoorDev commented 3 weeks ago

@PartialVolume Absolutely! Thanks for the great piece of software!

Yeah HP's BIOS is quite the mess at the moment, especially on their new AMD systems.

I did get a new error on the 865 G10. After it reaches 100% it gives me the error "error: can't allocate kernel" instead of just the black screen like the G8. Then it pushes me to the grub menu.

I will try the iso in a few to see if I get any different results. Unfortunately HP has dropped Legacy support on new machines. I tried the ISO's with Ventoy to no avail, but I still have a few other things I can try with the BIOS.

PartialVolume commented 3 weeks ago

I did get a new error on the 865 G10. After it reaches 100% it gives me the error "error: can't allocate kernel" instead of just the black screen like the G8. Then it pushes me to the grub menu.

That error can sometimes be caused by a bad burn on the flash drive. Maybe worth trying a new burn to a different stick if you haven't done so already. Could also be caused by some memory settings in the bios.

APoorDev commented 2 weeks ago

Couldn't be more right about these HP machines are weird. The G8 doesn't work with either image like my comment above. I will try to update its bios when i get a chance. The G10 I've had some luck with, I tried another usb but still the same "can't allocate kernel" error but only on the newer image. I tried disabling a few memory security options in the bios but no luck. The older v2023.08.2_25_x86-64_0.35 image seems to work fine! It still gives the "unable to create qla2xxx trace instance, instance logging will be disabled" but loads nwipe and looks to be able to wipe.

melodyka commented 2 weeks ago

@melodyka Is this working with the new version? v2024.02.2_26.0_x86-64_0.37

Sorry, it is the same result. And I don't have the mechine now. Thank you for your great help!!