I bought some inexpensive SanDisk Cruzer Glide 16GB USB sticks from Walmart last year. Cheap. Today I copied the CentOS 8 installation image onto one. time sudo dd if=CentOS-8-x86_64-1905-dvd1.iso of=/dev/sdg oflag=direct bs=16M (I used a USB 3 port on my dessktop.) It seemed to take a long time, so I did this to see if anything was happening (the dd process' PID was 29047): sudo kill -s USER1 29047 Yes, there was progress, but not as much as I would expect. The final statistics were: 425+1 records in 425+1 records out 7135559680 bytes (7.1 GB, 6.6 GiB) copied, 1560.63 s, 4.6 MB/s real 26m4.152s user 0m0.072s sys 0m4.706s This amounts to about 4.56 MB/s. That's even less than the poor Average Sustained Write Speed 7.64 MB/s reported here: <https://usb.userbenchmark.com/SpeedTest/2718/SanDisk-Cruzer-Glide> Note: this stick hasn't been written to often. It should not be near the end of its life (that could slow down a flash device).
On 9/29/19 11:46 AM, D. Hugh Redelmeier via talk wrote:
I bought some inexpensive SanDisk Cruzer Glide 16GB USB sticks from Walmart last year. Cheap.
Today I copied the CentOS 8 installation image onto one.
time sudo dd if=CentOS-8-x86_64-1905-dvd1.iso of=/dev/sdg oflag=direct bs=16M
(I used a USB 3 port on my dessktop.)
It seemed to take a long time, so I did this to see if anything was happening (the dd process' PID was 29047):
sudo kill -s USER1 29047
Yes, there was progress, but not as much as I would expect. The final statistics were:
425+1 records in 425+1 records out 7135559680 bytes (7.1 GB, 6.6 GiB) copied, 1560.63 s, 4.6 MB/s
real 26m4.152s user 0m0.072s sys 0m4.706s
This amounts to about 4.56 MB/s. That's even less than the poor Average Sustained Write Speed 7.64 MB/s reported here:
<https://usb.userbenchmark.com/SpeedTest/2718/SanDisk-Cruzer-Glide>
Note: this stick hasn't been written to often. It should not be near the end of its life (that could slow down a flash device).
I've not needed a new flash drive in awhile but I liked the higher perfomance Kingston and Corsair drives. Not sure how much they are but last thing I checked it was pretty expensive at around 80 dollars for 128GB. Then again the speeds were good i.e. 250MBS write that it did hit and around 150MBS writes. Through if your looking for speed these are amazing as almost as fast as a SATA 3 SSD around 100MBS slower. https://www.amazon.ca/Corsair-Flash-Voyager-256GB-Premium/dp/B079NWJTGG/ref=asc_df_B079NWJTGG/?tag=googleshopc0c-20&linkCode=df0&hvadid=292955488960&hvpos=1o1&hvnetw=g&hvrand=3699258915644707733&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9061009&hvtargid=pla-473498336284&psc=1 And yes they do hit though speeds to my knowledge. Nick
--- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
| From: D. Hugh Redelmeier via talk <talk@gtalug.org> | SanDisk Cruzer Glide 16GB USB stick | 7135559680 bytes (7.1 GB, 6.6 GiB) copied, 1560.63 s, 4.6 MB/s | real 26m4.152s ================ Corsair Voyager SliderX1 32G stick: 7135559680 bytes (7.1 GB, 6.6 GiB) copied, 279.491 s, 25.5 MB/s real 4m44.206s ================ ADATA C103 USB Flash Drive 64G 7135559680 bytes (7.1 GB, 6.6 GiB) copied, 155.161 s, 46.0 MB/s real 2m38.244s ================ (the real time includes the second or two that it takes me to enter my password.) ================ [A slightly relevant Windows war story. Really a whine. Consider skipping.] I've been wrestling with Win10. It really isn't good doing Windows Update with a 32G "HDD". Why should it handle this size? Because Microsoft forced this size upper limit on manufacturers with their licensing terms. I even bought a few such machines from Microsoft itself. (They run Linux just fine.) I recently got stuck with not enough space on C: (think /root). Even when I threw everything overboard. One possible victim was left: the Paging File. It was stubbornly stuck at 1.1GiB. I wanted to put a paging file on another drive so that I could get back the 1.1G of space on C:. The documentation says that this is possible with a USB stick or SD card iff it was ReadyBoost ready. That supposedly means "fast enough". - ReadyBoost is an obsolete technology. Vendors don't sell ReadyBoost ready devices - there is a ReadyBoost tab when you look at device properties in Win10. It just tells me that it is disabled on my computer because I have an SSD c:. Not useful. I want to know about ReadyBoost ready, not actually use ReadyBoost. - the Paging File configuration setting (buried way deep in Win10) doesn't see my USB flash sticks or my SD card. - the Paging File configuration setting does see an external USB HDD. So I try that. When I reboot, Win10 says that it has to temporarily create the Paging File on C:. So this is no advance. - Microsoft Support struggle with understanding the issue. When they do, they give useless advice.
I never did get Win10 running on an HP laptop with a 32Gb drive. I gave up and went Linux, which now leaves me about 21 gb to work with. I didn't know that Microsoft provides support. First I have heard about it! Duncan
| From: D. Hugh Redelmeier via talk <talk@gtalug.org>
| SanDisk Cruzer Glide 16GB USB stick
| 7135559680 bytes (7.1 GB, 6.6 GiB) copied, 1560.63 s, 4.6 MB/s | real 26m4.152s
================
Corsair Voyager SliderX1 32G stick:
7135559680 bytes (7.1 GB, 6.6 GiB) copied, 279.491 s, 25.5 MB/s real 4m44.206s
================
ADATA C103 USB Flash Drive 64G
7135559680 bytes (7.1 GB, 6.6 GiB) copied, 155.161 s, 46.0 MB/s real 2m38.244s
================
(the real time includes the second or two that it takes me to enter my password.)
================
[A slightly relevant Windows war story. Really a whine. Consider skipping.]
I've been wrestling with Win10. It really isn't good doing Windows Update with a 32G "HDD".
Why should it handle this size? Because Microsoft forced this size upper limit on manufacturers with their licensing terms. I even bought a few such machines from Microsoft itself. (They run Linux just fine.)
I recently got stuck with not enough space on C: (think /root). Even when I threw everything overboard. One possible victim was left: the Paging File. It was stubbornly stuck at 1.1GiB. I wanted to put a paging file on another drive so that I could get back the 1.1G of space on C:.
The documentation says that this is possible with a USB stick or SD card iff it was ReadyBoost ready. That supposedly means "fast enough".
- ReadyBoost is an obsolete technology. Vendors don't sell ReadyBoost ready devices
- there is a ReadyBoost tab when you look at device properties in Win10. It just tells me that it is disabled on my computer because I have an SSD c:. Not useful. I want to know about ReadyBoost ready, not actually use ReadyBoost.
- the Paging File configuration setting (buried way deep in Win10) doesn't see my USB flash sticks or my SD card.
- the Paging File configuration setting does see an external USB HDD. So I try that.
When I reboot, Win10 says that it has to temporarily create the Paging File on C:. So this is no advance.
- Microsoft Support struggle with understanding the issue. When they do, they give useless advice. --- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
| From: dbmacg--- via talk <talk@gtalug.org> | I never did get Win10 running on an HP laptop with a 32Gb drive. I gave up | and went Linux, which now leaves me about 21 gb to work with. Windows runs fine-ish on a 32GB (not 33Gb) drive. Windows Update sometimes gets into trouble. Usually when a big change is involved (what we'd think of as an OS release). There are tricks for babying Windows Update through these big updates. But they don't always work. A clean install does work. At least in my limited experience. | I didn't know that Microsoft provides support. First I have heard about it! Yes. Just not very good. And with no commitment to success. Available through email/forum posts, chat, and phone. It's actually OK except for the fact that I don't think that they've actually solved any of my problems. In fairness, I usually don't need support for easy problems. ======== Why did I care? Why would I run Windows? Because I want to use cheap, old, little, low power boxes for things with DRM: Crave TV and in some cases Netflix. Linux and DRM are not a good mix. There's an Android TV app for Crave. It is terrible. Crave/Bell seems to have thought it a valuable jewel: they only supported Amazon's cloned Android until recently. That was a monopolistic choice, not a technical one since the app could be sideloaded onto Android TV. Accessing Crave through their web interface is OK (not great) but it demands that the browser be running on a Windows PC or MacOS. I'm sure that's a stupid unnecessary limitation, but we are talking Bell. I've phoned and complained a few times to no avail.
On Sun, Sep 29, 2019 at 11:46:07AM -0400, D. Hugh Redelmeier via talk wrote:
7135559680 bytes (7.1 GB, 6.6 GiB) copied, 1560.63 s, 4.6 MB/s
Sounds about right. If the packaging doesn't say write speed, then there is a reason why they didn't advertised it. I have 128GB Samsung USB stick, advertised 135MB/s read speed. Yes, its read speed is correct. What they didn't say is its write speed, which is about 5MB/s!! -- William Park <opengeometry@yahoo.ca>
On Sun, Sep 29, 2019 at 11:46:07AM -0400, D. Hugh Redelmeier via talk wrote:
I bought some inexpensive SanDisk Cruzer Glide 16GB USB sticks from Walmart last year. Cheap.
Today I copied the CentOS 8 installation image onto one.
time sudo dd if=CentOS-8-x86_64-1905-dvd1.iso of=/dev/sdg oflag=direct bs=16M
(I used a USB 3 port on my dessktop.)
It seemed to take a long time, so I did this to see if anything was happening (the dd process' PID was 29047):
sudo kill -s USER1 29047
Yes, there was progress, but not as much as I would expect. The final statistics were:
425+1 records in 425+1 records out 7135559680 bytes (7.1 GB, 6.6 GiB) copied, 1560.63 s, 4.6 MB/s
real 26m4.152s user 0m0.072s sys 0m4.706s
This amounts to about 4.56 MB/s. That's even less than the poor Average Sustained Write Speed 7.64 MB/s reported here:
<https://usb.userbenchmark.com/SpeedTest/2718/SanDisk-Cruzer-Glide>
Note: this stick hasn't been written to often. It should not be near the end of its life (that could slow down a flash device).
I have encountered Kinston USB3 sticks that are incredibly slow too. Some of the cheap drives are complete garbage. -- Len Sorensen
participants (5)
-
D. Hugh Redelmeier -
dbmacg＠look.ca -
lsorense＠csclub.uwaterloo.ca -
Nicholas Krause -
William Park