All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Kimsufi:issue with boot kernel from network mode
Hi everyone,
I setup the boot kernel from the network mode on a kimsufi ks-le.
On the control panel, the server is marked as OK after the reboot done from the control panel but if I ping the server, there is no answer and I cannot access the server.
In the netboot/network section,I selected “ovh kernel” ( this is anyway the only one available) and in the root section I added /dev/md2
.
Below is the process I followed:
https://docs.ovh.com/gb/en/dedicated/kernel-netboot/#boot-your-server-from-network-mode
If I switch back to boot on the hard drive, after a few minutes, I can ping the server and establish a connection.
Does anyone know why the server hang after I modified the kernel netboot?
Some logs below.
Thank you!
root@ns3xxxxxxx:~# cat /etc/fstab
UUID=ec6cd7b0-612f-4ff5-86a9-54a92acb0589 / ext4 defaults 0 1
UUID=40ba21cf-b918-45b0-9454-f7606a074561 /var/lib/vz ext4 defaults 0 0
UUID=23262e8d-5004-4a42-8e31-36f589a4f647 swap swap defaults 0 0
UUID=c5cc6e47-b7c4-4887-9c46-50640c76da56 swap swap defaults 0 0
root@ns3xxxxxxx:~#
root@ns3xxxxxxx:~#
root@ns3xxxxxxx:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 20G 0 part
│ └─md2 9:2 0 20G 0 raid1 /
├─sda3 8:3 0 1G 0 part [SWAP]
├─sda4 8:4 0 1.8T 0 part
│ └─md4 9:4 0 1.8T 0 raid1
│ └─vg-data 253:0 0 1.8T 0 lvm /var/lib/vz
└─sda5 8:5 0 2M 0 part
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 1M 0 part
├─sdb2 8:18 0 20G 0 part
│ └─md2 9:2 0 20G 0 raid1 /
├─sdb3 8:19 0 1G 0 part [SWAP]
└─sdb4 8:20 0 1.8T 0 part
└─md4 9:4 0 1.8T 0 raid1
└─vg-data 253:0 0 1.8T 0 lvm /var/lib/vz
root@ns3xxxxxxx:~#
root@ns3xxxxxxx:~#
root@ns3xxxxxxx:~#
root@ns3xxxxxxx:~# fdisk -l
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: HGST HUS724020AL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5906030B-1856-5B24-247A-D264323C482B
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 41947135 41943040 20G Linux RAID
/dev/sda3 41947136 44044287 2097152 1G Linux filesystem
/dev/sda4 44044288 3907024895 3862980608 1.8T Linux RAID
/dev/sda5 3907025072 3907029134 4063 2M Linux filesystem
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: HGST HUS724020AL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CE71B4D4-7FBC-282A-B54E-5CBDCDB7B9C1
Device Start End Sectors Size Type
/dev/sdb1 2048 4095 2048 1M BIOS boot
/dev/sdb2 4096 41947135 41943040 20G Linux RAID
/dev/sdb3 41947136 44044287 2097152 1G Linux filesystem
/dev/sdb4 44044288 3907024895 3862980608 1.8T Linux RAID
Disk /dev/md2: 20 GiB, 21458059264 bytes, 41910272 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md4: 1.8 TiB, 1977711853568 bytes, 3862718464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/vg-data: 1.8 TiB, 1977710804992 bytes, 3862716416 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes