When a mistake is found, it sets a bit that makes the whole card read-only. That’s not great.Īdd to your explanation that the controller in an SD card looks for mistakes in its EPROM. I have a USB SSD waiting in the wings in case this happens again, but I’d prefer not to dedicate it to this problem.Īlso the PI4 runs hot. I’m currently trying with a USB Flash stick, but I really don’t know if this is more resilient to the write problem. But your system shouldn’t become unworkable. No other modern operating system has the problem - sure, if you interrupt power, whatever is in your cache should be toast. When a write happens to microSD card, if power is interrupted, the card goes into a locked mode that is basically unrecoverable.
This is all a workaround because I have destroyed too many microSD cards using the openhabian image (probably would happen under Raspian as well). It’s surprising to me that Etcher did not set the Active flag… but the problem existed in the Raspberry Pi OS Lite image that I used too. Among them, I booted the current version of Raspberry Pi OS (on a microSD) and used raspi-config to check the boot order and eeprom of the PI 4 (both were fine). This is after I tried a lot of different things. “detail partition” shows whether the command worked or not. “select partition X” where X is the partition number. “list partition” to find the boot paritition. “select disk X” where X is the disk number. In diskpart, I used “list disk” to find the disk.
(CMD would probably work too.) Then started DISKPART.
#FLASH OS IMAGES TO SD CARDS WINDOWS#
To do this, under Windows 10, I launched a Cygwin shell with administrator privileges. Tl dr To get a USB flash drive to boot, I needed to use diskpart to make the boot volume “active.”
0 kommentar(er)
