Oh a spelling error, I beg for your forgiveness ....

root@alexhost:~/vm-seed/vmXX# yamllint network-config network-config 1:1 warning missing document start "---" (document-start) 11:8 error wrong indentation: expecte

(Quote)

(Quote)

Are you Turkish? I also tried using 192.168.1.1 to a VPS in Frankfurt using that IP. It said there was almost no latency, but the Istanbul VPS didn't give any results and gave me an error, I think.

(Quote)

(Quote)

(Quote)

All should be resolved now. There was a BGP injection error across many of our hypervisors. We are putting in place some safety measures so that it does not occur again...

(Quote)

(Quote)

(Quote)

the fs on top however now seems borked and gives you that error on mount. did you run e2fsck on the assembled /dev/md0 yet? this would be the next step to try and get the filesystem repaired...

#mount -o ro /dev/md0 /mnt/testmount: /mnt/test: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error.

(Quote)

Error:

(Quote)

mount: /home: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error[ 5364.979604] print_req_error: I/O error, dev sda, sector 215099976[ 5364.979821

Running raid0 is always what it is. But if it needs to run like this, maybe filesystems with more resilence for logical errors ( like checksum feature ) should be used.

The server was working fine for years after this configuration, until we restarted it recently, and to my surprise it was unable to mount the raid array. The sda disk seems to have some bad sectors bu