Reply
SanDisk Guru
Posts: 2,605
Registered: ‎07-23-2010

Re: can't boot [snip]

Post your grub2 menu so we can see what you're working with.

 

Some boot problems are equipment related; low power, heat, low RAM, conflicting USB devices, maxed out USB hub, oxidized electrical contacts.

 

Ed
Important files = Backed up files
Newbie
Posts: 6
Registered: ‎07-09-2018

Re: can't boot [snip]

Ed_P, I don't know how much of this thread you've read (I genuinely don't), but it's quite certain if you read through it that the problem here is a bug within the firmware of some of these Ultra Fit 32GB drives, not anything in any particular with the OS or bootloader configuration.

To be sure, I'm able to boot this *exact same* image, a fresh install of Linux Mint, from practically any other thumb drive, using the standard, out of the box, default grub configuration, except for with this Ultra Fit 32GB drive.

The reason I posted was that I got the impression that some people had found a *specific* workaround for the buggy behavior with these Ultra Fit 32GB drives. That's all I'm looking for. I'm not using any non-default grub configuration, it's exactly as-is from a fresh Linux Mint install. I'd love to *know* some non-default grub configuration that would workaround the issue, though. Smiley Happy

SanDisk Guru
Posts: 2,605
Registered: ‎07-23-2010

Re: can't boot [snip]

I responded to your recent posting mmortal03, the other postings are 2 - 3 yrs old.  Drives manufactured today are not the same as they were 3 yrs ago.

Ed
Important files = Backed up files
Newbie
Posts: 6
Registered: ‎07-09-2018

Re: can't boot [snip]

Thanks for replying. This one is actually one of the older drives from a few years ago, not one I've recently purchased. I've been dealing with the issue for a few years now. Btw, a new finding, it *will* boot up without issue on a Samsung Series 7 Chronos laptop, but not on two or more other laptop models that I've tried it on. I don't know what the common denominator is. Could be slower processor machines, or it might be some weird incompatibility with various USB hardware? How might the in-depth explanation that jdb2 gave apply to some machines and not others?

SanDisk Guru
Posts: 2,605
Registered: ‎07-23-2010

Re: can't boot [snip]

[ Edited ]

Different machines = different hardware = different drivers and different states of oxidation, dust, rust, power supply voltage and obsolesence.

Ed
Important files = Backed up files
Newbie
Posts: 6
Registered: ‎07-09-2018

Re: can't boot [snip]

No doubt those things might affect certain situations, but here is how I can rule that sort of stuff out. If I make an image of the Ultra Fit, write that image to another thumb drive, and insert that other drive into the *same* laptops, the problem isn't there. And the Ultra Fit has been doing it from the beginning, so it's not as if the Ultra Fit has oxidized or rusted or what have you and is only now showing the problem -- it always has.

Highlighted
SanDisk Guru
Posts: 2,605
Registered: ‎07-23-2010

Re: can't boot [snip]

[ Edited ]

Ok, that eliminates some possibilities. 

 

If the SanDisk drive works fine other than booting the problem is MBR related.  Are the SanDisk drive and the "another drive" both formated the same way, with the same block alignments and MBR locations?

Ed
Important files = Backed up files
Newbie
Posts: 6
Registered: ‎07-09-2018

Re: can't boot [snip]

Yes, I do believe so. The exact same dd raw image that I'm writing to them should very well contain the same boot record and the same formatting, block alignments, and everything, unless I'm missing something. I really think the problem is something lower level than this, like in the firmware of the SanDisk Ultra Fit 32GB or what have you. I really just thought someone here had a workaround. I doubt we'll be able to discover the cause without lower level tools and detailed knowledge of the firmware.

SanDisk User
Posts: 24
Registered: ‎05-10-2015

Re: can't boot [snip]


@mmortal03 wrote:

"I've dealt with this issue for a while with my own SanDisk Fit 32 GB USB 3.0 thumb drive, and had come across the remove and re-insert trick somewhere, but I'd never found a permanent fix. I just read jdb2's suggestion above from 2015, and his follow-up from 2016, but none of what he suggests seems to fix the problem for me. I tried adding those various parameters to the grub default boot line, making sure to update grub and everything, but none of them on that rootwait ... line, nor any of the "quirks" parameters that I could discern seemed to work. Maybe I didn't use the right quirks parameters? What did other people actually use?"

 

Well, I'm sorry that my suggested solution didn't work for you Smiley Sad. I didn't work for me either which is why I started using a chain bootloader.

 

"Also, it's not clear how that "kiyoshi's help" boot loader would help in this instance. Is there not just a straightforward config that is known to work with these faulty drives and, say, a standard Linux Mint Cinnamon install (with no special bootloader config required)?"

 

Well, "kyoshi's help" just searches your system for boot loaders and then presents you with a menu which lists the various boot loaders that the "kyoshi's help" can chain load. I my case, my boot-loader was GRUB on ext4. It's a big kludge though and it's inconvenient because I had to burn "kiyoshi's help" to a DVD and then I'd boot off of the DVD and then I'd select the boot-loader for my LInux Mint install, which was in an USB slot, and then my install would be chain-booted successfully


 

I hope this helps,

 

jdb2

SanDisk Guru
Posts: 2,605
Registered: ‎07-23-2010

Re: can't boot [snip]

"The exact same dd raw image that I'm writing to them should very well contain the same boot record and the same formatting, block alignments, and everything,"

 

I'm not sure that is true, especially the block alignments on different drives.

 

Rather than copying images to the drive, install a system to it.  Get the ISO of the system you want and use something like RMPrepUSB or Easy2Boot to install it to the USB drive then see if it boots.

Ed
Important files = Backed up files