LinuxForum.Fans
Тема

ошибка чтения /dev/sda

Автор: live_in_sky_dreams 20 сообщений 4957 просмотров
21.10.2013 13:39 #344733

Серв на Debian Squeeze. DDS без kvm
RAID программный - 1
работает больше года.

На сервере установлен
wine - баловался
Appache
PHP
MySQL
VirtualBox

В VB - 2 рабочих тачки (Terminal server) и вторая - полигон для моих испытаний

Намечалось прибавление тачек и я решил отойти от VB и посмотреть в сторону proxmox

отредактировал /apt/sources.list
сделал Full-upgrade

дальше начал ставить pve. Ядро и заголовки.

Показать
text
root@Fiona:~# aptitude install pve-headers-2.6.32-19-pve
Следующие НОВЫЕ пакеты будут установлены:        
  pve-headers-2.6.32-19-pve pve-kernel-2.6.32-19-pve{a} 
0 пакетов обновлено, 2 установлено новых, 0 пакетов отмечено для удаления, и 120 пакетов не обновлено.
Необходимо получить 38,3 MB архивов. После распаковки 0 B будет занято.
Хотите продолжить? [Y/n/?] y
Получить:1 http://download.proxmox.com/debian/ squeeze/pve pve-kernel-2.6.32-19-pve amd64 2.6.32-96 [31,9 MB]
Получить:2 http://download.proxmox.com/debian/ squeeze/pve pve-headers-2.6.32-19-pve amd64 2.6.32-96 [6 322 kB]
Получено 38,3 MБ в 5с (7 153 kБ/с)                     
Выбор ранее не выбранного пакета pve-kernel-2.6.32-19-pve.
(Чтение базы данных ... 
dpkg: предупреждение: список файлов пакета «libwine-twain» отсутствует, предполагаем, что на данный момент у пакета нет установленных файлов.
(Чтение базы данных ... 5%
dpkg: предупреждение: список файлов пакета «libwine-devel» отсутствует, предполагаем, что на данный момент у пакета нет установленных файлов.
(Чтение базы данных ... 35%
dpkg: предупреждение: список файлов пакета «wine-gecko» отсутствует, предполагаем, что на данный момент у пакета нет установленных файлов.
(Чтение базы данных ... на данный момент установлено 116419 файлов и каталогов.)
Распаковывается пакет pve-kernel-2.6.32-19-pve (из файла .../pve-kernel-2.6.32-19-pve_2.6.32-96_amd64.deb)...
Выбор ранее не выбранного пакета pve-headers-2.6.32-19-pve.
Распаковывается пакет pve-headers-2.6.32-19-pve (из файла .../pve-headers-2.6.32-19-pve_2.6.32-96_amd64.deb)...
Настраивается пакет pve-kernel-2.6.32-19-pve (2.6.32-96) ...
update-initramfs: Generating /boot/initrd.img-2.6.32-19-pve
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
Generating grub.cfg ...
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
Found background image: /usr/share/images/desktop-base/desktop-grub.png
error: cannot read from `/dev/sda'.
Found linux image: /boot/vmlinuz-2.6.32-19-pve
Found initrd image: /boot/initrd.img-2.6.32-19-pve
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
error: cannot read from `/dev/sda'.
Found linux image: /boot/vmlinuz-2.6.32-5-amd64
Found initrd image: /boot/initrd.img-2.6.32-5-amd64
error: cannot read from `/dev/sda'.
done
Настраивается пакет pve-headers-2.6.32-19-pve (2.6.32-96) ...
done

невозможность прочитать /dev/sda меня смутила...
Вывел список дисков:

Показать
text
fdisk -l | grep '^Disk'
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/sdb: 750.2 GB, 750156374016 bytes
Disk identifier: 0x000b1c15
Disk /dev/md0: 2146 MB, 2146369536 bytes
Disk identifier: 0x00000000
Disk /dev/md1: 536 MB, 536805376 bytes
Disk identifier: 0x00000000
Disk /dev/md2: 747.5 GB, 747471044608 bytes
Disk identifier: 0x00000000

Ребутить тачку как то очкую, может не загрузиться, а kvm нет, а сервер очень далеко...
Рабочие тачки в Vb надолго останавливать тоже нельзя. Если у меня сейчас все полетит - то дня на восстановление у меня нет.

Возможно ли как то диагностировать проблему без ребута и остановки работы сервера?
Я новичок в линуксе, по возможности помогите не наделать ошибок.

21.10.2013 13:39 #344734

root@Fiona ~ # cat /proc/mdstat

Показать
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md2 : active raid1 sda3[2](F) sdb3[1]
729952192 blocks [2/1] [_U]

md1 : active raid1 sda2[2](F) sdb2[1]
524224 blocks [2/1] [_U]

md0 : active raid1 sda1[2](F) sdb1[1]
2096064 blocks [2/1] [_U]

unused devices: <none>
21.10.2013 14:01 #344735

Вобщем я понял. Развалился программный рэйд.
Какого он развалился только непонятно. Я туда не лазил, конфиги рэйда от провайдера были..

Как восстановить рэйд "нагорячую"? Возможно ли это?

21.10.2013 14:08 #344736

mdadm --detail /dev/md0

Показать
/dev/md0:
Version : 0.90
Creation Time : Mon Aug 20 16:31:59 2012
Raid Level : raid1
Array Size : 2096064 (2047.28 MiB 2146.37 MB)
Used Dev Size : 2096064 (2047.28 MiB 2146.37 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Mon Oct 21 10:59:47 2013
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0

UUID : 74587896:b8b73ab6:776c2c25:004bd7b2
Events : 0.44

Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync /dev/sdb1

2 8 1 - faulty spare /dev/sda1

Failed Devices : 1
Означает, что диск умер? Или он просто "выпал" из рэйда?

21.10.2013 15:03 #344747

Уже понял и начал катать письмо в ТП на площадку где сервак.
Но вот подумал тут, а как узнать загрузчик где у меня стоит? В рейде или нет?
Если они остановят сервак для замены харда, получается я потом его не запущу....

21.10.2013 15:04 #344748

Или правильнее будет сказать так:
как мне подготовить систему СЕЙЧАС ДО ВЫКЛЮЧЕНИЯ таким образом, чтобы она у меня запустилась ПОСЛЕ выключения?
Перезаписать загрузчик и т.д.

21.10.2013 16:32 #344758

Загрузчик причем? Сервак же ж виртуальный? Мало информации.

21.10.2013 17:11 #344765
"live.in.sky.dreams" написал:
Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md2 doesn't contain a valid partition table

так он просто потерял таблицу разделов.

"live.in.sky.dreams" написал:
error: cannot read from `/dev/sda'.

вывод dmesg + /var/log/messages само собой напрашивается.

21.10.2013 23:51 #344802

вывод dmesg превышает лимит на сообщение в этом форуме

21.10.2013 23:52 #344803
"karl_muenhgausen" написал:
Загрузчик причем? Сервак же ж виртуальный? Мало информации.

Нет, сам сервак не виртуальный. Debian стоит на хостовой тачке.
Какая информация нужна еще?

22.10.2013 00:02 #344805
"i2ks" написал:
вывод dmesg + /var/log/messages само собой напрашивается.

куча хрени вот такого рода (полностью не помещается, это кусок сначала вывода)
dmesg

Показать
dmesg
ead(10): 28 00 00 00 00 00 00 00 08 00
[12539294.447155] end_request: I/O error, dev sda, sector 0
[12539294.447156] Buffer I/O error on device sda, logical block 0
[12539595.915779] sd 0:0:0:0: [sda] Unhandled error code
[12539595.915781] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12539595.915783] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[12539595.915787] end_request: I/O error, dev sda, sector 0
[12539595.915789] Buffer I/O error on device sda, logical block 0
[12539595.915810] sd 0:0:0:0: [sda] Unhandled error code
[12539595.915811] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12539595.915813] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 57 54 66 e8 00 00 08 00
[12539595.915817] end_request: I/O error, dev sda, sector 1465149160
[12539595.915818] Buffer I/O error on device sda, logical block 183143645
[12539595.915839] sd 0:0:0:0: [sda] Unhandled error code
[12539595.915841] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12539595.915842] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[12539595.915846] end_request: I/O error, dev sda, sector 0
[12539595.915848] Buffer I/O error on device sda, logical block 0
[12539697.393908] Registering the dns_resolver key type
[12539697.393926] Slow work thread pool: Starting up
[12539697.394010] Slow work thread pool: Ready
[12539697.519254] CIFS VFS: cifs_mount failed w/return code = -22
[12539729.564497] AIF:UNPRIV connect attempt: IN=eth0 OUT= MAC=8c:89:a5:17:d2:4c:00:26:88:75:c1:9f:08:00 SRC=95.211.199.79 DST=213.239.194.90 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=2659 DF PROTO=TCP SPT=63340 DPT=8888 WINDOW=8192 RES=0x00 SYN URGP=0
[12539732.559242] AIF:UNPRIV connect attempt: IN=eth0 OUT= MAC=8c:89:a5:17:d2:4c:00:26:88:75:c1:9f:08:00 SRC=95.211.199.79 DST=213.239.194.90 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=6698 DF PROTO=TCP SPT=63340 DPT=8888 WINDOW=8192 RES=0x00 SYN URGP=0
[12539900.020103] sd 0:0:0:0: [sda] Unhandled error code
[12539900.020105] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12539900.020107] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 20 00
[12539900.020111] end_request: I/O error, dev sda, sector 0
[12539900.020113] Buffer I/O error on device sda, logical block 0
[12539900.020116] Buffer I/O error on device sda, logical block 1
[12539900.020118] Buffer I/O error on device sda, logical block 2
[12539900.020120] Buffer I/O error on device sda, logical block 3
[12539900.020132] sd 0:0:0:0: [sda] Unhandled error code
[12539900.020134] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12539900.020135] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[12539900.020139] end_request: I/O error, dev sda, sector 0
[12539900.020140] Buffer I/O error on device sda, logical block 0
[12539900.020158] sd 0:0:0:0: [sda] Unhandled error code
[12539900.020159] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12539900.020160] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 57 54 66 e8 00 00 08 00
[12539900.020164] end_request: I/O error, dev sda, sector 1465149160
[12539900.020166] Buffer I/O error on device sda, logical block 183143645
[12539900.020177] sd 0:0:0:0: [sda] Unhandled error code
[12539900.020178] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12539900.020180] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 57 54 66 e8 00 00 08 00
[12539900.020184] end_request: I/O error, dev sda, sector 1465149160
[12539900.020185] Buffer I/O error on device sda, logical block 183143645
[12539900.020204] sd 0:0:0:0: [sda] Unhandled error code
[12539900.020205] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12539900.020207] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[12539900.020210] end_request: I/O error, dev sda, sector 0
[12539900.020211] Buffer I/O error on device sda, logical block 0
[12539986.001710] CIFS VFS: cifs_mount failed w/return code = -22
[12540035.819687] CIFS VFS: cifs_mount failed w/return code = -22
[12540195.924041] sd 0:0:0:0: [sda] Unhandled error code
[12540195.924044] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12540195.924046] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 10 00
[12540195.924050] end_request: I/O error, dev sda, sector 0
[12540195.924052] Buffer I/O error on device sda, logical block 0
[12540195.924055] Buffer I/O error on device sda, logical block 1
[12540195.924070] sd 0:0:0:0: [sda] Unhandled error code
[12540195.924072] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12540195.924074] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[12540195.924077] end_request: I/O error, dev sda, sector 0
[12540195.924079] Buffer I/O error on device sda, logical block 0
[12540195.924095] sd 0:0:0:0: [sda] Unhandled error code
[12540195.924096] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12540195.924098] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 57 54 66 e8 00 00 08 00
[12540195.924101] end_request: I/O error, dev sda, sector 1465149160
[12540195.924103] Buffer I/O error on device sda, logical block 183143645
[12540195.924125] sd 0:0:0:0: [sda] Unhandled error code
[12540195.924126] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12540195.924128] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[12540195.924133] end_request: I/O error, dev sda, sector 0
[12540195.924135] Buffer I/O error on device sda, logical block 0
[12540286.050063] CIFS VFS: cifs_mount failed w/return code = -22
[12540337.506838] CIFS VFS: cifs_mount failed w/return code = -22
[12540480.184497] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=8c:89:a5:17:d2:4c:00:26:88:75:c1:9f:08:00 SRC=46.226.165.132 DST=213.239.194.90 LEN=52 TOS=0x00 PREC=0x00 TTL=51 ID=2729 DF PROTO=TCP SPT=1117 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0
[12540483.164012] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=8c:89:a5:17:d2:4c:00:26:88:75:c1:9f:08:00 SRC=46.226.165.132 DST=213.239.194.90 LEN=52 TOS=0x00 PREC=0x00 TTL=51 ID=2736 DF PROTO=TCP SPT=1117 DPT=139 WINDOW=65535 RES=0x00 SYN URGP=0
[12540510.624750] sd 0:0:0:0: [sda] Unhandled error code
[12540510.624752] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[12540510.624759] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[12540510.624763] end_request: I/O error, dev sda, sector 0
[12540510.624765] Buffer I/O error on device sda, logical block 0
[12540510.624803] sd 0:0:0:0: [sda] Unhandled error code

/var/log/messages лежит тут

22.10.2013 00:02 #344806
"verg" написал:
Воспользуйтесь одним из paste-сервисов,

Ага, сейчас

22.10.2013 00:28 #344809

На всякий вот вывод smartctl /dev/sda -x

Показать
smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

Device: /0:0:0:0 Version:
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

В то время как # smartctl /dev/sdb -x

Показать
smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.12 family
Device Model: ST3750528AS
Serial Number: 5VP3CKDG
Firmware Version: CC38
User Capacity: 750 156 374 016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Oct 21 21:43:50 2013 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 625) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 165) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 103 092 006 Pre-fail Always - 5403506
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 26
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 123668665
9 Power_On_Hours 0x0032 080 080 000 Old_age Always - 18372
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 13
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 045 045 000 Old_age Always - 55
188 Command_Timeout 0x0032 100 097 000 Old_age Always - 6
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 061 058 045 Old_age Always - 39 (Lifetime Min/Max 33/42)
194 Temperature_Celsius 0x0022 039 042 000 Old_age Always - 39 (0 21 0 0)
195 Hardware_ECC_Recovered 0x001a 052 031 000 Old_age Always - 5403506
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 77309429737
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 4205715983
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1121026904

General Purpose Logging (GPL) feature set supported
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
GP/S Log at address 0x00 has 1 sectors [Log Directory]
GP/S Log at address 0x01 has 1 sectors [Summary SMART error log]
GP/S Log at address 0x02 has 5 sectors [Comprehensive SMART error log]
GP Log at address 0x03 has 5 sectors [Ext. Comprehensive SMART error log]
GP/S Log at address 0x06 has 1 sectors [SMART self-test log]
GP Log at address 0x07 has 1 sectors [Extended self-test log]
GP/S Log at address 0x09 has 1 sectors [Selective self-test log]
GP Log at address 0x10 has 1 sectors [NCQ Command Error]
GP Log at address 0x11 has 1 sectors [SATA Phy Event Counters]
GP Log at address 0x21 has 1 sectors [Write stream error log]
GP Log at address 0x22 has 1 sectors [Read stream error log]
GP/S Log at address 0x80 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x81 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x82 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x83 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x84 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x85 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x86 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x87 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x88 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x89 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8a has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8b has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8c has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8d has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8e has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8f has 16 sectors [Host vendor specific log]
GP/S Log at address 0x90 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x91 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x92 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x93 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x94 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x95 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x96 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x97 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x98 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x99 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9a has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9b has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9c has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9d has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9e has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9f has 16 sectors [Host vendor specific log]
GP/S Log at address 0xa1 has 20 sectors [Device vendor specific log]
GP Log at address 0xa2 has 2248 sectors [Device vendor specific log]
GP/S Log at address 0xa8 has 129 sectors [Device vendor specific log]
GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log]
GP Log at address 0xb0 has 2928 sectors [Device vendor specific log]
GP Log at address 0xbd has 252 sectors [Device vendor specific log]
GP Log at address 0xbe has 65535 sectors [Device vendor specific log]
GP Log at address 0xbf has 65535 sectors [Device vendor specific log]
GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log]
GP/S Log at address 0xe0 has 1 sectors [SCT Command/Status]
GP/S Log at address 0xe1 has 1 sectors [SCT Data Transfer]

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 55 (device log contains only the most recent 20 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 55 [14] occurred at disk power-on lifetime: 18022 hours (750 days + 22 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 48 2b 00 18 39 00 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 48 2a 00 18 50 40 00 42d+02:11:12.094 READ FPDMA QUEUED
60 00 00 01 00 00 48 29 00 18 50 40 00 42d+02:11:12.089 READ FPDMA QUEUED
60 00 00 01 00 00 48 28 00 18 50 40 00 42d+02:11:12.084 READ FPDMA QUEUED
60 00 00 00 40 00 48 25 00 18 90 40 00 42d+02:11:12.066 READ FPDMA QUEUED
60 00 00 00 20 00 48 25 00 18 70 40 00 42d+02:11:12.059 READ FPDMA QUEUED

Error 54 [13] occurred at disk power-on lifetime: 17857 hours (744 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 48 2b 00 18 39 00 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 48 2b 00 18 38 40 00 35d+04:44:04.845 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+04:44:04.844 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 00 00 00 00 00 a0 00 35d+04:44:04.843 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 35d+04:44:04.843 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+04:44:04.816 READ NATIVE MAX ADDRESS EXT

Error 53 [12] occurred at disk power-on lifetime: 17857 hours (744 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 48 2b 00 18 39 00 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 48 2b 00 18 38 40 00 35d+04:44:01.648 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+04:44:01.648 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 00 00 00 00 00 a0 00 35d+04:44:01.647 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 35d+04:44:01.647 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+04:44:01.647 READ NATIVE MAX ADDRESS EXT

Error 52 [11] occurred at disk power-on lifetime: 17857 hours (744 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 48 2b 00 18 39 00 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 48 2b 00 18 38 40 00 35d+04:43:58.460 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+04:43:58.460 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 00 00 00 00 00 a0 00 35d+04:43:58.459 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 35d+04:43:58.458 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+04:43:58.458 READ NATIVE MAX ADDRESS EXT

Error 51 [10] occurred at disk power-on lifetime: 17857 hours (744 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 48 2b 00 18 39 00 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 48 2b 00 18 38 40 00 35d+04:43:55.262 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+04:43:55.262 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 00 00 00 00 00 a0 00 35d+04:43:55.261 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 35d+04:43:55.260 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+04:43:55.241 READ NATIVE MAX ADDRESS EXT

Error 50 [9] occurred at disk power-on lifetime: 17857 hours (744 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 48 2b 00 18 39 00 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 48 2b 00 18 38 40 00 35d+04:43:52.066 READ FPDMA QUEUED
60 00 00 00 08 00 48 87 00 10 b0 40 00 35d+04:43:52.066 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+04:43:52.065 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 00 00 00 00 00 a0 00 35d+04:43:52.065 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 35d+04:43:52.064 SET FEATURES [Set transfer mode]

Error 49 [8] occurred at disk power-on lifetime: 17857 hours (744 days + 1 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 48 2b 00 18 39 00 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 48 2b 00 18 38 40 00 35d+04:43:43.664 READ FPDMA QUEUED
60 00 00 00 08 00 0b 83 00 10 f8 40 00 35d+04:43:43.539 READ FPDMA QUEUED
60 00 00 00 08 00 0b 8d 00 10 c0 40 00 35d+04:43:43.534 READ FPDMA QUEUED
60 00 00 00 08 00 0b 83 00 10 78 40 00 35d+04:43:43.518 READ FPDMA QUEUED
60 00 00 00 08 00 0a 8d 00 d0 d8 40 00 35d+04:43:43.517 READ FPDMA QUEUED

Error 48 [7] occurred at disk power-on lifetime: 17854 hours (743 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 48 2b 00 18 39 00 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 48 2b 00 18 38 40 00 35d+02:11:13.053 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+02:11:13.052 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 00 00 00 00 00 a0 00 35d+02:11:13.052 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 35d+02:11:13.051 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 35d+02:11:13.051 READ NATIVE MAX ADDRESS EXT

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 7202 -
# 2 Extended offline Completed without error 00% 5542 -
# 3 Extended offline Completed without error 00% 2334 -
# 4 Extended offline Completed without error 00% 2302 -

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.

SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 39 Celsius
Power Cycle Min/Max Temperature: 33/42 Celsius
Lifetime Min/Max Temperature: 21/42 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 59 minutes
Min/Max recommended Temperature: 14/55 Celsius
Min/Max Temperature Limit: 10/60 Celsius
Temperature History Size (Index): 128 (55)

Index Estimated Time Temperature Celsius
56 2013-10-16 16:43 38 *******************
... ..( 6 skipped). .. *******************
63 2013-10-16 23:36 38 *******************
64 2013-10-17 00:35 40 *********************
65 2013-10-17 01:34 38 *******************
... ..( 21 skipped). .. *******************
87 2013-10-17 23:12 38 *******************
88 2013-10-18 00:11 39 ********************
89 2013-10-18 01:10 38 *******************
... ..( 21 skipped). .. *******************
111 2013-10-18 22:48 38 *******************
112 2013-10-18 23:47 40 *********************
113 2013-10-19 00:46 38 *******************
... ..( 13 skipped). .. *******************
127 2013-10-19 14:32 38 *******************
0 2013-10-19 15:31 37 ******************
1 2013-10-19 16:30 38 *******************
2 2013-10-19 17:29 37 ******************
... ..( 4 skipped). .. ******************
7 2013-10-19 22:24 37 ******************
8 2013-10-19 23:23 39 ********************
9 2013-10-20 00:22 37 ******************
... ..( 11 skipped). .. ******************
21 2013-10-20 12:10 37 ******************
22 2013-10-20 13:09 38 *******************
23 2013-10-20 14:08 37 ******************
... ..( 7 skipped). .. ******************
31 2013-10-20 22:00 37 ******************
32 2013-10-20 22:59 38 *******************
33 2013-10-20 23:58 37 ******************
... ..( 9 skipped). .. ******************
43 2013-10-21 09:48 37 ******************
44 2013-10-21 10:47 38 *******************
45 2013-10-21 11:46 37 ******************
46 2013-10-21 12:45 38 *******************
47 2013-10-21 13:44 38 *******************
48 2013-10-21 14:43 41 **********************
49 2013-10-21 15:42 39 ********************
50 2013-10-21 16:41 40 *********************
51 2013-10-21 17:40 37 ******************
52 2013-10-21 18:39 38 *******************
53 2013-10-21 19:38 37 ******************
54 2013-10-21 20:37 38 *******************
55 2013-10-21 21:36 38 *******************

SCT Error Recovery Control:
Read: Disabled
Write: Disabled

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 382 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
22.10.2013 02:44 #344818

Хард заменили, сервак не стартует.
Заказал LARA, у меня будет 2 часа. Гляну что и как, но скорее всего загрузчик ((

22.10.2013 09:38 #344830

Тему можно закрывать.
Сервак так и не стартанул. Через LARA посмотрел - при попытке загрузки GRUB-а уходит в ребут.
При прошлой установке Grub не встал на второй диск, как я нарыл в гугле - нужно было после установки вручную писать GRUB на диск №2.

Поставил Debian и proxmox, сижу настраиваю.
Всем спасибо за помощь!

22.10.2013 11:31 #344848

live.in.sky.dreams, чаво-чаво? Какой ещё диск 2? Загрузчик должен быть в корне диска, стоящего первым на загрузку. В нормально установленной системе это sda.

22.10.2013 17:53 #344943
"live.in.sky.dreams" написал:
RAID программный - 1
"karl_muenhgausen" написал:
live.in.sky.dreams, чаво-чаво? Какой ещё диск 2? Загрузчик должен быть в корне диска, стоящего первым на загрузку. В нормально установленной системе это sda.

как бы надо было сделать примерно следующие:

Софт рейд, не получается скопировать загрузчик Grub

Войдите или зарегистрируйтесь, чтобы ответить.