From: | daniel@×××××.nl |
---|---|
To: | gentoo-user@l.g.o |
Subject: | Re: [gentoo-user] e2fsck -a /dev/sdb1 |
Date: | Thu, 15 Jun 2017 19:43:00 |
Message-Id: | 6a6e5cdd-634b-4cc5-9531-5c7a03e66b49@email.android.com |
1 | On Jun 15, 2017 9:28 PM, Mick <michaelkintzios@×××××.com> wrote:
|
2 | |
3 | |
4 | |
5 | > I was under impression that ext4 file system was much better (not prone |
6 | |
7 | > to these kind of damages) but I was wrong. |
8 | |
9 | > |
10 | |
11 | > -- |
12 | |
13 | > Thelma |
14 | |
15 | |
16 | |
17 | If you remove the USB disk while the PC is accessing it, the electrical |
18 | |
19 | discharge across the physical contacts of the USB connector can cause terminal |
20 | |
21 | damage to the onboard chipset controller. |
22 | |
23 | |
24 | |
25 | If you're lucky only partial corruption of the filesystem occurs and the USB |
26 | |
27 | disk can be used again. If you are very lucky and no I/O operations were |
28 | |
29 | being performed at the time the USB will suffer no damage. I try to remember |
30 | |
31 | to unmount the USB before I remove it, but I had to learn this the hard way. |
32 | |
33 | -- |
34 | |
35 | Regards, |
36 | |
37 | Mick |
38 | This is the first time I heard about discharge damage while unplugging. I highly doubt that but for curiosity sake I like some document proving/explaining this. What I think is more likely is, flash memory needs special consideration when writing to. If the driver inside the USB flash drive did not have enough time to write out all it's accounting data on where to write stuff and it's cycles, the flash will be damaged. At least I assume this holds for flash as it does for SSD. Both are limited in write cycles, and I'd assume both use a similar technique, though I have no proof to back this up. Greetings, Daniel |
Subject | Author |
---|---|
Re: [gentoo-user] e2fsck -a /dev/sdb1 | Mick <michaelkintzios@×××××.com> |