mamboman wrote:
One last question: when I get it right with the new GPT layout I could even install a disk >> 2.2 TB. What would I have to save and copy from the current disk to a fresh new empty disk then to get a clean new up and running NAS?
I would assume just copy the bootsector from the current disk by doing this:
Old disk installed:
dd if=/dev/sda of=/path-to-a-backup-disk/mbr.img bs=512 count=1
And on the new disk then
dd if=/path-to-a-backup-disk/mbr.img of=/dev/sda bs=512 count=1
or
dd if=/path-to-a-backup-disk/mbr.img of=/dev/sda bs=446 count=1 (if the new disk has another partition table that needs to be preserved)
and the rest like desribed in your manual (like seeing up partitions, writing the images, etc.). It this correct?
I would like to make a backup of my system in case of a disk problem. /dev/sda8 of course will be backed up differently :)
I don't think that the procedure you describe is the right way to do it.
If the new disk is bigger it will have more sectors. And just copying the mbr will not work. In fact gpt partioned disks doesn't use the mbr it puts there something to protect older system form accessing the disk in the wrong way.
For disk bigger the 2.2TB only GPT can be used to make use of all space. If you use ms-dos partions then the max will be that you can use of the disk 2.2 TB
In fact the bootloader only tries to find partition 6 to load the kernel and pass some arguments to it. When it is a GPT formatted disk the loader will not use the MBR as far as I know (but I could be wrong)
I would just create the 8 partitions with gparted as you did with this one and using for sda8 the remaining size of the disk.
And the do the rest just as described in our manual
To preserve the settings you made you could copy the data base file as present in /rw_fs/etc (this is on sda5) on the current diks and write that to new disk sda5 partition instead of the one in the first time install package