Hello,

i have two comments having done something similar recently:

1. about the disk slots: for rotating disks, it is important to locate
   them in slots, but ssds are entirely enclosed electronic circuits so
   the can just be let loose (or attached say with double stick tape)
   anywhere in the box
2. If you really want to keep your environment as it is (with boot and
   every thing), first dd your entire disk to a new bigger one then
   boot on it start moving out what you wish.

Personnaly, I lived several years with 2 2TB disks in mirror with just a rpool on these and I added a 120G ssd as cache to the rpool. When I needed more space, I used zpool split to change the mirrored rpool in a single disk rpool and other disk named backuppool. Then I removed all disks and installed a fresh system (OI-Hipster2020.04 on a 500G ssd. Then I added two 4TB disks and created a mirrored dpool on it. Then I connected and imported backuppool, I used rsync to transfer data to zfs file systems on dpool. zpool status complained that backuppool used an old version of zfs. I did not upgrade it, in order to keep the possibility to use it in the the old configuration (the whole transfer operation takes a lot of time so I regularly had to reuse the old configuration and had to be able to transfer data to the new one using rsinc to and from the backup disk). Finally I added a second 500G ssd to have a mirrored rpool and the 120 GB as cache to the mirrored dpool. Note that only the two 4TB rotating disks are in disks slots. The ssd are just sticked here and there in the box. The do not heat much, so they atre happy anuwhere.
I hope these coments can help you.
Good luck
Marc

On 24/05/2020 19:50, Gary Mills wrote:
On Sun, May 24, 2020 at 12:09:31PM -0400, Harry Putnam wrote:
I use simple mirrored pairs for yrs now.
This is not a commercial operation or even a very serious homeboy HOST.
I use mirrored pairs too.  Disks do fail.  The system just keeps on
going in this configuration.

I had a disk failure some time ago that is one of the mirrored boot
disks. I have yet to fix that.

They were a pair of 700 GB disks I had on hand so used them for the
boot root disk pair some yrs ago now.  They are now a bit old and may
be hard to replace with matching new disk

    . . . (Hope this doesn't all just sound like gobbledy goop) ...

Because of the hefty 700gb size for root OS and boot bits, overtime
I've allowed data filesystems to creep onto them.
You may not be able to find a disk that small anymore.  1TB is about
the smallest available now.  I use a pair of these as data disks, and
a pair of SSDs for the OS.  The SSDs are faster than rotating disks,
of course.  I get the smallest SSDs I can find.  That is about
120GB these days.

Of course I need to replace the bad disk.

I want to reduce the size of the boot disks anyway and totally avoid
having any data but OS on them. So, first off I will get the extra FS
off of working  boot disk.  (I currently have plenty of room)

So wondering a bit about how to proceed from there.

I think I'd like to replace the bad disk with new 250 GB HDD.
You can certainly start by replacing the bad disk with a 1TB disk.
Then, you can replace the other one.  zfs will do all of that easily.
That may be all you need to do.

Assuming the data on the remaining boot 700gb disk is smaller than 250
gb, (In the actual case it will be a good bit smaller and only contain
OS) will the silvering of new smaller disk work?

Will the 700 GB and 250 GB be able to pair that way?
I'd recommend larger data disks and smaller boot disks, both mirrored.
This may not be possible, depending on how many disk slots your case
has.  There are brackets that allow two SSDs to fit in one slot.
Still, you'd need three slots.

Will it be possible to transfer the boot bits to the new 250 GB?
I've never done that.  There is a way to transfer the boot device to
a new device.  I recall that was safe and fairly easy, but I haven't
done that for a while.  Most of the work was done by:

     beadm create ... -p ...



_______________________________________________
openindiana-discuss mailing list
[email protected]
https://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to