| 1 |
Nikos Chantziaras wrote: |
| 2 |
> On 13/12/2018 11:18, Dale wrote: |
| 3 |
>> Nikos Chantziaras wrote: |
| 4 |
>>> |
| 5 |
>>> I'd recommend just using mkfs instead of using your own parameters: |
| 6 |
>>> |
| 7 |
>>> mkfs -t ext4 /dev/sdb1 |
| 8 |
>>> |
| 9 |
>>> It will use the parameters from /etc/mke2fs.conf. This is the safest |
| 10 |
>>> way to format a partition. |
| 11 |
>>> |
| 12 |
>>> |
| 13 |
>>> |
| 14 |
>> |
| 15 |
>> May try that next, if it ever finishes this current attempt. It's been |
| 16 |
>> a hour for the current format attempt. I won't be surprised if it gives |
| 17 |
>> up too. |
| 18 |
> |
| 19 |
> Did you check for any errors in dmesg? |
| 20 |
> |
| 21 |
> |
| 22 |
> |
| 23 |
|
| 24 |
|
| 25 |
OK. This is what I did this time. First, I dd'd the drive, the first |
| 26 |
several gigs worth to be sure the partition table etc is gone. Second, |
| 27 |
I ran portprobe for it to see the partition was gone. It would still |
| 28 |
show up in /proc/partitions. I then used gdisk to create the |
| 29 |
partition. I might add, cgdisk would not run. It spit out a error and |
| 30 |
quit. Then I ran partprobe again. May have ran it twice. Then it |
| 31 |
showed up in /proc/partitons as it should. Then I used your advice and |
| 32 |
used mkfs -t ext4 and other options for label etc to format the |
| 33 |
partition. That gave me this: |
| 34 |
|
| 35 |
|
| 36 |
root@fireball / # time mkfs -v -t ext4 -m 0 -L 8tb-backup /dev/sde1 |
| 37 |
mke2fs 1.43.9 (8-Feb-2018) |
| 38 |
fs_types for mke2fs.conf resolution: 'ext4', 'big' |
| 39 |
Filesystem label=8tb-backup |
| 40 |
OS type: Linux |
| 41 |
Block size=4096 (log=2) |
| 42 |
Fragment size=4096 (log=2) |
| 43 |
Stride=0 blocks, Stripe width=0 blocks |
| 44 |
244191232 inodes, 1953506385 blocks |
| 45 |
0 blocks (0.00%) reserved for the super user |
| 46 |
First data block=0 |
| 47 |
Maximum filesystem blocks=4102029312 |
| 48 |
59617 block groups |
| 49 |
32768 blocks per group, 32768 fragments per group |
| 50 |
4096 inodes per group |
| 51 |
Filesystem UUID: ebcd0ad4-f25f-466e-9b5c-acac33886df0 |
| 52 |
Superblock backups stored on blocks: |
| 53 |
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, |
| 54 |
2654208, |
| 55 |
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, |
| 56 |
102400000, 214990848, 512000000, 550731776, 644972544, 1934917632 |
| 57 |
|
| 58 |
Allocating group tables: done |
| 59 |
Writing inode tables: done |
| 60 |
Creating journal (262144 blocks): done |
| 61 |
Writing superblocks and filesystem accounting information: done |
| 62 |
|
| 63 |
|
| 64 |
real 37m50.570s |
| 65 |
user 0m0.121s |
| 66 |
sys 0m1.639s |
| 67 |
root@fireball / # |
| 68 |
|
| 69 |
|
| 70 |
Before you freak out, I did move the drive to another port when I |
| 71 |
changed the cable. It moved from sdb to sde. I always confirm using |
| 72 |
smartctrl -i until I find the right device. |
| 73 |
|
| 74 |
After all that, I get this: |
| 75 |
|
| 76 |
|
| 77 |
204,807,599 100% 120.79MB/s 0:00:01 (xfr#7946, ir-chk=3715/13065) |
| 78 |
|
| 79 |
120,136,339 100% 77.20MB/s 0:00:01 (xfr#7947, ir-chk=3714/13065) |
| 80 |
|
| 81 |
119,445,345 100% 94.38MB/s 0:00:01 (xfr#7948, ir-chk=3713/13065) |
| 82 |
|
| 83 |
109,298,753 100% 100.81MB/s 0:00:01 (xfr#7949, ir-chk=3712/13065) |
| 84 |
|
| 85 |
116,704,897 100% 82.38MB/s 0:00:01 (xfr#7950, ir-chk=3711/13065) |
| 86 |
|
| 87 |
110,075,610 100% 92.49MB/s 0:00:01 (xfr#7951, ir-chk=3710/13065) |
| 88 |
|
| 89 |
115,757,218 100% 106.46MB/s 0:00:01 (xfr#7952, ir-chk=3709/13065) |
| 90 |
|
| 91 |
111,693,138 100% 128.49MB/s 0:00:00 (xfr#7953, ir-chk=3708/13065) |
| 92 |
|
| 93 |
208,458,508 100% 56.93MB/s 0:00:03 (xfr#7954, ir-chk=3707/13065) |
| 94 |
|
| 95 |
113,847,275 100% 88.92MB/s 0:00:01 (xfr#7955, ir-chk=3706/13065) |
| 96 |
|
| 97 |
181,249,801 100% 79.22MB/s 0:00:02 (xfr#7956, ir-chk=3705/13065) |
| 98 |
|
| 99 |
215,941,705 100% 146.99MB/s 0:00:01 (xfr#7957, ir-chk=3704/13065) |
| 100 |
|
| 101 |
|
| 102 |
Now I knew this wasn't the fastest drive out there. It puts a little |
| 103 |
more on living a long life at the expense of a little speed. However, |
| 104 |
this is MUCH MUCH better than I was getting. Since I have a good size |
| 105 |
drive now, I'm backing up /home and excluding things I don't care about |
| 106 |
like cache and files in the trash etc. It's a progressive thing. |
| 107 |
|
| 108 |
At this point, I don't know if it was the cable, me running partprobe or |
| 109 |
both that did this. It could also be running mkfs instead of mkfs.ext4 |
| 110 |
as well. Who knows. I'm just glad to have some SPEED. O_O |
| 111 |
|
| 112 |
Thanks much to all. |
| 113 |
|
| 114 |
Dale |
| 115 |
|
| 116 |
:-) :-) |
Archives