infoboy
Cadet
- Joined
- Feb 22, 2023
- Messages
- 4
Hi friends.
Hope everyone's doing well.
I got this surprise today, a very inconvenient one. During a meeting i heard something which disturbed me a lot.
(I hope i will not have nightmares this night about some usb stick running in fire around the server room.)
On another site i'm not responsible for there is our archives infrastructure.
Freenas has been choosen to do the job at this time (2019 i think). That was a perfect choice.
I work on another site mostly on gnu/linux stuff and unfortunately the previous sysadmin quit and didn't leave any decent documentation.
Now the person in charge on the site is a little shy with BSD (as i am) and discovered recently that the entire production server is installed ... on a usb stick.
as you can see :
I feel really uncomfortable with this and wish to plan a migration to some SSD (zfs mirror) asap.
We got other large zfs pool divided into dataset like :
The idea as you can imagine is to leave untouched those datasets.
I got very poor skills with BSD, zfs and more specifically truenas as for example i have no idea how the bootloader works.
Can some of the wizards here drive me to some documentations/directions to plan a safe migration please ?
I can provide other details, logs of course an would be glad to learn and read you.
Thank you very much .
Hope everyone's doing well.
I got this surprise today, a very inconvenient one. During a meeting i heard something which disturbed me a lot.
(I hope i will not have nightmares this night about some usb stick running in fire around the server room.)
On another site i'm not responsible for there is our archives infrastructure.
Freenas has been choosen to do the job at this time (2019 i think). That was a perfect choice.
I work on another site mostly on gnu/linux stuff and unfortunately the previous sysadmin quit and didn't leave any decent documentation.
Now the person in charge on the site is a little shy with BSD (as i am) and discovered recently that the entire production server is installed ... on a usb stick.
as you can see :
Code:
freenas-boot 9.94G 45.3G 64K none freenas-boot/ROOT 9.91G 45.3G 29K none freenas-boot/ROOT/11.2-U2.1 195K 45.3G 756M / freenas-boot/ROOT/11.2-U8 355K 45.3G 759M / freenas-boot/ROOT/11.3-U1 261K 45.3G 1.00G / freenas-boot/ROOT/11.3-U3.2 230K 45.3G 1.01G / freenas-boot/ROOT/11.3-U4.1 250K 45.3G 1.01G / freenas-boot/ROOT/11.3-U5 242K 45.3G 1.02G / freenas-boot/ROOT/12.0-U4.1 172K 45.3G 1.19G / freenas-boot/ROOT/13.0-U3.1 9.90G 45.3G 1.30G / freenas-boot/ROOT/FreeNAS-12.0-U3.1 174K 45.3G 1.17G / freenas-boot/ROOT/Initial-Install 1K 45.3G 760M legacy freenas-boot/ROOT/default 190K 45.3G 760M legacy
Code:
freenas-boot 57G 9.94G 47.1G - - - 17% 1.00x ONLINE -
I feel really uncomfortable with this and wish to plan a migration to some SSD (zfs mirror) asap.
We got other large zfs pool divided into dataset like :
Code:
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT JUNGLE_ZFSpool 217T 145T 72.4T - - 4% 66% 1.00x ONLINE /mnt
The idea as you can imagine is to leave untouched those datasets.
I got very poor skills with BSD, zfs and more specifically truenas as for example i have no idea how the bootloader works.
Can some of the wizards here drive me to some documentations/directions to plan a safe migration please ?
I can provide other details, logs of course an would be glad to learn and read you.
Thank you very much .