usb_inst.sh not recognizing USB memory sticks (with fix)

Post there if you have problem when downloading the iso, or burning it.
MikeV
Posts: 1
Joined: 26 Nov 2013, 01:42

usb_inst.sh not recognizing USB memory sticks (with fix)

Postby MikeV » 26 Nov 2013, 02:38

I have been successfully making SRCD bootable USB sticks for some time. Today, I bought some more USB sticks (same manufacturer and size) and the usb_inst.sh is failing to detect the new sticks.

I've traced the problem to is_dev_usb_stick() in usb_inst.sh where it checks for a "1" in /sys/block/${curdev}/removable.

The problem of identifying removable USB drives has been discussed previously (both from 2010):
http://www.sysresccd.org/forums/viewtopic.php?f=5&t=3211
http://www.sysresccd.org/forums/viewtopic.php?f=1&t=3201&hilit=usb_inst.sh
but with no apparent resolution.

This may be come a more pressing matter now since Microsoft has directed manufactures, via the Windows 8 Certification process, to now report USB sticks / drives as fixed drives. This appears to be part of the "Windows To Go" requirements (see option #2 at http://blogs.technet.com/b/askcore/archive/2013/03/20/creating-bootable-usb-drive-for-uefi-computers.aspx

The USB drives that I have are from SanDisk and you can see this quite clearly stated here:
http://kb.sandisk.com/app/answers/detail/a_id/12830
with two notable quotes:
SanDisk is beginning production of flash drives configured as fixed disk in 2012 to meet new requirements for Windows 8 Certification.

and
NOTE: SanDisk does NOT support configuring flash drives as bootable device for running an OS.


I've been able to work around this in the short term by editing the usb_inst.sh script to not check for the "removable" attribute in /sys/block/${curdev}/removable.

Code: Select all

#if [ -f "${remfile}" ] && cat ${remfile} 2>/dev/null | grep -qF '1' \
#       && cat /sys/block/${curdev}/device/uevent 2>/dev/null | grep -qF 'DRIVER=sd'
if cat /sys/block/${curdev}/device/uevent 2>/dev/null | grep -qF 'DRIVER=sd'


It may be a timely because it looks like USB sticks with this "problem" are starting to make their way into the distribution channels and others will be experiencing this problem also.

Return to “Downloading and burning”

Who is online

Users browsing this forum: No registered users and 1 guest