-
Notifications
You must be signed in to change notification settings - Fork 20
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
Imaged drive details #260
Comments
Take a look at the example zuluscsi.ini: |
Thanks for the response. I meant implement features in the initiator function, I see that you can write the serial number, but you have to know it first. |
Same here. When I look at the logs, it shows the drive size, but doesn't pull information, like vendor, product, version, and serial. blah blah blah Even pulling geometry reported might be nice, say when imaging drives and then deploying said image via ZuluSCSI on a similar or same host that's expecting that same drive (but doesn't have to know it's emulated, of course). Another nice advantage of such a feature is if we're imaging multiple drives, that happen to be on ID 0 because they don't have jumpers, and I don't want to have to figure out which drive is what image, when I could look at zululog.txt and identify that image by drive model/serial/etc. I stand slightly corrected. |
Maybe add a option to write more drive details , serial number, etc to a base ini file. Maybe this exists already? If a software license is locked to a drive serial number it would be nice to accomodate this.
The text was updated successfully, but these errors were encountered: