2019-01-03 00:26:02
yay, it eventually finished

Clueless
2019-01-03 01:37:55
@Rotonen ashift=0, disk block size 4096

Clueless
2019-01-03 01:38:10
```
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
```

Clueless
2019-01-03 01:43:28
i can only assume ashift 0 to mean 'whatever the disk lied to me at creation time'

Rotonen
2019-01-03 02:02:01
yup, apparently hardware manufacturers lie

Clueless
2019-01-03 04:17:11
run dmidecode and despair

Rotonen