| 1 |
Am 26.10.2015 um 15:47 schrieb Peter Humphrey: |
| 2 |
|
| 3 |
> I keep the portage tree under /usr-bits. |
| 4 |
> |
| 5 |
> # dmesg | grep sdb3 |
| 6 |
> [ 1.753508] sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 > |
| 7 |
> [ 4.833460] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: |
| 8 |
> (null) |
| 9 |
> [ 107.205918] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: |
| 10 |
> (null) |
| 11 |
> |
| 12 |
> You can see the successful mount at 4.8 s; the entry at 107 s is me mounting |
| 13 |
> it again manually. |
| 14 |
> |
| 15 |
> I've rewritten the partition label, and I've run a smartctl test which |
| 16 |
> reported no faults found. I've also just reduced the speed of the chipset, |
| 17 |
> which has three settings: good performance, better performance and turbo. It |
| 18 |
> adopts the turbo setting by default and I've now set it to "better". It's too |
| 19 |
> early yet to see if that will help. |
| 20 |
|
| 21 |
interesting ... |
| 22 |
|
| 23 |
What init-system? openrc or systemd? |
| 24 |
No trace of the actual unmount in any logs? |
| 25 |
|
| 26 |
Maybe also look/grep for the LABEL of the fs. |
| 27 |
|
| 28 |
Maybe test if using the device-name itself ( /dev/sdb3 ) or the UUID in |
| 29 |
fstab changes the behavior. |
| 30 |
|
| 31 |
I use UUIDs here without problems (with systemd). |
Archives