проблемы с gmirror

Nick_mad

Здравствуйте.

Настроил себе зеркало по этой статье http://www.lissyara.su/articles/freebsd ... m/gmirror/
Проработало почти 2 года, и вот заметил на мониторе сервака что там проблемы с /dev/ad0, Глянул что там с зеркалом работало только на /dev/ad2
Как то не осознано (понедельник, утро) дал команду gmirror forget gm0 и хотел gmirror insert gm0 /dev/ad0 а оно мне

Код: Выделить всё

server# gmirror insert gm0 /dev/ad0
gmirror: Cannot store metadata on ad0.

и тут я понял что я сделал что-то не так

Теперь я не знаю что делать.
1. мне интересно что с /dev/ad0 но я не знаю как узнать
2. Может можно выкрутиться так

Код: Выделить всё

gmirror label -v -b round-robin gm0 /dev/ad2
gmirror insert gm0 /dev/ad0

подождать пока з асинхронизируются, потом

Код: Выделить всё

gmirror forget gm0

gmirror label -v -b round-robin gm0 /dev/ad0
gmirror insert gm0 /dev/ad2

Я пока боюсь вообще что-либо делать жду пока Вы порекомендуете ув спецы как быть. Подскажите плз, а то это боевой сервак, шобы не уложить его.

Хостинг HostFood.ru · **Хостинг HostFood.ru**

Тарифы на хостинг в России, от 12 рублей: https://www.host-food.ru/tariffs/hosting/
Тарифы на виртуальные сервера (VPS/VDS/KVM) в РФ, от 189 руб.: https://www.host-food.ru/tariffs/virtualny-server-vps/
Выделенные сервера, Россия, Москва, от 2000 рублей (HP Proliant G5, Intel Xeon E5430 (2.66GHz, Quad-Core, 12Mb), 8Gb RAM, 2x300Gb SAS HDD, P400i, 512Mb, BBU):
https://www.host-food.ru/tariffs/vydelennyi-server-ds/
Недорогие домены в популярных зонах: https://www.host-food.ru/domains/

vitar · Непрочитанное сообщение **vitar** » 2010-01-25 15:36:53

Дай вывод ...

Код: Выделить всё

gmirror status
gmirror list
grep ad0 /var/log/messages
smartctl -a /dev/ad0

ЗЫ. smartctl - /usr/ports/sysutils/smartmontools

Nick_mad

gmirror status

Код: Выделить всё

Name    Status  Components
mirror/gm0  COMPLETE  ad2

gmirror list

Код: Выделить всё

Geom name: gm0
State: COMPLETE
Components: 1
Balance: round-robin
Slice: 4096
Flags: NONE
GenID: 1
SyncID: 1
ID: 4086046872
Providers:
1. Name: mirror/gm0
   Mediasize: 164696555008 (153G)
   Sectorsize: 512
   Mode: r5w5e6
Consumers:
1. Name: ad2
   Mediasize: 164696555520 (153G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Priority: 0
   Flags: DIRTY
   GenID: 1
   SyncID: 1
   ID: 2200566480

grep ad0 /var/log/messages

Код: Выделить всё

Jan 25 12:05:39 server kernel: ad0: FAILURE - WRITE_DMA48 status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=321672959
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA48 status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=321672959
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=128
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=16
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=512
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=64
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=2
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=16
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=128
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA48 status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=321672959
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=1
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:05:39 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:19:57 server kernel: ad0: FAILURE - WRITE_DMA48 status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=321672959
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA48 status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=321672959
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=128
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=16
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=512
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=64
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=2
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=16
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=128
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA48 status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=321672959
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=1
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:19:57 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:20:03 server kernel: ad0: FAILURE - WRITE_DMA48 status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=321672959
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA48 status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=321672959
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=128
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=16
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=512
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=64
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=2
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=16
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=128
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA48 status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=321672959
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=1
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0
Jan 25 12:20:03 server kernel: ad0: FAILURE - READ_DMA status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=0

smartctl -a /dev/ad0

Код: Выделить всё

smartctl 5.39 2009-12-09 r2995 [FreeBSD 7.0-RELEASE i386] (local build)
Copyright (C) 2002-9 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital RE Serial ATA family
Device Model:     WDC WD1600YS-01SHB1
Serial Number:    WD-WCAP02981157
Firmware Version: 20.06C06
User Capacity:    164,696,555,520 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Mon Jan 25 18:12:24 2010 EET
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        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:                 (5580) 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:        (   2) minutes.
Extended self-test routine
recommended polling time:        (  68) minutes.
Conveyance self-test routine
recommended polling time:        (   6) minutes.
SCT capabilities:              (0x103f) SCT Status supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
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   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   183   183   021    Pre-fail  Always       -       3816
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       121
  5 Reallocated_Sector_Ct   0x0033   106   106   140    Pre-fail  Always   FAILING_NOW 749
  7 Seek_Error_Rate         0x000f   200   200   051    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   085   085   000    Old_age   Always       -       11127
 10 Spin_Retry_Count        0x0013   100   100   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0013   100   100   051    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       120
194 Temperature_Celsius     0x0022   121   096   000    Old_age   Always       -       26
196 Reallocated_Event_Count 0x0032   001   001   000    Old_age   Always       -       749
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0009   200   200   051    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 127 (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 127 occurred at disk power-on lifetime: 11127 hours (463 days + 15 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
  -- -- -- -- -- -- --
  04 61 ff 00 00 00 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 00 00  28d+05:10:58.744  IDENTIFY DEVICE
  c8 00 01 00 00 00 00 00  27d+23:19:01.026  READ DMA
  c8 00 01 00 00 00 00 00  27d+23:19:01.025  READ DMA
  c8 00 01 01 00 00 00 00  27d+23:19:01.024  READ DMA
  c8 00 01 00 00 00 00 00  27d+23:19:01.023  READ DMA

Error 126 occurred at disk power-on lifetime: 11121 hours (463 days + 9 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
  -- -- -- -- -- -- --
  04 61 01 00 00 00 e0  Device Fault; Error: ABRT 1 sectors at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 01 00 00 00 00 00  27d+23:19:01.026  READ DMA
  c8 00 01 00 00 00 00 00  27d+23:19:01.025  READ DMA
  c8 00 01 01 00 00 00 00  27d+23:19:01.024  READ DMA
  c8 00 01 00 00 00 00 00  27d+23:19:01.023  READ DMA
  25 00 01 ff 56 2c 13 00  27d+23:19:01.022  READ DMA EXT

Error 125 occurred at disk power-on lifetime: 11121 hours (463 days + 9 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
  -- -- -- -- -- -- --
  04 61 01 00 00 00 e0  Device Fault; Error: ABRT 1 sectors at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 01 00 00 00 00 00  27d+23:19:01.025  READ DMA
  c8 00 01 01 00 00 00 00  27d+23:19:01.024  READ DMA
  c8 00 01 00 00 00 00 00  27d+23:19:01.023  READ DMA
  25 00 01 ff 56 2c 13 00  27d+23:19:01.022  READ DMA EXT
  c8 00 01 00 00 00 00 00  27d+23:19:01.021  READ DMA

Error 124 occurred at disk power-on lifetime: 11121 hours (463 days + 9 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
  -- -- -- -- -- -- --
  04 61 01 01 00 00 e0  Device Fault; Error: ABRT 1 sectors at LBA = 0x00000001 = 1

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 01 01 00 00 00 00  27d+23:19:01.024  READ DMA
  c8 00 01 00 00 00 00 00  27d+23:19:01.023  READ DMA
  25 00 01 ff 56 2c 13 00  27d+23:19:01.022  READ DMA EXT
  c8 00 01 00 00 00 00 00  27d+23:19:01.021  READ DMA
  c8 00 01 80 00 00 00 00  27d+23:19:01.020  READ DMA

Error 123 occurred at disk power-on lifetime: 11121 hours (463 days + 9 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
  -- -- -- -- -- -- --
  04 61 01 00 00 00 e0  Device Fault; Error: ABRT 1 sectors at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 01 00 00 00 00 00  27d+23:19:01.023  READ DMA
  25 00 01 ff 56 2c 13 00  27d+23:19:01.022  READ DMA EXT
  c8 00 01 00 00 00 00 00  27d+23:19:01.021  READ DMA
  c8 00 01 80 00 00 00 00  27d+23:19:01.020  READ DMA
  c8 00 01 10 00 00 00 00  27d+23:19:01.019  READ DMA

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.

Nick_mad

А вообще я могу не разбирая сервак (на гарантии) выяснить что с винтом? Может подлечить его как-то можна??
Если я его просто перегружу он хоть запуститься????

vitar · Непрочитанное сообщение **vitar** » 2010-01-26 18:35:42

Вобщем винт имхо на замену. Миррор жив - но работает _только_ с ad2. Проблем при перезагрузке быть не должно.

Можно правда попробовать поремапить бедсектора с помощью badblocks(/usr/ports/sysutils/e2fsprogs) и попытаться его добавить в миррор снова, но помоему безсмысленно.

Nick_mad

Я так понял винт начал сыпаться???

Комп на гарантии, сказали поменяют винт.
После того как поменяют нужно будет запустить сервак, но мне кажется он не загрузится так как на /dev/ad0 не будет MBR.

Наверное в биосе поставить загрузку с ad2 а потом выполнить с учетом того что я давал ранее команду gmirror forget gm0

Код: Выделить всё

gmirror insert gm0 /dev/ad0
gmirror rebuild gm0 /dev/ad0

потом поставить в биосе загрузку обратно с ad0

Я правильно все описал????

vitar · Непрочитанное сообщение **vitar** » 2010-01-27 12:29:06

Да все верно.

Nick_mad · Непрочитанное сообщение **Nick_mad** » 2013-09-16 9:12:02

Здравствуйте.
Так как проблема с тем же сервером и схожа по сути то решил продолжить тему.
Вчера перегружал сервак и утром в мыле увидел

Код: Выделить всё

ad2: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset
ad2: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset
ad2: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset
ad2: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset
ad2: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset
ad2: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset
ad2: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset
ad2: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset
ad2: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
ad2: 239429MB <WDC WD2502ABYS-02B7A0 02.03B03> at ata1-master UDMA100 SATA 3Gb/s
ad2: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset
ad2: WARNING - READ_DMA48 requeued due to channel reset LBA=490350669
ad2: WARNING - READ_DMA48 requeued due to channel reset LBA=490350671
ad2: WARNING - READ_DMA48 requeued due to channel reset LBA=490350655
ad2: WARNING - READ_DMA requeued due to channel reset LBA=128
ad2: WARNING - READ_DMA48 requeued due to channel reset LBA=490350668
ad2: WARNING - READ_DMA requeued due to channel reset LBA=16
ad2: WARNING - READ_DMA48 requeued due to channel reset LBA=490350671
ad2: WARNING - READ_DMA requeued due to channel reset LBA=0
ad2: WARNING - READ_DMA48 requeued due to channel reset LBA=490350671
ad2: WARNING - READ_DMA requeued due to channel reset LBA=512
ad2: WARNING - READ_DMA48 requeued due to channel reset LBA=490350609
ad2: WARNING - READ_DMA requeued due to channel reset LBA=128
ad2: WARNING - READ_DMA requeued due to channel reset LBA=16
ad2: WARNING - READ_DMA requeued due to channel reset LBA=0
ad2: WARNING - READ_DMA requeued due to channel reset LBA=512
ad2: WARNING - READ_DMA requeued due to channel reset LBA=64
ad2: WARNING - READ_DMA requeued due to channel reset LBA=0
ad2: WARNING - READ_DMA requeued due to channel reset LBA=2
ad2: WARNING - READ_DMA requeued due to channel reset LBA=16
ad2: WARNING - READ_DMA requeued due to channel reset LBA=128
ad2: WARNING - READ_DMA requeued due to channel reset LBA=0
ad2: WARNING - READ_DMA48 requeued due to channel reset LBA=490350671
ad2: WARNING - READ_DMA requeued due to channel reset LBA=0
ad2: WARNING - READ_DMA requeued due to channel reset LBA=0
ad2: WARNING - READ_DMA requeued due to channel reset LBA=1

# smartctl -a /dev/ad2

Код: Выделить всё

smartctl 6.2 2013-07-26 r3841 [FreeBSD 8.4-RELEASE i386] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/ad2: Unable to detect device type
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

Хотя когда первый раз смотрел смарт то оно его вывело а сейчас не хочет.

Что посоветуете, может просто разобрать сервак подергать sata кабеля или капец винту???

gumeniuc · Непрочитанное сообщение **gumeniuc** » 2013-09-16 9:29:56

Однажды внезапно начались сыпаться READ_DMA, думаю всё, капец винту. Оказалось тамошние ребята шлейф поменять решили. Поставил другой, завелось без проблем.

Nick_mad

Странно, пока винт не вытянул, сетка глючила.

Проверяю винт вроде целый, бедов нет, смарт нормальный, проверяю винт на том кабеле с которым он стоял в серваке, работает отлично.

Посоветуйте, как лучше, теперь сделать. Наверное отформатировать его чтобы когда его вставил в сервак он с него не загрузился??

А на горячую можно винты втыкать?? Как их потом подключать чтобы система увидела??

Nick_mad

Проверил винт, поменял кабель, подключил на тот самый канал, ситуация та же, подцепил на другой канал заработало.

Наверное материнка доходит потихоньку, сначала встроенная сетевая, теперь сата канал, нужно собирать деньги на новую мать.

Такой еще вопрос я подключил винт он стал ad1, и не посмотрев что он начал синхронизироваться дал команду (ну не думал я что он подхватит ad1 вместо ad2)

Код: Выделить всё

gmirror forget gm0

Значит ли это что нужно заново создавать зеркало?

Код: Выделить всё

gmirror label -v -b round-robin gm0 /dev/ad0
gmirror insert gm0 /dev/ad1

forum.lissyara.su

проблемы с gmirror

проблемы с gmirror

Услуги хостинговой компании Host-Food.ru

Re: проблемы с gmirror

Re: проблемы с gmirror

Re: проблемы с gmirror

Re: проблемы с gmirror

Re: проблемы с gmirror

Re: проблемы с gmirror

Re: проблемы с gmirror

Re: проблемы с gmirror

Re: проблемы с gmirror

Re: проблемы с gmirror