It also managed to corrupt my VM's disk somehow on the first attempt (yes, I'm sure I chose sda, which is mapped to a 7.4GB drive - I triple checked). I cannot run with -p anymore because it is now marked as read only. It still does the same Free cluster summary wrong afterwards. chkdsk now reports nothing is wrong, and fsck still reports MBR inconsistencies, but now always chooses first FAT automatically after telling me FATs differ. However the inability to do so even on a bootable disk indicated something more serious is wrong. This is when I ran through the attempts listed above, to try and reformat it in case of a faulty format. After a few attempts, it started coming up as read only on insertion. On reconnect, it would come up as normal but a write operation would cause it to go read only again. Disk management reported it as read only. Plugging it back in, it came up as normal - however, any write action would fail. The drive at this point was already formatted, SYSLINUX already installed, just waiting on the unpacking of an ISO and the modifying of the boot menus. After waiting for about fifteen minutes (longer than the 3.5GB Knoppix ISO took last time), I pulled the drive out. The format was successful, however, the extract and copy of Kubuntu (which YUMI uses a 7zip binary for) froze at about 60% done. I used YUMI's built in reformat (to FAT32) option and installed a Kubuntu ISO (700MB). My next attempt was to use YUMI, again, to rebuild the whole drive. Halfway through fixing the files, the VM froze - I ended its process about ten minutes later. To try to fix something, at least, I ran it with the -p option. If I chose Correct, it gave a list of incorrect file names. Whichever I selected, I got a notice of Free cluster summary wrong. It told me FATs differ and asked me to select either the first or second FAT. There are differences between boot sector and its backup. I umounted it ( /dev/sda1) and ran a fsck. I decided to give fsck a shot, so I loaded up my Kubuntu VM and attached the drive to it with VirtualBox's USB 2.0 passthrough. Running the standard Windows chkdsk scan without /r or /f reported errors found. I tried reinserting the drive to delete this file - without safely removing, if that made a difference (hey, first time for everything). In the old Knoppix folder, there was a 0 byte file named KNOPPIX that could not be deleted. However, the free space was stuck at about 700MB, same as it was before removing Knoppix. The files went first, then the menus were cleared successfully. I then went through YUMI to 'uninstall' Knoppix, i.e. The drive was nearly full (45MB free), so I deleted a generic ISO that also was not booting. I was thinking the Knoppix files may have been corrupted somehow, so I tried reloading it. On the attempt to boot, Knoppix reported some form of LZMA corruption. ttys 1 through 6 still worked as text only interfaces.Ī few days later, I took some time to take that odd video option off, making the boot command match the one that comes with Knoppix. When I tried to put the Knoppix DVD on, YUMI added an odd video option to its boot comman which caused Knoppix to boot with a black screen on X. I had thrown quite a few Linux distros on, along with a copy of Hiren's. The end usable space was about what I normally expect from a 8GB drive (approx 7.4 GIBIbytes). Approximately 127MB was listed as "used" by Windows. It came formatted as FAT32, though oddly a little larger than most 8 GIGAbyte flash drives I've come across. This was a brand new, generic, 8GB flash drive I wanted to create a multiboot flash drive with. Kubuntu fsck (through VirtualBox USB passthrough): see below for detailsĪcronis True Image to format, to convert to GPT, to destroy and rebuild MBR, basically anything: failed (could not write to MBR) See the System Event Log for more information.Ĭannot format. Attempted solutionsįormatting it in Windows (in Disk management, the format options are greyed out when right clicking).ĭiskPart Clean ( CLEAN - Clear the configuration information, or all information, off the disk.): DISKPART> cleanĭiskPart has encountered an error: The media is write protected. What really confuses me is Current Read-only State : Yes and Read-only : No. The drive itself has somehow become locked in a read only state. It's certainly not been used enough to die from normal wear and tear, though I would not discount defective components. Why did this happen? Is it fixable? If it is, how can I fix this?įirstly, this drive is new. I have a brand new flash drive (one week old) that has become marked as read only, by Windows, Kubuntu and a bootable partitioner.
0 Comments
Leave a Reply. |