I installed Debian 11 on the Data Concentrator/Network Data Server/Frame Writer computer in TAMA. In 2951 we ran across a problem where we couldn't complete the software installation for the Debian 11 install, and for some reason couldn't install a boot loader properly. The problem was that the installation medium was running in BIOS mode as opposed to the more appropriate UEFI mode. Switching to UEFI installer upon startup made the installation go smoothly as for the frontend computer.
The following options were chosen during installation:
Language - English
Region - Japan
Locales - en_US.UTF-8
Keyboard - American English
hostname - DCCentral
domain name - mtk.nao.ac.jp (default)
Network interface - eno1 Intel Corporation I210 Gigabit Network Connection
root password - normal KAGRA controls password
ops user 1000 (same password as usual)
controls user 1001 (same password as usual)
package manager - deb.debian.org
HTTP proxy - blank
The following drive partitioning scheme was chosen:
Disk 1 - 1 TB Western Digital ATA - for operating system and user files
512 MB - EFI System Partition (ESP) - in the failing step last time, using the BIOS mode installer would not let us install this partition. Now it's fine.
128 GB swap space
Remaining (~870 GB) - ext4 / - perhaps there's no real need to separate into /home, /var, /tmp here, so the system can just figure that out by itself
Disk 2 - 24 TB Avago MegaRAID virtual drive (4x 7.6 TB disks with RAID5 redundancy) - for mass storage of channel data
24.0 TB - ext4 /data0 - used for frame writer. In KAGRA, there are two frame writer PCs k1fw0 /data0 and k1fw1 /data1 with about 25 TB storage each, for extra data redundancy. But we only have one server PC, so I just assume we are using one frame writer.
Afterwards, I added ops and controls to the sudoers file and installed cdssoft version 1.0.11 (was 1.0.9 when installing frontend) from the aligo caltech Debian Bullseye repository.
*I will comment later in a bit more detail about what some of these technical terms mean