2020年03月28日

Regza HDD Copy by xfsdump and xfsrestore

REGZA側できちんと4TB−HDDを認識する機械に交換したところ、まず レグザで初期化をして、その後取り外してPCに接続してKNOPPIXで 以下の xfsdump and xfsrestore を実行するだけで コピーは無事に完了した。

巷で言うような、UUIDの複製はする必要ないみたい。(xfsdump and xfsrestore では UUIDは複製されないです)
ちゃんと元のHDDとして勝手に認識されていました。(37 Z7000の場合)

先日までは、1台のお立ち台に2つ新旧HDDをつないでESATA接続でデータコピーしていましたがその時は8時間以上はコピーに時間がかかってました。
今回は REGZA用に新規に購入した お立ち台(USB3.0)を使い別々にPCに接続してコピーしました。すると3時間で1.5TBの録画データをコピー完了しました。
1分あたり7.87GB 程度の転送スピードです。 130MB/sec 程度は出ているのでまずまずのスピードかなと。

コピー後のディスクをレグザに取り付け後、録画番組のプレビューの最初に若干不具合がありましたが、しばらくするとそれらもOKになりました。というわけで問題なくデータの引っ越し完了。

結論として、10年前からやり方が変わっていない(10年以上前の製品だしね)という事になります。
http://nnspaces.sblo.jp/article/42316179.html

今回いろいろてこずったのは、10年前のKNOPPIXを捨てて最新のKNOPPIXでやろうとしたこと(xfsdumpコマンドをあとから入れる必要があったお)とか、4TBを認識しない原因の特定に時間がかかったこととかがありました。KNOPPIXで日本語入力が普通にできたら最高の環境だなと思った。あと、Ubuntuでもおんなじことをやってみたい。
以上。


今回のコピーコマンドの控え:

knoppix@Microknoppix:~$ sudo xfsdump -J - /media/sdb1 |sudo xfsrestore -J -p 180 - /media/sdc1
xfsrestore: using file dump (drive_simple) strategy
xfsdump: using file dump (drive_simple) strategy
xfsrestore: version 3.1.6 (dump format 3.0)
xfsdump: version 3.1.6 (dump format 3.0)
xfsdump: level 0 dump of Microknoppix:/media/sdb1
xfsdump: dump date: Sat Mar 28 19:54:02 2020
xfsdump: session id: 7f4f5930-991f-40bd-80f0-31449a680eb7
xfsdump: session label: ""
xfsrestore: searching media for dump
xfsdump: ino map phase 1: constructing initial dump list
xfsdump: ino map phase 2: skipping (no pruning necessary)
xfsdump: ino map phase 3: skipping (only one dump stream)
xfsdump: ino map construction complete
xfsdump: estimated dump size: 1603201556608 bytes
xfsdump: creating dump session media file 0 (media 0, file 0)
xfsdump: dumping ino map
xfsdump: dumping directories
xfsdump: dumping non-directory files
xfsrestore: examining media file 0
xfsrestore: dump description:
xfsrestore: hostname: Microknoppix
xfsrestore: mount point: /media/sdb1
xfsrestore: volume: /dev/sdb1
xfsrestore: session time: Sat Mar 28 19:54:02 2020
xfsrestore: level: 0
xfsrestore: session label: ""
xfsrestore: media label: ""
xfsrestore: file system id: b87b48ac-6d33-4891-b53d-3cf53d224997
xfsrestore: session id: 7f4f5930-991f-40bd-80f0-31449a680eb7
xfsrestore: media id: fef30ede-94c2-4a10-aa17-2eeb2c8337dd
xfsrestore: searching media for directory dump
xfsrestore: reading directories
xfsrestore: 8 directories and 1945 entries processed
xfsrestore: directory post-processing
xfsrestore: restoring non-directory files
xfsrestore: status at 19:57:02: 37/1938 files restored, 1.7% complete, 180 seconds elapsed
xfsrestore: status at 20:00:02: 42/1938 files restored, 3.6% complete, 360 seconds elapsed
xfsrestore: status at 20:03:02: 48/1938 files restored, 5.0% complete, 540 seconds elapsed
xfsrestore: status at 20:06:02: 76/1938 files restored, 7.5% complete, 720 seconds elapsed
xfsrestore: status at 20:09:02: 84/1938 files restored, 8.7% complete, 900 seconds elapsed
xfsrestore: status at 20:12:02: 106/1938 files restored, 10.5% complete, 1080 seconds elapsed
xfsrestore: status at 20:15:02: 131/1938 files restored, 12.4% complete, 1260 seconds elapsed
xfsrestore: status at 20:18:02: 154/1938 files restored, 13.9% complete, 1440 seconds elapsed
xfsrestore: status at 20:21:02: 160/1938 files restored, 15.5% complete, 1620 seconds elapsed
xfsrestore: status at 20:24:02: 170/1938 files restored, 17.3% complete, 1800 seconds elapsed
xfsrestore: status at 20:27:02: 189/1938 files restored, 18.9% complete, 1980 seconds elapsed
xfsrestore: status at 20:30:02: 211/1938 files restored, 20.6% complete, 2160 seconds elapsed
xfsrestore: status at 20:33:02: 233/1938 files restored, 23.1% complete, 2340 seconds elapsed
xfsrestore: status at 20:36:02: 252/1938 files restored, 23.9% complete, 2520 seconds elapsed
xfsrestore: status at 20:39:02: 287/1938 files restored, 25.5% complete, 2700 seconds elapsed
xfsrestore: status at 20:42:02: 307/1938 files restored, 27.1% complete, 2880 seconds elapsed
xfsrestore: status at 20:45:02: 324/1938 files restored, 28.5% complete, 3060 seconds elapsed
xfsrestore: status at 20:48:02: 368/1938 files restored, 30.5% complete, 3240 seconds elapsed
xfsrestore: status at 20:51:02: 423/1938 files restored, 32.0% complete, 3420 seconds elapsed
xfsrestore: status at 20:54:02: 451/1938 files restored, 34.2% complete, 3600 seconds elapsed
xfsrestore: status at 20:57:02: 463/1938 files restored, 35.3% complete, 3780 seconds elapsed
xfsrestore: status at 21:00:02: 475/1938 files restored, 36.6% complete, 3960 seconds elapsed
xfsrestore: status at 21:03:02: 501/1938 files restored, 38.8% complete, 4140 seconds elapsed
xfsrestore: status at 21:06:02: 511/1938 files restored, 39.8% complete, 4320 seconds elapsed
xfsrestore: status at 21:09:02: 536/1938 files restored, 42.3% complete, 4500 seconds elapsed
xfsrestore: status at 21:12:02: 546/1938 files restored, 43.0% complete, 4680 seconds elapsed
xfsrestore: status at 21:15:02: 584/1938 files restored, 44.5% complete, 4860 seconds elapsed
xfsrestore: status at 21:18:02: 627/1938 files restored, 45.8% complete, 5040 seconds elapsed
xfsrestore: status at 21:21:02: 660/1938 files restored, 47.6% complete, 5220 seconds elapsed
xfsrestore: status at 21:24:02: 670/1938 files restored, 49.1% complete, 5400 seconds elapsed
xfsrestore: status at 21:27:02: 697/1938 files restored, 50.3% complete, 5580 seconds elapsed
xfsrestore: status at 21:30:02: 714/1938 files restored, 51.6% complete, 5760 seconds elapsed
xfsrestore: status at 21:33:02: 721/1938 files restored, 53.0% complete, 5940 seconds elapsed
xfsrestore: status at 21:36:02: 752/1938 files restored, 54.5% complete, 6120 seconds elapsed
xfsrestore: status at 21:39:02: 773/1938 files restored, 56.2% complete, 6300 seconds elapsed
xfsrestore: status at 21:42:02: 806/1938 files restored, 57.9% complete, 6480 seconds elapsed
xfsrestore: status at 21:45:02: 857/1938 files restored, 58.9% complete, 6660 seconds elapsed
xfsrestore: status at 21:48:02: 888/1938 files restored, 60.3% complete, 6840 seconds elapsed
xfsrestore: status at 21:51:02: 901/1938 files restored, 61.8% complete, 7020 seconds elapsed
xfsrestore: status at 21:54:02: 940/1938 files restored, 63.1% complete, 7200 seconds elapsed
xfsrestore: status at 21:57:02: 962/1938 files restored, 64.7% complete, 7380 seconds elapsed
xfsrestore: status at 22:00:02: 979/1938 files restored, 66.0% complete, 7560 seconds elapsed
xfsrestore: status at 22:03:02: 1010/1938 files restored, 67.5% complete, 7740 seconds elapsed
xfsrestore: status at 22:06:02: 1059/1938 files restored, 69.5% complete, 7920 seconds elapsed
xfsrestore: status at 22:09:02: 1069/1938 files restored, 70.6% complete, 8100 seconds elapsed
xfsrestore: status at 22:12:02: 1099/1938 files restored, 72.3% complete, 8280 seconds elapsed
xfsrestore: status at 22:15:02: 1113/1938 files restored, 74.4% complete, 8460 seconds elapsed
xfsrestore: status at 22:18:02: 1130/1938 files restored, 75.8% complete, 8640 seconds elapsed
xfsrestore: status at 22:21:02: 1161/1938 files restored, 77.8% complete, 8820 seconds elapsed
xfsrestore: status at 22:24:02: 1191/1938 files restored, 79.3% complete, 9000 seconds elapsed
xfsrestore: status at 22:27:02: 1214/1938 files restored, 81.3% complete, 9180 seconds elapsed
xfsrestore: status at 22:30:02: 1255/1938 files restored, 82.8% complete, 9360 seconds elapsed
xfsrestore: status at 22:33:02: 1279/1938 files restored, 84.4% complete, 9540 seconds elapsed
xfsrestore: status at 22:36:02: 1292/1938 files restored, 85.8% complete, 9720 seconds elapsed
xfsrestore: status at 22:39:02: 1325/1938 files restored, 87.4% complete, 9900 seconds elapsed
xfsrestore: status at 22:42:02: 1361/1938 files restored, 88.9% complete, 10080 seconds elapsed
xfsrestore: status at 22:45:02: 1408/1938 files restored, 90.6% complete, 10260 seconds elapsed
xfsrestore: status at 22:48:02: 1428/1938 files restored, 92.0% complete, 10440 seconds elapsed
xfsrestore: status at 22:51:02: 1462/1938 files restored, 93.5% complete, 10620 seconds elapsed
xfsrestore: status at 22:54:02: 1480/1938 files restored, 94.5% complete, 10800 seconds elapsed
xfsrestore: status at 22:57:02: 1504/1938 files restored, 96.4% complete, 10980 seconds elapsed
xfsrestore: status at 23:00:02: 1522/1938 files restored, 98.2% complete, 11160 seconds elapsed
xfsrestore: status at 23:03:02: 1539/1938 files restored, 99.9% complete, 11340 seconds elapsed
xfsdump: ending media file
xfsdump: media file size 1603639490016 bytes
xfsdump: dump size (non-dir files) : 1603611349248 bytes
xfsdump: dump complete: 11435 seconds elapsed
xfsdump: Dump Status: SUCCESS
xfsrestore: restore complete: 11435 seconds elapsed
xfsrestore: Restore Status: SUCCESS


knoppix@Microknoppix:~$ df -ht xfs
Filesystem Size Used Avail Use% Mounted on
/dev/sdc1 3.7T 1.5T 2.2T 41% /media/sdc1
/dev/sdb1 1.9T 1.5T 370G 81% /media/sdb1


knoppix@Microknoppix:~$ lsblk -fip
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
/dev/sdb
`-/dev/sdb1 xfs ***-6d33-**-*-3cf53***4997 369.8G 80% /media/sdb
/dev/sdc
`-/dev/sdc1 xfs ***-f139-**-*-b9ab0***b76c 2.2T 40% /media/sdc


xfsdump をインストールする場合
http://nnspaces.sblo.jp/article/187305442.html
@2020/03/28 23:06 | Comment(0) | PC環境構築奮闘記

parted -l on my PC

knoppix@Microknoppix:~$ sudo parted -l
Model: ATA WDC WD6003FZBX-0 (scsi)
Disk /dev/sda: 6001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 17.4kB 16.8MB 16.8MB Microsoft reserved partition msftres
2 16.8MB 1702GB 1702GB ntfs Basic data partition msftdata
3 1702GB 2017GB 315GB ntfs Basic data partition msftdata
4 2017GB 3589GB 1573GB ntfs Basic data partition msftdata
5 5896GB 6001GB 105GB ntfs Basic data partition msftdata


Model: ATA TOSHIBA MD04ACA2 (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 17.4kB 2000GB 2000GB xfs primary msftdata


Model: Netac OnlyDisk (scsi)
Disk /dev/sde: 1995MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 16.4kB 1995MB 1995MB primary fat32 boot, lba




Model: ASMT 2115 (scsi)
Disk /dev/sdc: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 17.4kB 4001GB 4001GB xfs primary msftdata


Model: Kingmax USB2.0 FlashDisk (scsi)
Disk /dev/sdd: 7986MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 7986MB 7985MB primary fat32 boot, lba


Warning: Unable to open /dev/cloop2 read-write (Read-only file system).
/dev/cloop2 has been opened read-only.
Error: /dev/cloop2: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/cloop2: 152MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Model: WDS500G3X0C-00SJG0 (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 524MB 523MB ntfs Basic data partition hidden, diag
2 524MB 628MB 104MB fat32 EFI system partition boot, esp
3 628MB 645MB 16.8MB Microsoft reserved partition msftres
4 645MB 500GB 499GB ntfs Basic data partition msftdata


Warning: Unable to open /dev/cloop0 read-write (Read-only file system).
/dev/cloop0 has been opened read-only.
Error: /dev/cloop0: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/cloop0: 9686MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Warning: Unable to open /dev/cloop1 read-write (Read-only file system).
/dev/cloop1 has been opened read-only.
Error: /dev/cloop1: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/cloop1: 2317MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Model: Samsung SSD 970 EVO Plus 1TB (nvme)
Disk /dev/nvme1n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 17.4kB 16.8MB 16.8MB Microsoft reserved partition msftres
2 16.8MB 900GB 900GB ntfs Basic data partition msftdata


Model: Unknown (unknown)
Disk /dev/zram0: 4295MB
Sector size (logical/physical): 4096B/4096B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 4295MB 4295MB linux-swap(v1)

Model: Patriot Memory (scsi)
Disk /dev/sde: 15.5GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 4129kB 15.5GB 15.5GB primary ntfs

@2020/03/28 22:13 | Comment(0) | PC環境構築奮闘記

Regza のHDDコピーに失敗した理由(4TB 容量を認識できていない)は HDDのクレードルが古いタイプだったからのようだ

4TBのHDDをRegzaにつないだのに、1.8TBしか認識されず、PCにつなぎなおししてから 領域を拡張して、、なんてやっていたので PCでのデータコピーは成功していても、Regza 側では認識せずに困っていた。

PC側の新しめのクレードルにつないだところ問題なく認識した。

こちらがその古いクレードルを、Regzaから取り外ししてPCに持ってきてつないだ時のHDD認識の画面。
確かに1.8TBまでしか認識していない、納得。
2020-03-28_095550.png

新しめのクレードル。全容量認識。
2020-03-28_100147.png

問題の原因はRegza側に用意していたHDDクレードル(HDDを裸のまま接続可能な例のお立ち台)が古くて、認識がおかしかったのだ。
つまりあれだ、Regza用に新しいクレードルを用意しないと。。。
引き続き検証します。

⇒ 新しい裸族のお立ち台(HDDクレードル)で、REGZA側4TB無事認識、その後のコピーも過去に比べて最速コピー完了。
Regza HDD Copy by xfsdump and xfsrestore: NN Space BLOG-NN空間ブログ
@2020/03/28 10:09 | Comment(0) | PC環境構築奮闘記

・おすすめ楽天ショップ1:trendyimpact楽天市場店
・おすすめサプリショップ:iHerb.com
・おすすめ楽天ショップ2:上海問屋
Powered by さくらのブログ