Re: Intel DQ67SW motherboard, SanDisk Ultra Fit USB 3.0 128 GB flash drive, and Debian 7.11 amd64
On 08/01/2016 06:51 PM, Rick Thomas wrote:
> What version of the util-linux package are you using?
>
> Please see us the output of
> aptitude versions util-linux
2016-08-01 19:21:49 root@i72600s ~
# aptitude versions util-linux
Package util-linux:
i 2.20.1-5.3
oldstable
500
Package util-linux-locales:
i A 2.20.1-5.3
oldstable
500
> Jessie seems to have 2.25.2-6, while Stretch has 2.28-6. Maybe the “-w” (alias “—follow”) option was added between the two?
The --follow option does not seem to exist in the dmesg on Wheezy:
2016-08-01 19:21:59 root@i72600s ~
# man dmesg | grep follow
> In any case, you might be able to get the same results by doing
>
> dmesg > /tmp/part1
> … do your experiments …
> dmesg > /tmp/part2
> diff /tmp/part1 /tmp/part2
I've attempted something similar, but the system becomes unstable once I
plug in the flash drive and I can't obtain information.
> Do you get the same problem if you use a USB2 socket instead of the second USB3?
The flash drive works correctly on the USB 2.0 ports.
> Maybe the mainboard can’t handle the data rate from two simultaneously active USB3 ports?
I doubt it -- the system malfunctioned immediately upon inserting the
flash drive into the second USB 3.0 port.
Fortunately for operations (and unfortunately for debugging; e.g. this
thread), I connected the drive to a USB 2.0 port, everything was fine,
so I wiped the first 100 MB, set it up using parted mklabel, parted
mkpart, cryptsetup luksFormat, cryptsetup luksOpen, mkfs.ext4, and now
it works just fine in the USB 3.0 port.
Therefore, I suspect the problem is Debian software failing on data it
doesn't like (e.g. something unexpected in the SanDisk factory image).
While I do have an image of the flash drive, I don't know the
architecture of Debian or Linux. So, I won't know where or how to
troubleshoot it.
I re-imaged an older SanDisk Ultra Fit USB 3.0 16 GB flash drive and
tried that -- it seems to work correctly in the motherboard USB 3.0 port.
I seem to recall seeing the same problem with newer SanDisk Ultra Fit
USB 3.0 16 GB flash drives. Unfortunately, I don't have one available
to experiment with.
I do like your idea of starting a debugging stream when the system is
running, plugging in a flash drive, and then watching the debugging
stream for clues. The following shows useful information when I plug
and unplug USB flash drives:
# tail -n 20 -f /var/log/kern.log
I'll post a follow-up if and when I run into this issue again.
Thank you,
David
Reply to: