Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extend image instead of using gparted #311

Open
boruto79 opened this issue Jan 5, 2025 · 3 comments
Open

extend image instead of using gparted #311

boruto79 opened this issue Jan 5, 2025 · 3 comments

Comments

@boruto79
Copy link

boruto79 commented Jan 5, 2025

I was able to make a kernel 6.12.8 using a tarball, add linux-tool from Buildroot Git, and Busybox also. When trying to do it with a updated buildroot it keep on having issue. Question 1. is there a way to make the image bigger instead of using gparted so i have room for the pdf. 2: Is there a way to use the nvme-cl in nwipe instead of Alt-F2?

@PartialVolume
Copy link
Owner

PartialVolume commented Jan 5, 2025

  1. Edit ../board/shredos/genimage.cfg, find the line size = 280000000 that's the size in bytes. To double the size change it to size = 560000000, then rebuild ShredOS.
  2. No, at least not yet, but nvme erasure using the drives firmware is in the list of features to be added.

@boruto79
Copy link
Author

boruto79 commented Jan 6, 2025

Okay thanks, Another question can you add an option to read the firmware and add make, model, asset tag and serial number of the computer. will help a lot to keep track of the pdfs.

@PartialVolume
Copy link
Owner

can you add an option to read the firmware and add make, model, asset tag and serial number of the computer. will help a lot to keep track of the pdfs.

Yes, that's in progress, it will be a host specific PDF report showing host details and all the drives on the host that were wiped. Nwipe will produce both types of certificates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants