bootable stick after bcdboot command, boot error and stick read-only
Hi.
Really strange behaviour since I used the bcdboot command to fix a Win10 installation, with the parameter /all with.
Stick does not boot anymore, and is only readable. Not to delete or to repair or to create new, the stick to work.
Here the stick from Linux dosfsck,
(Note: translation for "Das Dateisystem ist nur lesbar" = The file-system is only readable.)
Sorry, missed to mention, trying a lot, also the aomei free software, but without success.
Really strange behaviour since I used the bcdboot command to fix a Win10 installation, with the parameter /all with.
Stick does not boot anymore, and is only readable. Not to delete or to repair or to create new, the stick to work.
Here the stick from Linux dosfsck,
(Note: translation for "Das Dateisystem ist nur lesbar" = The file-system is only readable.)
Gerät Boot Anfang Ende Sektoren Größe Kn Typ /dev/sdd1 * 2048 60022783 60020736 28,6G 7 HPFS/NTFS/exFAT /dev/sdd2 60022784 60088319 65536 32M ef EFI (FAT-12/16/32) knoppix@Microknoppix:/media/sdb2$ sudo dosfsck -a -v /dev/sdd fsck.fat 3.0.28 (2015-05-16) open: Das Dateisystem ist nur lesbar knoppix@Microknoppix:/media/sdb2$ sudo dosfsck -a -v /dev/sdd1 fsck.fat 3.0.28 (2015-05-16) Logical sector size is zero. knoppix@Microknoppix:/media/sdb2$ sudo dosfsck -a -v /dev/sdd2 fsck.fat 3.0.28 (2015-05-16) Checking we can access the last sector of the filesystem Boot sector contents: System ID "mkfs.fat" Media byte 0xf8 (hard disk) 512 bytes per logical sector 512 bytes per cluster 1 reserved sector First FAT starts at byte 512 (sector 1) 2 FATs, 16 bit entries 130048 bytes per FAT (= 254 sectors) Root directory starts at byte 260608 (sector 509) 512 root directory entries Data area starts at byte 276992 (sector 541) 64995 data clusters (33277440 bytes) 63 sectors/track, 255 heads 0 hidden sectors 65536 sectors total Reclaiming unconnected clusters. /dev/sdd2: 1015 files, 55570/64995 clusters knoppix@Microknoppix:/media/sdb2$ sudo dosfsck -a -v /dev/sdd fsck.fat 3.0.28 (2015-05-16) open: Das Dateisystem ist nur lesbarThanks for reading.
Sorry, missed to mention, trying a lot, also the aomei free software, but without success.
Comments
Not really.
´clean´ does not work, from only readable.
´con MBR´, what is con (and what to do exact), please, will not work, too.
The "aomei free" only in connection, that I tried to fix it with this.
If You still need the screen-shot, OK. I need to start the Win10 laptop and to login to the forum there.
Clean says input / output device error.
More informations in system event protocol.
I am not familiar to know where - or/and how - this is to find.
(The Laptop (Windows 10) Network connection troubles just, for screen-shot sending.)
2) What PC brand, year, model #, desktop or laptop?
3) HDD, SSD 2.5", SSD M.2 SATA, SSD M.2 NVMe?
4) Hard Drive partition table MBR or GPT?
5) Aomei product tier Standard, Pro, Other? Version?
6) Windows version 10, 11, Home, Pro, Enterprise?
Please, can You give me the exact command for attributes, else I need to search in internet again, thank You ?
5) Aomei product tier: Free version.
Sorry, Win 10 is german.
SanDisk Ultra USB 3.0 Flash Drive
32 GB.
From Ventoy 1 partition as FAT 16, but has been working.
DISKPART> list disk
Datenträger ### Status Größe Frei Dyn GPT
--------------- ------------- ------- ------- --- ---
Datenträger 0 Online 298 GB 0 B
Datenträger 1 Online 298 GB 0 B
* Datenträger 2 Online 28 GB 0 B
DISKPART> attributes clear readonly
Microsoft DiskPart-Version 10.0.19041.964
VOLUME - Ändert Volumeattribute.
DISK - Datenträgerattribute bearbeiten.
DISKPART>
A Ventoy (multi-boot, ISOs) stick with Win10 ISO for repair a Win 10 installation I as last GParted command (BCDBoot, used with parameter (/all) with) did repair the Win 10 installation.
But since then the Ventoy stick does not boot anymore.
But more the bad, with trying to repair the since then ´read-only´ error, when trying all the GParted commands, delete, clean, format and so on, and also the free Aomei software, this ´read-only´ denies nearly every try to access the stick.
The log-data from the Linux command (in the first post here)
shows some infos, this stick.
Thanks a lot the companion.
I remind, in my beginning years, I did some low level formattings.
Depending on the brand, every brand has its own software for this.
SanDisk (Wikipedia) "manufactured and marketed by Western Digital".
So I need the low level format software from Western Digital.
Good idea.
"damaged": I do not think so, because the 2 troubles - not booting anymore, and the error message ´read-only´ since then, didbeging after repairing 1 Win10 installation with bcdboot (´... /all´) commend and presumably from the (/all) parameter using, quite unoverthaught unnecessarily.
It´s just too sad, that software to pay do promise to solve this, but for just to try I cannot throw money - and more than once - out the window.
Luckily I have an older version of Acronis True Image (with Drive Cleanser), which is one recommending for this at https://support-en.wd.com/app/answers/detailweb/a_id/10850/initiator/user
Thank You, let´s see. I will report.