You do not say what type and brand of USB key you are using. US keys are not all born equal.
What about getting a new one?
Running 7.4.2 on a USB boot device.
The whole thing works perfectly time after time after time ...
... until it doesn't, and the message "Boot error" comes up.
In the past I've tried chkdsk /f or dd-ing a library copy of sector 1 or even defrag (crazy, it takes forever) but now I just sigh and reformat.
I know USB devices have "lifetimes" but these are intermittent recoverable failures, not deaths.
The device is used 2,3,4,... times a day. The failures occur maybe 4 times a year. I am not aware of any consistent lead-up to failure.
Anybody else getting the same sort of behaviour?
Fergus
You do not say what type and brand of USB key you are using. US keys are not all born equal.
What about getting a new one?
>> What about getting a new one?
Good question - sorry, I should have said. The device is a super-expensive 200G Sandisk micro-SD in my phone, partitioned as 8G FAT32 + 192G exFAT.
I jut plug the phone in via USB cable and away I go.
(So I only have one device, containing EVERYTHING for my cyber-life, and can rove workstations. Everything I need at home/ work including archived material lives on 192G, admittedly just approaching capacity. I'm not interested in music or video which is why this can be achieved, and it's also why I don't want to lose the amazing convenience of this architecture. I'll upgrade the chip if Sandisk offer greater capacity, but just a straight 200G replacement would feel very expensive and not really necessary at this time.)
Thanks for comment. Still don't understand the reason for the error. That partition has almost no usage at all - and only read, not write.
Fergus
So you are not talking about a common USB flash drive but rather about a micro-SD card.
I know nothing about the reliability of such cards. I hope someone ellse can help you with an answer to your question.
More of the same today. Yet another "Boot error" on startup. I will write this while I reformat the card as a KNOPPIX bootable drive.
If I cannot actually understand and defeat this phenomenon, I would at least like to keep track of time-between-failures and number-of-successes-between-failures.
Is there a line that I could introduce into syslinux.cfg that would be enacted exactly once at a successful boot and that would augment an increasing "record" of successful boots?
I guess I mean something like
date >> /mnt-system/boot/record.txt
that would build a growing historical file one line at a time.
But I do not know the syntax that would achieve this. Can anybody help?
Thank you, in growing frustration.
Fergus
A-Tech 8GB DDR3 1600 PC3-12800 Laptop SODIMM 204-Pin Memory RAM PC3L DDR3L 1x 8G
$13.99
Samsung 16GB 2Rx4 PC4-2133P DDR4-17000 1.2V RDIMM ECC Registered Server Memory
$15.49
Samsung 2 x 16GB DDR4 2Rx4 PC4-2133P-R Server Memory ECC Reg RDIMM M393A2G40DB0
$29.99
A-Tech 8GB PC3-12800 Desktop DDR3 1600 MHz Non ECC 240-Pin DIMM Memory RAM 1x 8G
$13.99
HyperX FURY DDR3 8GB 16GB 32GB 1600 MHz PC3-12800 Desktop RAM Memory DIMM 240pin
$12.90
Micron 16GB 2Rx8 PC4-3200AA DDR4 Laptop Memory Ram MTA16ATF2G64HZ
$21.95
Corsair Vengeance LPX 16GB (2x8GB) Memory Kit (CMK16GX4M2A2666C16)
$35.99
SK Hynix 8GB (2x4GB) 1Rx8 PC3L-12800 DDR3-1600MHz Laptop Memory HMT451S6AFR8A-PB
$8.25
A-Tech 256GB 4x 64GB 4Rx4 PC4-19200 ECC Load Reduced LRDIMM Server Memory RAM
$287.96
Micron 32GB 2RX4 PC4-2400T-RB1-11 Registered ECC Server Memory RAM
$32.95