Skocz do zawartości

zoltan2

Użytkownik
  • Liczba zawartości

    517
  • Rejestracja

  • Ostatnia wizyta

Posty dodane przez zoltan2

  1. Manta ma obraz zbliżony do innych markowych w tej cenie, czasem nawet lepszy, ale faktem jest że to straszny szmelc. Skoro się śmiali w sklepie to wiedza o czym mówię bo sam to sprzedaję.

     

    Ktoś wyżej pisał że taki sam jak TCL, otoz to że nie. tCL to naprawdę fajne TV. Jak chcesz kupić tv to idź w ten weekend do jakiegoś media czy euro i kup to co ci się podoba w tej cenie, byle markowe. W końcu jest Black Friday, w większości do niedzieli. Spiesz się.

  2. Ilość pamięci jest wystarczajaca,

     

    Ja mam x4 955 i R9 285 i 8GB ram, gram na najwyższych, poza dwoma opcjami. I mimo karty 2GB to ustawienia w grze mam na prawie 2.5GB i wszystko ładnie śmiga.

     

    Więc przyczyny trzeba szukać gdzieś indziej. Sprawdź obciążenie CPU i gpu

     

    Ps, ja mam na dodatek jakiś stary prawie 10cio letni dysk HDD który swoje dobre czasy już dawno zapomniał i te transfery nie są najwyższych lotów.

  3. Ja tylko dołożę swoje 3 grosze.

     

     

    Kupuj coś gdzie masz dużo vramu, czyli właśnie 1060 6GB jak polecają.

     

    Wczoraj sobie odpaliłem COD WWII, ja mam R9 285 2GB i gierka śmiga na najwyższych FHD bez dwóch ustawien ale zbiera 2400 MB vram, takie 6GB to powinno być minimum na dzień dzisiejszy. Iw ostatnich 2ch latach nastąpił spory skok ilościowy tej pamięci w kartach i teraz podejrzewam że nowe wydania gier będą je coraz częściej wykorzystywać.

  4. Zaczne od inpulag, nie przejmuj się nim. Baw się dobrze ;)

     

    Zwykłej klawiatury i myszki nie podepniesz pod konsole.

     

    Twój Procek ma jeszcze spory zapas mocy względem grafiki i tylko ja musiałbyś wymienic, nic więcej.

     

    Wg mojej opinii, kupujesz PS4 pro za 1500 jak trafisz promo dobre i za resztę weź sobie używaną grafike.

  5. A idzie to jakoś naprawić? To wyrównanie? I muszę pod zwykły pc podpiąć? Nie da rady przez sieć?

     

     

     

    Teraz z ciekawości przeczytałem sobie test tego dysku sprzed 6ciu lat. I one nigdy nie osiągały takich prędkości jak ja miałem gdy montowałem NAS.

     

    HMMMMmMM

     

     

     

    Tutaj załączam zdjęcie z transferu, w sierpniu robione. I widać że transfer jest w miarę stabilny na wysokim poziomie.

    7da080975bced2aec1f9e0f4bba45d95.jpg

  6. Mam tam pełno danych na tym dysku. Niechce go ruszać aby nie zepsuć nic w systemie plików czy coś tam. Dlatego myślałem że może jakość z innego PC można to zrobić zdalnie.

     

    Tak, ruszałem go, od końca sierpnia chodzi praktycznie non stop. Przy sprzątaniu przesuwam go 20cm w prawo i 20cm w lewo. Jest to delikatne przesunięcie więc wykluczylbym to. Raczej fakt że już trochę czasu ma ten dysk przepracowane, wcześniej chodził normalnie w stacjonarne jako dysk na dane.

     

    Chciałem tylko sprawdzić czy spowolnienie transferu aż do 2/3 mniej jest wina dysku czy czegoś innego.

     

     

     

    Nie wiem co to jest bf niezerowy, a gwarancja już dawno się skończyła bo mam go chyba z 6 lat. Kupowałem go chyba jeszcze przed bumem cenowym na dyski sprzed kilku lat. Wtedy 4 stówki za niego dalem.

  7. Witam, 

     

    prośba o małą pomoc i dopowiedzenie.

     

    Zastosowanie komputera: Gry, głównie strzelanki i może jakaś strategia, czy FM. Od reszty mam PS4.

    Maksymalna kwota jaką dysponujesz: 3000 zł

    Kiedy zamierzam kupić komputer? po nowym roku

    Czy będziesz podkręcać sprzęt? nie umiem. Moze kiedyś jak będzie potrzeba.

    Specjalne wymagania: cisza

    Jaką rozdzielczość posiada Twój monitor?: TV FHD, z wymianą na 4k gdy się zepsuje, więc pewnie nie długo. Obstawiam max 2 lata bo syn zaraz zacznie chodzić ;)

    Których części potrzebujesz?: procesor+ chlodzenie, płyta, ram, SSD M2 (jak najszybsza możliwa opcja na której mogę postawić system + kilka gier)

    Czy posiadasz jakieś części z poprzedniego komputera? obudowa i zasilacz Corsair z sygnatury, grafika z sygnatury, chłodzenie które mam z am3 będzie pasowało pod AM4 gdybym się zdecydował na zestaw z Ryzenem? Wtedy wszystko by mnie dużo taniej wyniosło?

    Własna propozycja zestawu wg cen z Komputronika:

    - Samsung 960 Evo M.2 250GB 560zł 

    - Crucial Ballistix Sport 2x4GB 2400MHz DDR4 CL16 UDIMM 1.2V 380zł

    - intel i5-8600k 1230 zł

     

    Może lepiej wziąć I7-8700(non k) bo ma załączone dodatkowo chłodzenie a I5-8600k nie ma, różnica w cenie 200zł z haczykiem

     

    Inne: Grafikę raczej też będę zmieniał na taką która będzie miała więcej pamieci, ale w późniejszym terminie, budżet na nią będzie z tego co mi zostanie (chyba nic plus sprzedaż obecnych części. Póki co ta mi wystarczy jako tako, przynajmniej tak mi się wydaje. Na razie siedzę awaryjnie na x4 955 i 8 GB ramu, reszta tak jak w sygnaturce. PS im mniej wyjdzie tym lepiej. Ma to być na lata, ostatnio składalem niedługo po premierze Phenomow II i czasowo tak samo bym chciał bez dokupowania czegokolwiek. Ma to chodzić ;) 

     

     

    Dzięki

  8. No to tak

     

    Zakładka z dodatkowych informacji

    smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.9.0-0.bpo.3-amd64] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Family:     SAMSUNG SpinPoint F4 EG (AF)
    Device Model:     SAMSUNG HD204UI
    Serial Number:    S2H7J1CZA01707
    LU WWN Device Id: 5 0024e9 00426c007
    Firmware Version: 1AQ10001
    User Capacity:    2,000,397,852,160 bytes [2.00 TB]
    Sector Size:      512 bytes logical/physical
    Rotation Rate:    5400 rpm
    Form Factor:      3.5 inches
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ATA8-ACS T13/1699-D revision 6
    SATA Version is:  SATA 2.6, 3.0 Gb/s
    Local Time is:    Thu Nov 16 17:03:19 2017 CET
    
    ==> WARNING: Using smartmontools or hdparm with this
    drive may result in data loss due to a firmware bug.
    ****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
    Buggy and fixed firmware report same version number!
    See the following web pages for details:
    http://knowledge.seagate.com/articles/en_US/FAQ/223571en
    http://www.smartmontools.org/wiki/SamsungF4EGBadBlocks
    
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    AAM feature is:   Disabled
    APM level is:     254 (maximum performance)
    Rd look-ahead is: Enabled
    Write cache is:   Enabled
    ATA Security is:  Disabled, NOT FROZEN [SEC1]
    Wt Cache Reorder: 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: 		(20460) seconds.
    Offline data collection
    capabilities: 			 (0x5b) SMART execute Offline immediate.
    					Auto Offline data collection on/off support.
    					Suspend Offline collection upon new
    					command.
    					Offline surface scan supported.
    					Self-test supported.
    					No 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: 	 ( 341) minutes.
    SCT capabilities: 	       (0x003f)	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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
      1 Raw_Read_Error_Rate     POSR-K   100   100   051    -    81
      2 Throughput_Performance  -OS--K   252   252   000    -    0
      3 Spin_Up_Time            PO---K   066   066   025    -    10417
      4 Start_Stop_Count        -O--CK   095   095   000    -    5617
      5 Reallocated_Sector_Ct   PO--CK   252   252   010    -    0
      7 Seek_Error_Rate         -OSR-K   252   252   051    -    0
      8 Seek_Time_Performance   --S--K   252   252   015    -    0
      9 Power_On_Hours          -O--CK   100   100   000    -    13145
     10 Spin_Retry_Count        -O--CK   252   252   051    -    0
     11 Calibration_Retry_Count -O--CK   252   252   000    -    0
     12 Power_Cycle_Count       -O--CK   098   098   000    -    2756
    181 Program_Fail_Cnt_Total  -O---K   093   093   000    -    166529546
    191 G-Sense_Error_Rate      -O---K   100   100   000    -    17
    192 Power-Off_Retract_Count -O---K   252   252   000    -    0
    194 Temperature_Celsius     -O----   064   052   000    -    34 (Min/Max 11/48)
    195 Hardware_ECC_Recovered  -O-RCK   100   100   000    -    0
    196 Reallocated_Event_Count -O--CK   252   252   000    -    0
    197 Current_Pending_Sector  -O--CK   252   252   000    -    0
    198 Offline_Uncorrectable   ----CK   252   252   000    -    0
    199 UDMA_CRC_Error_Count    -OS-CK   200   200   000    -    0
    200 Multi_Zone_Error_Rate   -O-R-K   100   100   000    -    10786
    223 Load_Retry_Count        -O--CK   252   252   000    -    0
    225 Load_Cycle_Count        -O--CK   100   100   000    -    5684
                                ||||||_ K auto-keep
                                |||||__ C event count
                                ||||___ R error rate
                                |||____ S speed/performance
                                ||_____ O updated online
                                |______ P prefailure warning
    
    General Purpose Log Directory Version 1
    SMART           Log Directory Version 1 [multi-sector log support]
    Address    Access  R/W   Size  Description
    0x00       GPL,SL  R/O      1  Log Directory
    0x01           SL  R/O      1  Summary SMART error log
    0x02           SL  R/O      2  Comprehensive SMART error log
    0x03       GPL     R/O      2  Ext. Comprehensive SMART error log
    0x06           SL  R/O      1  SMART self-test log
    0x07       GPL     R/O      2  Extended self-test log
    0x08       GPL     R/O      2  Power Conditions log
    0x09           SL  R/W      1  Selective self-test log
    0x10       GPL     R/O      1  SATA NCQ Queued Error log
    0x11       GPL     R/O      1  SATA Phy Event Counters log
    0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
    0xe0       GPL,SL  R/W      1  SCT Command/Status
    0xe1       GPL,SL  R/W      1  SCT Data Transfer
    
    SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
    Device Error Count: 30 (device log contains only the most recent 8 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 30 [5] occurred at disk power-on lifetime: 5289 hours (220 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 COUNT  LBA_48  LH LM LL DV DC
      -- -- -- == -- == == == -- -- -- -- --
      10 -- 51 00 b8 00 00 e9 e0 88 a0 e0 00  Error: IDNF 184 sectors at LBA = 0xe9e088a0 = 3923806368
    
      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
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      35 00 00 00 b8 00 00 e9 e0 88 a0 e0 00     00:00:10.593  WRITE DMA EXT
      25 00 00 00 01 00 00 00 00 00 00 e0 00     00:00:10.593  READ DMA EXT
      ef 00 02 00 00 00 00 00 00 00 00 a0 00     00:00:10.593  SET FEATURES [Enable write cache]
      f5 00 00 00 00 00 00 00 00 00 00 a0 00     00:00:10.593  SECURITY FREEZE LOCK
      ef 00 66 00 00 00 00 00 00 00 00 a0 00     00:00:10.593  SET FEATURES [Disable revert defaults]
    
    Error 29 [4] occurred at disk power-on lifetime: 5287 hours (220 days + 7 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
      -- -- -- == -- == == == -- -- -- -- --
      10 -- 51 00 b8 00 00 e9 e0 88 a0 e0 00  Error: IDNF 184 sectors at LBA = 0xe9e088a0 = 3923806368
    
      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
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      35 00 00 00 b8 00 00 e9 e0 88 a0 e0 00     00:00:10.200  WRITE DMA EXT
      25 00 00 00 01 00 00 00 00 00 00 e0 00     00:00:10.200  READ DMA EXT
      ef 00 02 00 00 00 00 00 00 00 00 a0 00     00:00:10.200  SET FEATURES [Enable write cache]
      f5 00 00 00 00 00 00 00 00 00 00 a0 00     00:00:10.200  SECURITY FREEZE LOCK
      ef 00 66 00 00 00 00 00 00 00 00 a0 00     00:00:10.200  SET FEATURES [Disable revert defaults]
    
    Error 28 [3] occurred at disk power-on lifetime: 5281 hours (220 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
      -- -- -- == -- == == == -- -- -- -- --
      10 -- 51 00 b8 00 00 e9 e0 88 a0 e0 00  Error: IDNF 184 sectors at LBA = 0xe9e088a0 = 3923806368
    
      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
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      35 00 00 00 b8 00 00 e9 e0 88 a0 e0 00     00:00:19.667  WRITE DMA EXT
      25 00 00 00 01 00 00 00 00 00 00 e0 00     00:00:19.667  READ DMA EXT
      25 00 00 01 00 00 00 53 1e ba 32 e0 00     00:00:19.666  READ DMA EXT
      25 00 00 01 00 00 00 53 1e b9 32 e0 00     00:00:19.666  READ DMA EXT
      25 00 00 01 00 00 00 53 1e b8 32 e0 00     00:00:19.666  READ DMA EXT
    
    Error 27 [2] occurred at disk power-on lifetime: 5275 hours (219 days + 19 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
      -- -- -- == -- == == == -- -- -- -- --
      10 -- 51 00 b8 00 00 e9 e0 88 a0 e0 00  Error: IDNF 184 sectors at LBA = 0xe9e088a0 = 3923806368
    
      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
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      35 00 00 00 b8 00 00 e9 e0 88 a0 e0 00     00:00:20.064  WRITE DMA EXT
      25 00 00 00 01 00 00 00 00 00 00 e0 00     00:00:20.064  READ DMA EXT
      25 00 00 01 00 00 00 7b 02 85 32 e0 00     00:00:20.064  READ DMA EXT
      25 00 00 01 00 00 00 7b 02 84 32 e0 00     00:00:20.064  READ DMA EXT
      25 00 00 01 00 00 00 84 0c 1d 8a e0 00     00:00:20.063  READ DMA EXT
    
    Error 26 [1] occurred at disk power-on lifetime: 5266 hours (219 days + 10 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
      -- -- -- == -- == == == -- -- -- -- --
      10 -- 51 00 b8 00 00 e9 e0 88 a0 e0 00  Error: IDNF 184 sectors at LBA = 0xe9e088a0 = 3923806368
    
      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
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      35 00 00 00 b8 00 00 e9 e0 88 a0 e0 00     00:00:20.088  WRITE DMA EXT
      25 00 00 00 01 00 00 00 00 00 00 e0 00     00:00:20.088  READ DMA EXT
      25 00 00 01 00 00 00 2d 54 22 9a e0 00     00:00:20.088  READ DMA EXT
      25 00 00 01 00 00 00 e5 14 2d da e0 00     00:00:20.088  READ DMA EXT
      25 00 00 01 00 00 00 e5 3f 47 aa e0 00     00:00:20.087  READ DMA EXT
    
    Error 25 [0] occurred at disk power-on lifetime: 5256 hours (219 days + 0 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
      -- -- -- == -- == == == -- -- -- -- --
      10 -- 51 00 b8 00 00 e9 e0 88 a0 e0 00  Error: IDNF 184 sectors at LBA = 0xe9e088a0 = 3923806368
    
      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
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      35 00 00 00 b8 00 00 e9 e0 88 a0 e0 00     00:00:00.440  WRITE DMA EXT
      25 00 00 00 01 00 00 00 00 00 00 e0 00     00:00:00.440  READ DMA EXT
      25 00 00 01 00 00 00 de fc 72 2a e0 00     00:00:00.440  READ DMA EXT
      25 00 00 01 00 00 00 de fc 71 2a e0 00     00:00:00.440  READ DMA EXT
      25 00 00 01 00 00 00 14 6a 10 ca e0 00     00:00:00.440  READ DMA EXT
    
    Error 24 [7] occurred at disk power-on lifetime: 5244 hours (218 days + 12 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
      -- -- -- == -- == == == -- -- -- -- --
      10 -- 51 00 b8 00 00 e9 e0 88 a0 e0 00  Error: IDNF 184 sectors at LBA = 0xe9e088a0 = 3923806368
    
      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
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      35 00 00 00 b8 00 00 e9 e0 88 a0 e0 00     00:00:07.078  WRITE DMA EXT
      25 00 00 00 01 00 00 00 00 00 00 e0 00     00:00:07.078  READ DMA EXT
      25 00 00 01 00 00 00 2f 96 6e b2 e0 00     00:00:07.078  READ DMA EXT
      25 00 00 01 00 00 00 2f 96 6d b2 e0 00     00:00:07.078  READ DMA EXT
      25 00 00 01 00 00 00 2f 96 6c b2 e0 00     00:00:07.077  READ DMA EXT
    
    Error 23 [6] occurred at disk power-on lifetime: 5228 hours (217 days + 20 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
      -- -- -- == -- == == == -- -- -- -- --
      10 -- 51 00 b8 00 00 e9 e0 88 a0 e0 00  Error: IDNF 184 sectors at LBA = 0xe9e088a0 = 3923806368
    
      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
      -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
      35 00 00 00 b8 00 00 e9 e0 88 a0 e0 00     00:00:08.749  WRITE DMA EXT
      25 00 00 00 01 00 00 00 00 00 00 e0 00     00:00:08.749  READ DMA EXT
      ef 00 02 00 00 00 00 00 00 00 00 a0 00     00:00:08.749  SET FEATURES [Enable write cache]
      f5 00 00 00 00 00 00 00 00 00 00 a0 00     00:00:08.748  SECURITY FREEZE LOCK
      ef 00 66 00 00 00 00 00 00 00 00 a0 00     00:00:08.748  SET FEATURES [Disable revert defaults]
    
    SMART Extended Self-test Log Version: 1 (2 sectors)
    No self-tests have been logged.  [To run self-tests, use: smartctl -t]
    
    SMART Selective self-test log data structure revision number 0
    Note: revision number not 1 implies that no selective self-test has ever been run
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Completed [00% left] (0-65535)
        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:                  2
    SCT Version (vendor specific):       256 (0x0100)
    SCT Support Level:                   1
    Device State:                        Active (0)
    Current Temperature:                    33 Celsius
    Power Cycle Min/Max Temperature:     22/39 Celsius
    Lifetime    Min/Max Temperature:     11/54 Celsius
    Under/Over Temperature Limit Count:   0/0
    
    SCT Temperature History Version:     2
    Temperature Sampling Period:         5 minutes
    Temperature Logging Interval:        5 minutes
    Min/Max recommended Temperature:     -5/80 Celsius
    Min/Max Temperature Limit:           -10/85 Celsius
    Temperature History Size (Index):    128 (64)
    
    Index    Estimated Time   Temperature Celsius
      65    2017-11-16 06:25    33  **************
     ...    ..( 11 skipped).    ..  **************
      77    2017-11-16 07:25    33  **************
      78    2017-11-16 07:30    34  ***************
      79    2017-11-16 07:35    33  **************
     ...    ..( 10 skipped).    ..  **************
      90    2017-11-16 08:30    33  **************
      91    2017-11-16 08:35    34  ***************
      92    2017-11-16 08:40    34  ***************
      93    2017-11-16 08:45    33  **************
     ...    ..( 37 skipped).    ..  **************
       3    2017-11-16 11:55    33  **************
       4    2017-11-16 12:00    34  ***************
       5    2017-11-16 12:05    33  **************
     ...    ..(  3 skipped).    ..  **************
       9    2017-11-16 12:25    33  **************
      10    2017-11-16 12:30    34  ***************
     ...    ..( 28 skipped).    ..  ***************
      39    2017-11-16 14:55    34  ***************
      40    2017-11-16 15:00    35  ****************
      41    2017-11-16 15:05    34  ***************
     ...    ..( 22 skipped).    ..  ***************
      64    2017-11-16 17:00    34  ***************
    
    SCT Error Recovery Control:
               Read: Disabled
              Write: Disabled
    
    Device Statistics (GP/SMART Log 0x04) not supported
    
    SATA Phy Event Counters (GP Log 0x11)
    ID      Size     Value  Description
    0x0001  4            0  Command failed due to ICRC error
    0x0002  4            0  R_ERR response for data FIS
    0x0003  4            0  R_ERR response for device-to-host data FIS
    0x0004  4            0  R_ERR response for host-to-device data FIS
    0x0005  4            0  R_ERR response for non-data FIS
    0x0006  4            0  R_ERR response for device-to-host non-data FIS
    0x0007  4            0  R_ERR response for host-to-device non-data FIS
    0x0008  4            0  Device-to-host non-data FIS retries
    0x0009  4            1  Transition from drive PhyRdy to drive PhyNRdy
    0x000a  4            1  Device-to-host register FISes sent due to a COMRESET
    0x000b  4            0  CRC errors within host-to-device FIS
    0x000d  4            0  Non-CRC errors within host-to-device FIS
    0x000f  4            0  R_ERR response for host-to-device data FIS, CRC
    0x0010  4            0  R_ERR response for host-to-device data FIS, non-CRC
    0x0012  4            0  R_ERR response for host-to-device non-data FIS, CRC
    0x0013  4            0  R_ERR response for host-to-device non-data FIS, non-CRC
    0x8e00  4            0  Vendor specific
    0x8e01  4            0  Vendor specific
    0x8e02  4            0  Vendor specific
    0x8e03  4            0  Vendor specific
    0x8e04  4            0  Vendor specific
    0x8e05  4            0  Vendor specific
    0x8e06  4            0  Vendor specific
    0x8e07  4            0  Vendor specific
    0x8e08  4            0  Vendor specific
    0x8e09  4            0  Vendor specific
    0x8e0a  4            0  Vendor specific
    0x8e0b  4            0  Vendor specific
    0x8e0c  4            0  Vendor specific
    0x8e0d  4            0  Vendor specific
    0x8e0e  4            0  Vendor specific
    0x8e0f  4            0  Vendor specific
    0x8e10  4            0  Vendor specific
    0x8e11  4            0  Vendor specific
    
    

    Tutaj screen z atrybutów 

     

    0ab265f336b6feccmed.jpg

×
×
  • Dodaj nową pozycję...