[Gautam Koji]
Taking the opportunity to shutdown c1ioo for adding a DAC card, we shutdown chiara and worked on moving of the main disk to the bigger home.
We shutdown most of the martian machines including the control machines, megatron, optimus, and nodus.
- Before shutting down chiara, we ran rsync to make the 4TB disk (used to be teh backup) and /cvs/cds synced.
sudo rsync -a --progress /home/cds/ /media/40mBackup
- Modified /etc/fstab
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=972db769-4020-4b74-b943-9b868c26043a / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=a3f5d977-72d7-47c9-a059-38633d16413e none swap sw 0 0
UUID="90a5c98a-22fb-4685-9c17-77ed07a5e000" /media/40mBackup ext4 defaults,relatime,commit=60 0 0
#fb:/frames /frames nfs ro,bg
UUID=92dc7073-bf4d-4c58-8052-63129ff5755b /home/cds ext4 defaults,relatime,commit=60 0 0
- Shutdown chiara. Put the 4TB disk in the chassis. We also installed a new disk (but later it turned out that it only has 2TB...)
- Restart the mahcine. This already made the 4TB disk mounted as /cvs/cds .
- Restart bind9 with DHCP for the diskless clients (cf. https://wiki-40m.ligo.caltech.edu/CDS/How_to_join_martian)
sudo service bind9 restart
sudo service isc-dhcp-server restart
- Looks like /etc/resolv.conf is automatically overwritten by a tool or something everytime we restart the machine!? I still don't know how to avoid this. (cf. https://www.ctrl.blog/entry/resolvconf-tutorial). But at least for today we manually wrote /etc/resolv.conf
controls@chiara|backup> cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.113.104
nameserver 131.215.125.1
nameserver 8.8.8.8
search martian
|