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
NEW Original OEM 60W Power Adapter Charger A1344 for APPLE 13" MacBook Pro A1278
$22.24
85W OEM NEW Power Adapter Charger For Apple Macbook Pro 13 15" A1424 A1502 A1398
$24.24
Original OEM 87W USB-C Power Adapter Charger for Apple MacBook Pro 15" 13" A1719
$28.44
OEM Apple MacBook Pro 13 A1706 A1708 2017 LCD Screen Display Assembly Silver
$115.31
Genuine Apple A1718 61W USB-C Power Adapter Apple OEM CHARGER
$24.99
Genuine OEM Apple 10w USB Wall Charger Adapter iPhone iPad with Lightning cable
$6.99
APPLE OEM Original Cinema Display (Aluminum) Power Supply AC Adapter 65w or 90w
$13.99
OEM 61W USB C Type C Adapter Charger for Apple MacBook PRO 13" A1718 + Cable NEW
$23.00
OEM Apple MacBook Pro 15" LCD Screen Display 2018-2019 A1990 Space Gray Grade C
$150.00
OEM 30W USB-C Power Adapter Charger for apple MacBook Air iPhone 11 12 Pro +Cord
$22.89