When I put in my bootable USB with the OS it just shows a black screen with a white blinking cursor on the top left corner. I wait for hours (to be specific 5 whole hours) waiting for something to happen but I get nothing, so I pull out the USB and my Ubuntu 12.04 loads up.
Repeated this several times with putting different boot priority options on top-est that relate to USB but the results are same. I go and visit some sites on the net like this -replace-ubuntu-with-windows.175716/ that say I have to zero out my hard drive.
If I have to lose my primary OS (Ubuntu 12.04) in the process I am ready to as my aim is just to install Windows 7 successfully. Please don't answer that there is something wrong with my USB or my USB reader/port/hardware or the content inside the USB cause they all works fine on my brothers PC as it boots up flawlessly.
What's the purpose of sync? Simple: in case if your storage is slow and power off happens right after dd while disk data is not synchronized, some of the data might be lost. It might be not so relevant for this particular case about zeroing out the drive on PC, but for things like embedded systems with slow flash memories this needs to be considered.
Maybe I can add a little insight here. When booting with a Windows CD, the Windows installer program is kind of stupid and worthless as most Microsoft products are. What can end up happening is the operating system of the Windows installer CD will hand and die. Mostly because it doesn't know what to do with a hard drive that is not zero'd, or doesn't have Windows. It doesn't give an error, just hangs.
I happen to have a perfect example right in front of me right now. Even when I boot with an Ubuntu CD, on this ASUS computer, the OS, begins to start, then it touches the hard drive, as any good OS should do, in order to see what resources are present.
On this particular computer, (and the problem is with the BIOS of the particular machine) it appears to hang, for almost 20 minutes, for each touch of the hard drive. So booting a live CD on this computer can take almost 20 minutes. Just in case, I'd check for a BIOS upgrade on your system, it will prolly fix the USB booting issues and maybe the timeout routine for no hard drive access, although that's more unlikely.
If you can boot from the live CD, just let it sit. Shouldn't take more than an hour, if you have the same booting flaw as this machine. Once it comes up, do the HD zero out, in a pinch though, boot with your Ubuntu on HD, and zero it out anyhow. It should zero out enough before the OS crashes to allow your worthless Windows install CD to work.
I am not sure why some folks prefer to pay the fees upfront, but I always go with Zero drive-off w/ all fees rolled into the lease. In most cases, I get out of my lease early so technically I pay less in fees.
I guess if the MF is high then you are paying interest on the fees which could be avoided if you paid it upfront. I think it is down to your personal circumstances, if you just got a bonus and want to reduce you monthly then paying them upfront would help.
We, and our partners in the Netherlands, are helping top global government officials and private sector innovators reach an ambitious goal of 100% new zero-emission medium- and heavy-duty vehicle sales by the year 2040 under the Global MOU.
I have macOS 10.15.2, I have erase the data drive, recreated it, encrypted it, deleted and recreated and still am able to recover data from the drive using recovery software. Is there a way to zero the bits, Orr am I going to be unable to sell this computer?
Yes, that is the primary issue I have. I followed it, but the data is still recoverable. I have also utilized FileVault to encrypt the drive, then erased it, then created it again and the data is still there. Using Disk Drill now and it is picking up over 50GB of files right now
I was also, but I work in security and when you select erase and it erases and reformats a drive in under 60 seconds I became skeptical. I am questioning the true value of encrypting the volume after waiting 4 + hours for it to do so, then delete it. You open recovery software on new volume and it is picking up the same files. Very disappointing.
I would assume that using super eraser, you would merely put all files you want erased into the trash, then empty the trash, and then they will then be written over since they would be identified as free space. Am I missing something here?
Assuming a fairly recent computer with middle-grade drives, on a minimal linux boot disk running JUST the zeroing operation (no gui, internet, etc) loaded entirely to RAM, it could be anywhere from 2-12 hours. If I had to throw a single number out, I'd say closer to 3 and a half hours, but again, there's not enough information to get a good estimate other than actually doing it.
If you have more than 1GB free space, you could try mounting the drive and running dd if=/dev/zero bs=512 count=2048 of=/tmp/tempzero or some other file. If you know more about the optimal block size for fastest writing to your drive, you can use that for the bs value (in kilobytes) and set the count to whatever gets you the filesize you want. Then you can use that to get a better estimate without losing data. It will just create a large file that contains zeros.
I did a dd with random data on a 750GB drive. I think it took about 20 hours. The thing that really sucked about it, is I had to do that four times for a four disk RAID array. I think the bottleneck is the write speed of your drives. You're being smart to do it to the drives in parallel.
My guess, on the order of hour or hours. Days seems long. Depending on how your machine is set up, running both at the same time may actually slow things down if you create contention for the drive controller. Even though you're pumping out zeros, nothing in your drive knows that and it needs to write every byte.
If you're just erasing the drives, a great tool to use for parallel throughput is DBAN in simple erase mode. It's available as an ISO and basically does the dd if=/dev/zero command for you on the drives you select.
It should take 2-5 hours. Your bottleneck is the disk, not the RAM, the CPU, the cables or controller configuration. Unless you have a very old computer, like an original Pentium, your CPU and memory are way faster than the hard disk's spindle speed, as are your SATA cables. Cache does not even come into play because you are zeroing the drive (unless you have 1 TB of cache).
Drive to Zero focuses on reducing injuries and fatalities on our roadways. Our goal is to reduce fatal and serious injury crashes to zero by 2035. Based on recent data, this could save 32 lives and prevent 250 serious injuries every year in Clackamas County.
Determine if the intersection meets criteria to build a traffic signal. If criteria is met, both a traffic signal and a roundabout will be evaluated to determine which solution would provide the best value. A traffic signal design would likely add southbound and eastbound left-turn lanes and a westbound right-turn lane.
Construct sidewalks on both sides of SE Webster Road from Bilquist Elementary School to the existing Tri-Met transit stop at SE Roots Road, widen bike lanes to 8-feet and add a buffer area between bikes and vehicles. Crosswalk upgrades include adding lighting, a center pedestrian refuge and constructing curb ramps to comply with Americans with Disabilities Act (ADA) requirements to provide access for people with disabilities.
Apply a high friction surface treatment approximately between MP 5.05 to MP 5.35 near Kraxberger Road, add two radar-activated curve warning signs with lights, and add reflective material to curve warning sign posts to enhance their visibility.
Provide 6-foot separated sidewalks on both sides of Courtney Avenue; 8-foot buffered bike lanes; intermittent rain gardens for stormwater management; street and pedestrian lighting and ADA compliant intersection curb ramps; and crosswalk enhancements at two intersections.
Install a radar detection system to detect vehicles as they approach the Knights Bridge Road/Arndt Road intersection and add signal ahead signs and pavement markings to alert drivers of changing conditions.
Wearing the right motorcycle helmet can mean the difference between life and death. We know it can also mean the difference between a comfortable and miserable ride. Learn more from our partners at NHTSA.
I want to remove two empty data drives from my array. Normally I would just verify parity, remove the drives, then initconfig. However, for kicks, I decided I want to try the method of zeroing out the drives before removing them, thereby avoiding the lengthy (and slightly risky) parity sync.
Zeroing disks involves updating parity. Doing multiples may be pretty rough on the parity drive and slow things down so much that it might make more sense to run them sequentially. Maybe you can do some experimenting and let us know if running in parallel is faster.
Here's what happened. I followed your instructions in the link above (though specifying the block size as 2048 as Joe suggested). The disk did NOT immediately show up as 'unformatted' as expected. Instead, it immediately showed up as having 0 free space (see disk9 in the screenshot below). However, the writes to that drive and the parity drive were incrementally increasing in unison, so I let it continue. When I came back hours later, the writes have all stopped, so I assume it is done. I'm tempted to contine with the proceedure as normal, but I figured I should get some feedback before I do.
Huh, weird, I could have sworn I attached it. Anyway, I'll have to do it when I get home tonight, I don't have it with me. I'm not sure how helpful it will be, though, since it just has two errors repeated over and over.
c80f0f1006