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
Grandstream GS-HT802 2 Port Analog Telephone Adapter VoIP Phone & Device, Black
$32.00
Yealink T53W IP Phone, 12 VoIP Accounts. 3.7-Inch Display w/o Adapter - Black
$59.99
POLYCOM - VOIP POLY EDGE E350 IP PHONE #2200-87010-025
$145.00
Cisco SPA504G 4-Line IP Phone with 2-Port Switch, PoE, LCD Display &Power Supply
$21.00
Yealink T53W IP Phone, 12 VoIP Accounts. 3.7-Inch Display w/Power Adapter - Blk
$45.00
Cisco CP-7841 VoIP Phone PoE IP Business Phone Great Condition Mult. Available
$19.99
Yealink T54W IP Phone, 16 VoIP Accounts. 4.3-Inch Color Display - Black
$98.99
Lightly Used Cisco 8811 Series VoIP phone Factory Reset great condition
$21.00
LOT OF 10 Cisco CP-7841 Desktop Business VoIP Phone w/ Stand and Handset & cord
$125.00
Cisco DX650 VoIP HD Touchscreen Video Phone - Android WiFi
$45.00