Zobrazit příspěvky

Tato sekce Vám umožňuje zobrazit všechny příspěvky tohoto uživatele. Prosím uvědomte si, že můžete vidět příspěvky pouze z oblastí Vám přístupných.


Příspěvky - rado3105

Stran: 1 ... 29 30 [31] 32 33 ... 37
451
Kabel na poslanie prikazu na vypnutie servera...nie napajaci kabel....ale ok, ktosi sa nema s kym bavit...tak tu zije svoj zivot....

452
Takze co som zistoval tak vraj aj obycajne apc back-ups ma kabel a vypina pc....tak teraz neviem....

453
Server / Re:Kontrola druheho disku az po nabehnuti systemu?
« kdy: 22. 08. 2012, 20:48:34 »
Problem je ze ked je systemovy disk v poriadku, system nenabehne, lebo tento druhy disk, kde su len data ukazuje chyby a treba urobit manualne fsck....

454
Hardware / Re:Hardisk problem?
« kdy: 22. 08. 2012, 20:46:09 »
# smartctl -a /dev/sda
smartctl 5.40 2010-07-12 r3124 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital AV-GP family
Device Model:     WDC WD15EVDS-68V9B0
Serial Number:    WD-WMAVU0931943
Firmware Version: 01.00A01
User Capacity:    1,500,300,828,160 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Aug 22 20:45:23 2012 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:  (0x84)   Offline data collection activity
               was suspended by an interrupting command from host.
               Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 121)   The previous self-test completed having
               the read element of the test failed.
Total time to complete Offline
data collection:        (35700) 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:     ( 255) minutes.
Conveyance self-test routine
recommended polling time:     (   5) minutes.
SCT capabilities:           (0x303f)   SCT Status supported.
               SCT Error Recovery Control 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     0x002f   200   200   051    Pre-fail  Always       -       1700
  3 Spin_Up_Time            0x0027   189   180   021    Pre-fail  Always       -       5508
  4 Start_Stop_Count        0x0032   080   080   000    Old_age   Always       -       20552
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   071   071   000    Old_age   Always       -       21623
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   080   080   000    Old_age   Always       -       20550
192 Power-Off_Retract_Count 0x0032   173   173   000    Old_age   Always       -       20541
193 Load_Cycle_Count        0x0032   156   156   000    Old_age   Always       -       132097
194 Temperature_Celsius     0x0022   106   103   000    Old_age   Always       -       44
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   199   199   000    Old_age   Always       -       330
198 Offline_Uncorrectable   0x0030   199   199   000    Old_age   Offline      -       255
199 UDMA_CRC_Error_Count    0x0032   200   199   000    Old_age   Always       -       4931
200 Multi_Zone_Error_Rate   0x0008   198   198   000    Old_age   Offline      -       410

SMART Error Log Version: 1
ATA Error Count: 699 (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 699 occurred at disk power-on lifetime: 21615 hours (900 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
  -- -- -- -- -- -- --
  40 51 00 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  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 00 ff 38 40 e3 08      14:06:15.378  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:15.371  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:15.371  SET FEATURES [Set transfer mode]

Error 698 occurred at disk power-on lifetime: 21615 hours (900 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
  -- -- -- -- -- -- --
  40 51 00 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  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 00 ff 38 40 e3 08      14:06:12.690  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:12.682  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:12.682  SET FEATURES [Set transfer mode]

Error 697 occurred at disk power-on lifetime: 21615 hours (900 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
  -- -- -- -- -- -- --
  40 51 00 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  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 00 ff 38 40 e3 08      14:06:10.017  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:10.009  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:10.009  SET FEATURES [Set transfer mode]

Error 696 occurred at disk power-on lifetime: 21615 hours (900 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
  -- -- -- -- -- -- --
  40 51 00 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  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 00 ff 38 40 e3 08      14:06:07.344  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:07.336  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:07.336  SET FEATURES [Set transfer mode]

Error 695 occurred at disk power-on lifetime: 21615 hours (900 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
  -- -- -- -- -- -- --
  40 51 00 08 39 40 e3  Error: UNC at LBA = 0x03403908 = 54540552

  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 00 ff 38 40 e3 08      14:06:04.671  READ DMA
  ec 00 00 00 00 00 a0 08      14:06:04.663  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      14:06:04.663  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     21617         485393

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.

455
Distribuce / Re:Výběr distribuce
« kdy: 22. 08. 2012, 18:48:38 »
Tiez za mna jednoznacne archlinux....

456
Server / Re:Kontrola druheho disku az po nabehnuti systemu?
« kdy: 22. 08. 2012, 18:24:21 »
Kontrola disku
if mountpoint -q /media/xxx
then
   echo "kontrola nebyla provedena, disk je pripojen" >> /dev/null
else
   fsck -fyv /dev/sda1
   vystup=$?

Toto som moc nepochopil.
Predtym sa disk odmountuje, odpoja sa sluzby. Tento prikaz hovori ze ak je disk pripojeny tak sa neurobi kontrola, ak nie je tak sa urobi.
Lenze disk sa odmountuje, disk nevyzaduje kontrolu - takze nebude mountnuty.....asi by bolo vhodnejsie dat umount a vypnutie sluzieb po else a spojit to nejako s fsck alebo ? dakujem...

457
Server / Re:Kontrola druheho disku az po nabehnuti systemu?
« kdy: 22. 08. 2012, 18:22:41 »
Nikto neporadi na co som sa pytal? Phil ok to neries, proste sa nieco pytam....a rad by som keby niekto poradil....

458
Server / Re:Kontrola druheho disku az po nabehnuti systemu?
« kdy: 22. 08. 2012, 17:48:20 »
Preco by som to potreboval mat odpojene? Uvital by som background fsck, na btrfs sa tesim ako male decko....
Ale zatial to potrebujem vyriesit v zavislosti od realnej situacie a fsck sa pusta az po odpojeni....

459
Server / Re:Kontrola druheho disku az po nabehnuti systemu?
« kdy: 22. 08. 2012, 17:31:40 »
Kontrola disku
if mountpoint -q /media/xxx
then
   echo "kontrola nebyla provedena, disk je pripojen" >> /dev/null
else
   fsck -fyv /dev/sda1
   vystup=$?

Toto som moc nepochopil.
Predtym sa disk odmountuje, odpoja sa sluzby. Tento prikaz hovori ze ak je disk pripojeny tak sa neurobi kontrola, ak nie je tak sa urobi.
Lenze disk sa odmountuje, disk nevyzaduje kontrolu - takze nebude mountnuty.....asi by bolo vhodnejsie dat umount a vypnutie sluzieb po else a spojit to nejako s fsck alebo ? dakujem...

460
Server / Re:Kontrola druheho disku az po nabehnuti systemu?
« kdy: 22. 08. 2012, 16:42:57 »
A ked ho nepojde mountnut lebo tam bude vela chyb a bude treba restart?
Aky je prikaz na hlboku kontrolu disku?

461
Server / Re:Kontrola druheho disku az po nabehnuti systemu?
« kdy: 22. 08. 2012, 16:12:28 »
Dakujem chladic ak ta to potesi. Ale pravdepodobne si nepochopil co chcem. To co si napisal dokazem urobit v fstabe zmenenim 0 2 na 0 0. Alebo sa mylim?
Vlastne teraz rozmyslam ako to spravit.
Vypnem kontrolu toho disku v fstabe.
Je pripojeny ako /dev/sda1 na /media/xxx.
Takze ked odmountujem, tak klientske sluzby tam nebudu pristupovat, lebo tie pristupuju na /media/xxx nie na /dev...
Bezi tam len samba share....
Potreboval by som nejaky prikaz, ktory vzdy po zapnuti systemu - nabehnuti os, skontroloval dany disk a opravil ho, ak by trebalo restartovat tak restartoval pc.
Hlboka kontrola sa robi akym prikazom?
A velmi pekne dakujem za kazdu radu.....

462
Hardware / Re:Hardisk problem?
« kdy: 22. 08. 2012, 15:34:01 »
Vdaka...mam objednany 2 tyzdne WD RED a stale nic...tak pockam kym pride zalohujem a obnovim a budu tam tie data ulozene duplicitne...vdaka este raz...vsetkym

463
Server / Re:Kontrola druheho disku az po nabehnuti systemu?
« kdy: 22. 08. 2012, 15:32:44 »
A teraz prikaz ktory mi sam skontroluje disk po kazdom restarte ale az po nabehnuti systemu - pricom sam si ho najprv odpoji, ak su chyby restartuje system...
?

464
http://pc.bazos.sk/inzerat/17597788/Predam-zalozny-zdroj-APC-SmartUPS-700i-NET.php  taketo nieco? Ako sa to potom pripaja k pc cez rs232?
Ako sa oznacuje moznost pripojenia ext. baterie alebo ako to zistim ci tam mozem pripojit externu bateriu..?

465
Hardware / Re:Hardisk problem?
« kdy: 22. 08. 2012, 15:19:28 »
Vdaka Rhinox, vyzera ze vies o com hovoris. Este som sa chcel spytat, ked spustim prikaz: hdparm --write-sector CHS /dev/??? je tam riziko straty dat?

Stran: 1 ... 29 30 [31] 32 33 ... 37