Hi again, fullzero and all 
I've got a question for you. Some of my rigs now have a problem booting from USB stick. I have many different sticks but after a month or two of normal booting some of them started to fail on booting process, I/O errors etc... I understand that this is a quality problem in most cases, but also I think it's the usecase problem. So now I'm thinking of nvOC/rxOC mod that could do network booting to completely exclude this kind of issues while using these distros. The question is - have someone tried to boot nvOC from network? If yes, please share your experience to us!
I've got a question for you. Some of my rigs now have a problem booting from USB stick. I have many different sticks but after a month or two of normal booting some of them started to fail on booting process, I/O errors etc... I understand that this is a quality problem in most cases, but also I think it's the usecase problem. So now I'm thinking of nvOC/rxOC mod that could do network booting to completely exclude this kind of issues while using these distros. The question is - have someone tried to boot nvOC from network? If yes, please share your experience to us!I have made ramdisk generating / loading OS to ram; then running off ram: OS variants before. I don't think most users have enough ram for this with nvOC ~8.6 GB + space for actual system ram usage. It would also take longer to build the ram disk (longer boot).
Netboot based on a single local network hosted img; would most likely only work if all your rigs had identical hardware.
Right now using a usb to sata usb adapter with an SSD or more frequently swapping out usb key's is the easier solution.
You can usually fix most of the problems with a usb key by:
In linux open: Disks and select the broken/troubled USB Key from the list on the left.
Examine what device the Key is mounted as.
For any partition that is not listed as Free Space; select it so that it becomes orange; then look below, at the information to the right of the Device. It should look something like:
Code:
/dev/sdb1
or
Code:
/dev/sdb2
ect
depending on how many storage devices you have connected to the computer the letter after sd will be different. Assuming you have another nvOC imaged USB or SSD running and you have attached the broken USB key (with no other storage devices) the broken usb device should be:
Code:
/dev/sdb
use the cmd:
Code:
sudo dd if=/dev/zero of=/dev/sdb
to zeroize it in the guake terminal
NOTE: ENSURE YOU HAVE REFERENCED THE INTENDED DRIVE ! sudo dd if=/dev/zero of=/dev/sd(the correct final character here)
This will not appear to be doing anything for a while
It takes a while to write 0s to the entire disk.
When it is done you will get a message.
After zeroizing is complete: the usb Key (might) work normally again.