И продолжение:
SMART Error Log Version: 1 ATA Error Count: 177 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 177 occurred at disk power-on lifetime: 15654 hours (652 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 80 ff ff ff 4f 00 14d+22:12:57.874 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 14d+22:12:57.874 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 14d+22:12:57.874 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 14d+22:12:57.874 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 14d+22:12:57.874 SET FEATURES [Set transfer mode] Error 176 occurred at disk power-on lifetime: 15654 hours (652 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 80 ff ff ff 4f 00 14d+22:12:55.024 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 14d+22:12:55.024 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 14d+22:12:55.024 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 14d+22:12:55.023 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 14d+22:12:55.023 SET FEATURES [Set transfer mode] Error 175 occurred at disk power-on lifetime: 15654 hours (652 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 80 ff ff ff 4f 00 14d+22:12:52.182 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 14d+22:12:52.181 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 14d+22:12:52.181 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 14d+22:12:52.181 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 14d+22:12:52.181 SET FEATURES [Set transfer mode] Error 174 occurred at disk power-on lifetime: 15654 hours (652 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 80 ff ff ff 4f 00 14d+22:12:49.331 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 14d+22:12:49.331 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 14d+22:12:49.331 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 14d+22:12:49.330 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 14d+22:12:49.330 SET FEATURES [Set transfer mode] Error 173 occurred at disk power-on lifetime: 15654 hours (652 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 80 ff ff ff 4f 00 14d+22:12:46.445 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 14d+22:12:46.445 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 14d+22:12:46.445 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 14d+22:12:46.445 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 14d+22:12:46.445 SET FEATURES [Set transfer mode] SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
он не перспективный, а мутный.
+1 за лес и пинок под зад для ускорения
мы тут про сайты вроде как
на нет и суда нет 🤣
Куда хотите туда и записывайте. Я уже привык, что все способны прочитать только один пост.
Это тоже процесс.---------- Добавлено 02.02.2015 в 09:14 ----------
Это автоматизация процесса контроля за сотрудниками, являющегося частью общего процесса закупорки бутылок на заводе.
Вы вот уперлись в одну точку, а влево и вправо даже посмотреть не хотите.
1. Открыл эксель. Занес данные сотрудника. Зашел в M1, посмотрел стату, перенес ее в эксель, отправил инфу на почту сотруднику. И так каждый день.
2. Поставил сайт (скрипт). Все.
Автоматизация?
Великий гуру и телепат сделает в Экселе аналог автоматизации от ТС? Или спустится в демагогию?
Может покажете класс? Сделайте в экселе функционал по регистрации там сотрудников, и по предоставлению им статистики по лидам, так чтобы в любой момент каждый сотрудник мог зайти и посмотреть свои
А Вы хороший специалист по определению уровня знаний по аватарке ;)
