Archive Data Server - Revision history

Rtang at 20:24, 25 June 2022

2022-06-25T20:24:19Z

← Older revision		Revision as of 16:24, 25 June 2022
Line 1:		Line 1:
	The archive data server is ~~build~~ upon an relic Dell R710 rack server, which was bought around 2010 and ~~haven~~'t been ~~using~~ for long time. It was a ~~format~~ [[ANASEN]] DAQ computer. The server has 8 TB of storage.		The archive data server is built upon a relic Dell R710 rack server, which was bought around 2010 and hasn't been used for long time. It was a former [[ANASEN]] DAQ computer. The server has 8 TB of storage.

	~~Users~~ home directories and data and code of finished experiments will be stored in the server.		User's home directories and data and code of finished experiments will be stored on the server.

	The directories are		The directories are

Rtang: /* Solution on installing Modern OS */

2022-06-25T19:58:34Z

Solution on installing Modern OS

← Older revision		Revision as of 15:58, 25 June 2022
Line 18:		Line 18:
	Modern OS, like Ubuntu 20, use UEFI boot that is different from BIOS boot.		Modern OS, like Ubuntu 20, use UEFI boot that is different from BIOS boot.

	This is ~~a very~~ old machine ~~that~~ booting from BIOS that read only the 1st 512kB for the master boot record and the 2nd 512kB for the boottrap.img. It provides UEFI boot manual (so that Ubuntu 20 USB boot drive can run, with BIOD update, BIOS mode can also boot Ubuntu 20 USB), but, the RAID controller does not support the UEFI (in fact, it clearly shows that the Virtual Disk is supported by BIOS), so when boosting the RAID array from UEFI, it switches back to BIOS mode. That's why an installed Ubuntu 20.04 cannot boot and return the grub command line. In fact, in the grub command line, it only sees 2 partitions, the (proc) and (hd0), which are both 512kB. This indicates that it is using BIOS mode to see the first two 512kB for the boot loader.		This is an old machine booting from BIOS that read only the 1st 512kB for the master boot record and the 2nd 512kB for the boottrap.img. It provides UEFI boot manual (so that Ubuntu 20 USB boot drive can run, with BIOD update, BIOS mode can also boot Ubuntu 20 USB), but, the RAID controller does not support the UEFI (in fact, it clearly shows that the Virtual Disk is supported by BIOS), so when boosting the RAID array from UEFI, it switches back to BIOS mode. That's why an installed Ubuntu 20.04 cannot boot and return the grub command line. In fact, in the grub command line, it only sees 2 partitions, the (proc) and (hd0), which are both 512kB. This indicates that it is using BIOS mode to see the first two 512kB for the boot loader.

	There is no way to bypass the RAID controller, as it is the only interface to connect hard disks to the motherboard.		There is no way to bypass the RAID controller, as it is the only interface to connect hard disks to the motherboard.

Rtang: /* Solution on installing UEFI-boot OS */

2022-06-25T19:58:15Z

Solution on installing UEFI-boot OS

← Older revision		Revision as of 15:58, 25 June 2022
Line 14:		Line 14:


	= Solution on installing UEFI-boot ~~OS =~~		= Solution on installing Modern OS =

			Modern OS, like Ubuntu 20, use UEFI boot that is different from BIOS boot.

	This is a very old machine that booting from BIOS that read only the 1st 512kB for the master boot record and the 2nd 512kB for the boottrap.img. It provides UEFI boot manual (so that Ubuntu 20 USB boot drive can run, with BIOD update, BIOS mode can also boot Ubuntu 20 USB), but, the RAID controller does not support the UEFI (in fact, it clearly shows that the Virtual Disk is supported by BIOS), so when boosting the RAID array from UEFI, it switches back to BIOS mode. That's why an installed Ubuntu 20.04 cannot boot and return the grub command line. In fact, in the grub command line, it only sees 2 partitions, the (proc) and (hd0), which are both 512kB. This indicates that it is using BIOS mode to see the first two 512kB for the boot loader.		This is a very old machine that booting from BIOS that read only the 1st 512kB for the master boot record and the 2nd 512kB for the boottrap.img. It provides UEFI boot manual (so that Ubuntu 20 USB boot drive can run, with BIOD update, BIOS mode can also boot Ubuntu 20 USB), but, the RAID controller does not support the UEFI (in fact, it clearly shows that the Virtual Disk is supported by BIOS), so when boosting the RAID array from UEFI, it switches back to BIOS mode. That's why an installed Ubuntu 20.04 cannot boot and return the grub command line. In fact, in the grub command line, it only sees 2 partitions, the (proc) and (hd0), which are both 512kB. This indicates that it is using BIOS mode to see the first two 512kB for the boot loader.

Rtang: /* solution to increase the supported disk size */

2022-06-25T19:53:52Z

solution to increase the supported disk size

← Older revision		Revision as of 15:53, 25 June 2022
Line 72:		Line 72:
	indicate that it is using 512 bytes sector size (physical).		indicate that it is using 512 bytes sector size (physical).

	For the old 2 TB disk in [[fsunuc]],		For the old 2 TB disk in [[Web Server\|fsunuc]],
	Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors		Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
	Disk model: ST2000VN004-2E41		Disk model: ST2000VN004-2E41

Rtang: /* solution to increase the supported disk size */

2022-06-25T19:53:22Z

solution to increase the supported disk size

← Older revision		Revision as of 15:53, 25 June 2022
Line 60:		Line 60:

	Some people suggest that it is related to the sector size. The hard disk in the past used 512 bytes for a sector size and the partition table support 2^32 bit, so 2 TB is the max disk size. From the transition to 512 bytes to 4 KB sector size, there is a 512 emulation (512e). But it supports a 4 ~ 6 TB disk, not more.		Some people suggest that it is related to the sector size. The hard disk in the past used 512 bytes for a sector size and the partition table support 2^32 bit, so 2 TB is the max disk size. From the transition to 512 bytes to 4 KB sector size, there is a 512 emulation (512e). But it supports a 4 ~ 6 TB disk, not more.

			using fdisk -l

			~>sudo fdisk -l /dev/sda
			Disk /dev/sda: 5.46 TiB, 5999532441600 bytes, 11717836800 sectors
			Disk model: PERC 6/i
			Units: sectors of 1 * 512 = 512 bytes
			Sector size (logical/physical): 512 bytes / 512 bytes
			I/O size (minimum/optimal): 512 bytes / 512 bytes

			indicate that it is using 512 bytes sector size (physical).

			For the old 2 TB disk in [[fsunuc]],
			Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
			Disk model: ST2000VN004-2E41
			Units: sectors of 1 * 512 = 512 bytes
			Sector size (logical/physical): 512 bytes / 4096 bytes
			I/O size (minimum/optimal): 4096 bytes / 4096 bytes

	= Update BIOS =		= Update BIOS =

Rtang: /* solution to increase the supported disk size */

2022-06-25T19:40:10Z

solution to increase the supported disk size

← Older revision		Revision as of 15:40, 25 June 2022
Line 56:		Line 56:
	# a firmware upgrade to 4 TB (rumor? which firmware version at the present?)		# a firmware upgrade to 4 TB (rumor? which firmware version at the present?)
	#: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=f96nr&oscode=naa&productcode=poweredge-r710		#: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=f96nr&oscode=naa&productcode=poweredge-r710
	# replace the PERC 6/i RAID controller with H700, which supports 6 TB. The cable also needs to change		# replace the PERC 6/i RAID controller with H700 (~ $65 from Amazon), which supports 6 TB. The cable also needs to change
	#: see this post https://www.reddit.com/r/sysadmin/comments/2pjuy3/perc_6i_controller_with_6tb_drives/		#: see this post https://www.reddit.com/r/sysadmin/comments/2pjuy3/perc_6i_controller_with_6tb_drives/

Rtang: /* solution to increase the supported disk size */

2022-06-25T19:38:28Z

solution to increase the supported disk size

← Older revision		Revision as of 15:38, 25 June 2022
Line 56:		Line 56:
	# a firmware upgrade to 4 TB (rumor? which firmware version at the present?)		# a firmware upgrade to 4 TB (rumor? which firmware version at the present?)
	#: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=f96nr&oscode=naa&productcode=poweredge-r710		#: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=f96nr&oscode=naa&productcode=poweredge-r710
	# replace the PERC 6/i RAID controller with H700, which supports 6 TB. ~~Cable~~ also needs to change		# replace the PERC 6/i RAID controller with H700, which supports 6 TB. The cable also needs to change
	#: see this post https://www.reddit.com/r/sysadmin/comments/2pjuy3/perc_6i_controller_with_6tb_drives/		#: see this post https://www.reddit.com/r/sysadmin/comments/2pjuy3/perc_6i_controller_with_6tb_drives/

			Some people suggest that it is related to the sector size. The hard disk in the past used 512 bytes for a sector size and the partition table support 2^32 bit, so 2 TB is the max disk size. From the transition to 512 bytes to 4 KB sector size, there is a 512 emulation (512e). But it supports a 4 ~ 6 TB disk, not more.

	= Update BIOS =		= Update BIOS =

Rtang: /* Solution on installing UEFI-boot OS */

2022-06-25T19:29:00Z

Solution on installing UEFI-boot OS

← Older revision		Revision as of 15:29, 25 June 2022
Line 16:		Line 16:
	= Solution on installing UEFI-boot OS =		= Solution on installing UEFI-boot OS =

	This is a very old ~~machines~~ that ~~boosting~~ from BIOS that read only the 1st 512kB for the master boot record and the 2nd 512kB for the boottrap.img. It provides UEFI boot manual (so that Ubuntu 20 USB boot drive can run), but, the RAID controller does not support the UEFI (in fact, it clearly shows that the Virtual Disk is supported by BIOS), so when boosting the RAID array from UEFI, it switches back to BIOS mode. That's why an installed Ubuntu 20.04 cannot boot and return the grub command line. In fact, in the grub command line, it only sees 2 partitions, the (proc) and (hd0), which are both 512kB. This indicates that it is using BIOS mode to see the first two 512kB for the boot loader.		This is a very old machine that booting from BIOS that read only the 1st 512kB for the master boot record and the 2nd 512kB for the boottrap.img. It provides UEFI boot manual (so that Ubuntu 20 USB boot drive can run, with BIOD update, BIOS mode can also boot Ubuntu 20 USB), but, the RAID controller does not support the UEFI (in fact, it clearly shows that the Virtual Disk is supported by BIOS), so when boosting the RAID array from UEFI, it switches back to BIOS mode. That's why an installed Ubuntu 20.04 cannot boot and return the grub command line. In fact, in the grub command line, it only sees 2 partitions, the (proc) and (hd0), which are both 512kB. This indicates that it is using BIOS mode to see the first two 512kB for the boot loader.

			There is no way to bypass the RAID controller, as it is the only interface to connect hard disks to the motherboard.

	The problem is the grub cannot read a partition larger than 100 GB. In order to cope with that, we need to set the partition manually		The problem is the grub cannot read a partition larger than 100 GB. In order to cope with that, we need to set the partition manually
Line 28:		Line 30:

	=== an idea ===		=== an idea ===
	Install a PCIe card with NVMe M.2 SSD, and boot to the SSD?		#Install a PCIe card with NVMe M.2 SSD, and boot to the SSD?
			#replace the CD-ROM with an SSD. The CD-ROM is using SATA cable to connect, power?

	= Network =		= Network =

Rtang: /* an idea */

2022-06-25T19:24:21Z

an idea

← Older revision		Revision as of 15:24, 25 June 2022
Line 28:		Line 28:

	=== an idea ===		=== an idea ===
	Install a ~~PCI~~ card with ~~NVME~~ M.2 SSD, and boot to the SSD?		Install a PCIe card with NVMe M.2 SSD, and boot to the SSD?

	= Network =		= Network =

Rtang: /* Solution on installing UEFI-boot OS */

2022-06-25T19:23:50Z

Solution on installing UEFI-boot OS

← Older revision		Revision as of 15:23, 25 June 2022
Line 16:		Line 16:
	= Solution on installing UEFI-boot OS =		= Solution on installing UEFI-boot OS =

	This is a very old machines that boosting from BIOS that read only the 1st 512kB for the master boot record and the 2nd 512kB for the boottrap.img. It provides UEFI boot manual (so that Ubuntu 20 USB boot drive can run), but, the RAID controller does not support the UEFI (in fact, it clearly shows that the Virtual Disk is supported by BIOS), so when boosting the RAID array from UEFI, it switches back to BIOS mode. That's why an installed Ubuntu 20.04 cannot boot and return the grub command line. In fact, in the grub command line, it only ~~see~~ 2 partitions, the (proc) and (hd0), which are both 512kB. This indicates that it is using BIOS mode to see the first 2 512kB for boot loader.		This is a very old machines that boosting from BIOS that read only the 1st 512kB for the master boot record and the 2nd 512kB for the boottrap.img. It provides UEFI boot manual (so that Ubuntu 20 USB boot drive can run), but, the RAID controller does not support the UEFI (in fact, it clearly shows that the Virtual Disk is supported by BIOS), so when boosting the RAID array from UEFI, it switches back to BIOS mode. That's why an installed Ubuntu 20.04 cannot boot and return the grub command line. In fact, in the grub command line, it only sees 2 partitions, the (proc) and (hd0), which are both 512kB. This indicates that it is using BIOS mode to see the first two 512kB for the boot loader.

	The problem is the grub cannot read partition larger than 100 GB. In order to cope with that, we need to set the partition manually		The problem is the grub cannot read a partition larger than 100 GB. In order to cope with that, we need to set the partition manually
	* 1 MB for BIOS_boot ~~for~~ master boot record, unformatted		* 1 MB for BIOS_boot (master boot record), unformatted
	* 10 GB for /boot , ~~et4~~		* 10 GB for /boot , ext4
	* 8 GB swap		* 8 GB swap
	* 500 MB for EFI System, FAT		* 500 MB for EFI System, FAT
	* Rest /		* Rest /, ext4

	Then Ubuntu 22.04 is able to installed and boot		Then Ubuntu 22.04 is able to installed and boot

			=== an idea ===
			Install a PCI card with NVME M.2 SSD, and boot to the SSD?

	= Network =		= Network =