اختلال قطی برق در دیتاسنتر هتزنر

نمایش نسخه قابل چاپ

سلام
ظاهرا ساعتی پیش مشکل برقی در دیتاسنتر Falkenstein انها رخ داده است

Type: Fault report

Categories: Basic infrastructure

Start: May 24, 2018 11:30:00 AM CEST

End: Unknown

Description: Due to a current disruption of the power supply at our location Falkenstein, there are currently accessibility problems of some customer servers. Our technicians are currently analyzing the source of the problem and we will keep you up to date.

بروز رسانی جدید

https://www.hetzner-status.de/images/addition_flag.png Update: May 24, 2018 12:10:00 PM CEST

Update: According to current knowledge there was a short-term power failure in the DC7, DC10 + DC12. Due to the concomitant failure of core network technology, there was a short-term failure of the entire network in Datacenterpark Falkenstein due to the power failure

https://www.hetzner-status.de/en.html

May 24th, 2018, 19:04
Mr-Pro

پاسخ : اختلال قطی برق در دیتاسنتر هتزنر

يكي از سرورهامون داون شده چند ساعته . كسي خبر جديد نداره؟
May 24th, 2018, 19:57
RoobinaServer

پاسخ : اختلال قطی برق در دیتاسنتر هتزنر

نقل قول:

نوشته اصلی توسط Mr-Pro

يكي از سرورهامون داون شده چند ساعته . كسي خبر جديد نداره؟

با سلام

هم اکنون اکثر dc ها در دسترس هستند احتمالا سرورتون روشن نشده پنلتون را چک کنید.
May 24th, 2018, 20:40
Amlaaki

پاسخ : اختلال قطی برق در دیتاسنتر هتزنر

یک سرور در dc16 هنوز قطعه + پنل هم باز نمیشد ظهری.

Type:	Fault report
Categories:	Basic infrastructure
Start:	May 24, 2018 11:30:00 AM CEST
End:	Unknown
Description:	Due to a current disruption of the power supply at our location Falkenstein, there are currently accessibility problems of some customer servers. Our technicians are currently analyzing the source of the problem and we will keep you up to date.

https://www.hetzner-status.de/images/addition_flag.png Update:	May 24, 2018 12:10:00 PM CEST
	Update: According to current knowledge there was a short-term power failure in the DC7, DC10 + DC12. Due to the concomitant failure of core network technology, there was a short-term failure of the entire network in Datacenterpark Falkenstein due to the power failure

پاسخ : اختلال قطی برق در دیتاسنتر هتزنر

نقل قول:

نوشته اصلی توسط Amlaaki

یک سرور در dc16 هنوز قطعه + پنل هم باز نمیشد ظهری.

درود
آخرین آپدیت دیتا سنتر از وضعیت :

May 24, 2018 4:36:00 PM CEST

In the meantime, all servers that did not restart automatically after the voltage failure were switched on or checked for defective power supplies. The next step is to work on the tickets in the data centers concerned - servers that are currently not available must all be checked individually, because the error situations can vary greatly.

The following tickets are currently in the queues:

DC 07 1013
DC 10 1408
DC 12 465

To avoid further delays, we ask you to create only one ticket per affected server.

Thank you very much.

May 24th, 2018, 20:55
ehsanyeganeh

پاسخ : اختلال قطی برق در دیتاسنتر هتزنر

عزیزم قطی نه قطعی!
May 24th, 2018, 22:30
SaeedFazlollahzadeh

پاسخ : اختلال قطی برق در دیتاسنتر هتزنر

تا ساعت 7 که بنده اطلاع دارم کامل رفع نشده بود.

ولی عجیب هست! بیمارستان در ایران برق اضطراری دارد. هتزنر نداشت!
نکنه آلمان رو تحریم کردیم که برق ندارن و خبر نداریم؟
May 24th, 2018, 22:58
DjMohsen

پاسخ : اختلال قطی برق در دیتاسنتر هتزنر

دهنم سرویس شده به قرآن
حاضرم پول بدم اگر کسی واقعا بتونه کمک کنه
وی ام ویر ۵.۵ می خواد لود کنه خط زر تا وسط میاد بعدش صفحه سیاه میشه
پینگ هست ولی سیستم عامل وی ام ویر اجرا نمیشه.
اینم مشخصات هاد از روی رسکیو هست که البته هر دو دیسک استفاده شده اند برای وی ام ها

کد:

fdisk -l Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/loop0: 2.5 GiB, 2634022912 bytes, 5144576 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/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 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 Disklabel type: gpt Disk identifier: AC03FA71-5C21-4C1C-A403-49BFB1EBEEF6 Device Start End Sectors Size Type /dev/sdb1 2048 5860532223 5860530176 2.7T unknown Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 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 Disklabel type: gpt Disk identifier: 5D55F2DF-C58E-4B87-B7DD-1198D2D982E3 Device Start End Sectors Size Type /dev/sda1 64 8191 8128 4M EFI System /dev/sda2 7086080 15472639 8386560 4G Microsoft basic data /dev/sda3 15472640 5860533134 5845060495 2.7T unknown /dev/sda5 8224 520191 511968 250M Microsoft basic data /dev/sda6 520224 1032191 511968 250M Microsoft basic data /dev/sda7 1032224 1257471 225248 110M unknown /dev/sda8 1257504 1843199 585696 286M Microsoft basic data /dev/sda9 1843200 7086079 5242880 2.5G unknown Partition table entries are not in disk order.

	May 24, 2018 4:36:00 PM CEST
	In the meantime, all servers that did not restart automatically after the voltage failure were switched on or checked for defective power supplies. The next step is to work on the tickets in the data centers concerned - servers that are currently not available must all be checked individually, because the error situations can vary greatly. The following tickets are currently in the queues: DC 07 1013 DC 10 1408 DC 12 465 To avoid further delays, we ask you to create only one ticket per affected server. Thank you very much.