| 1 |
On Saturday, July 6, 2019 12:44:46 A.M. AEST Robin Atwood wrote: |
| 2 |
> On Fri, 05 Jul 2019 15:34:18 +0100 |
| 3 |
> |
| 4 |
> Mick <michaelkintzios@×××××.com> wrote: |
| 5 |
> > On Friday, 5 July 2019 15:30:06 BST Robin Atwood wrote: |
| 6 |
> > > Thanks Vladimir, that sounds promising. Can you recommend any GPT |
| 7 |
> > > programs (this is new to me)? However the dd utility failed when I |
| 8 |
> > > tried to copy my old HD to the new one. |
| 9 |
> > > |
| 10 |
> > > # dd if=/dev/sda of=/dev/sdb bs=64K conv=noerror,sync |
| 11 |
> > > dd: error writing '/dev/sdb': No space left on device |
| 12 |
> > > 160+0 records in |
| 13 |
> > > 159+0 records out |
| 14 |
> > > 10481664 bytes (10 MB, 10 MiB) copied, 0.132944 s, 78.8 MB/s |
| 15 |
> > > |
| 16 |
> > > Cheers |
| 17 |
> > > Robin |
| 18 |
> > |
| 19 |
> > You can use gptfdisk, parted/gparted, etc. |
| 20 |
> > |
| 21 |
> > To check the size as well as additional information you can use |
| 22 |
> > smartmontools and run: |
| 23 |
> > |
| 24 |
> > smartctl -i /dev/sda |
| 25 |
> > |
| 26 |
> > It may also be worth checking if later firmware is available to |
| 27 |
> > address any issues with it, like reporting the wrong size with some |
| 28 |
> > tools. |
| 29 |
> > |
| 30 |
> > However, the dd command failure sounds suspicious - as I understand |
| 31 |
> > it dd should not fail unless the disk has run out of space. |
| 32 |
> |
| 33 |
> OK panic over! I had shelled into the wrong system! The mystery is what |
| 34 |
> I was trying to copy to, the machine only has one HD. |
| 35 |
|
| 36 |
|
| 37 |
It would probably just have created a normal file called /dev/sdb which would |
| 38 |
have grown till it filled the empty space on the partition. |
| 39 |
|
| 40 |
|
| 41 |
-- |
| 42 |
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/ |
| 43 |
Asking for technical help in newsgroups? Read this first: |
| 44 |
http://catb.org/~esr/faqs/smart-questions.html#intro |
Archives