monza

super keen to hear any updates on this please! I've just started to explore Frigate and was hoping to use my 8th Gen iGPU. I had it setup and 'working' but abandoned it due to constant errors logged. Ive reverted to CPU decode for detect streams, VAAPI for record streams. BUT i really would like to utilise that iGPU more 2025-12-21 10:36:37.448671296 [2025-12-21 10:36:37] frigate.video ERROR : cam1_garage_left: Unable to read frames from ffmpeg process. 2025-12-21 10:36:37.448980304 [2025-12-21 10:36:37] frigate.video ERROR : cam1_garage_left: ffmpeg process is not running. exiting capture thread... 2025-12-21 10:36:41.491373632 [2025-12-21 10:36:41] watchdog.cam1_garage_left ERROR : Ffmpeg process crashed unexpectedly for cam1_garage_left. 2025-12-21 10:36:41.491559377 [2025-12-21 10:36:41] watchdog.cam1_garage_left ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2025-12-21 10:36:41.491784547 [2025-12-21 10:36:41] ffmpeg.cam1_garage_left.detect ERROR : [AVHWFramesContext @ 0x1542bc07d940] Failed to sync surface 0x12: 1 (operation failed). 2025-12-21 10:36:41.491956202 [2025-12-21 10:36:41] ffmpeg.cam1_garage_left.detect ERROR : [hwdownload @ 0x1542cc003980] Failed to download frame: -5. 2025-12-21 10:36:41.492097315 [2025-12-21 10:36:41] ffmpeg.cam1_garage_left.detect ERROR : [vf#0:0 @ 0x557742939240] Error while filtering: Input/output error 2025-12-21 10:36:41.492225410 [2025-12-21 10:36:41] ffmpeg.cam1_garage_left.detect ERROR : [vf#0:0 @ 0x557742939240] Task finished with error code: -5 (Input/output error) 2025-12-21 10:36:41.492365843 [2025-12-21 10:36:41] ffmpeg.cam1_garage_left.detect ERROR : [vf#0:0 @ 0x557742939240] Terminating thread with return code -5 (Input/output error) 2025-12-21 10:36:41.492525800 [2025-12-21 10:36:41] watchdog.cam1_garage_left INFO : Restarting ffmpeg...

literally came to this support thread to +1 this too. I think it is a fantastic feature that would help for containers. I don't need bleeding edge, i need stability. So in my use case, a delay of x days helps with that. Yes, I also use the appdata backup plugin so can always revert - but id rather not have to do that if its as easy as just waiting for an update to be 'stable' prior to updating the container. thank you to the original devs for this plugin

stumbled upon this and i feel as though i've got very similar questions as i work my way through the complex journey of understanding cloudflare, ngnix, VPS etc etc. Kudos for the well laid out post, its a shame there hasn't been a reply as I would have been keen to see how you progressed with your setup and if you persisted or changed things up.

Hi.. i am crossing this same bridge and googling like a madman. If there is any way you still have the perl script then would you mind providing a copy of it please? 100% understand if that is not possible though, so no worries either way. thanks all

thank you both for your assistance

ok great, that sounds like what I had thought would/should happen :) I think I'm set now, once ive get the physical data disks moved over, ill then assign the parity drive LAST. Then i can setup my user shares again which ill likely replicate based on my 'old' server config - hoping that is straight forward too and doesn't mess anything up? e.g i have a "Movies" user share that spanned disks 1, 2 and 3. The folder structure on each of those disks was: /Movies --> 01BluRay --> 02UHD4K So I can just go ahead and create the "Movies" user share on TowerB_7 and it wouldn't do anything funky even though that Movies 'folder' exists on the data disks?

thank you JorgeB. Bonus question, is there anything special I need to do with my existing Parity disk from TowerA_6 to REPURPOSE it for use as a data disk in TowerB_7? If I just moved that disk to TowerB_7 and assigned it as a data disk slot, would unraid just format it and have it ready for me to use it? For some reason in my head i am thinking it would cause some issues as TowerB_7 would see it as as being previously used for Parity and that might cause some issues. again, thank you for the prompt response Jorge, i feel a lot happier moving into this now.

hi all, Been using Unraid since around 2010 and its been rock solid. Just need to ping a few things off the more intelligent people out there as I don't really do major changes to hardware often and there is only so much reading you can do in preparation, especially when moving to a new major version. Goal: Move my 5 unraid data disks from my existing Unraid 6.12 server (TowerA_6) to a new server running Unraid 7 (TowerB_7). I would rather NOT copy the data to "new" disks as this involves me first having to BUY a lot of large (14+ TB) drives. So my goal is to MOVE the physical disks over to the new server. I have a PRO licence on my TowerA_6 server. I currently have a TRIAL Unraid 7 on a fresh USB as I intend to setup dockers and apps from fresh to tidy up some old legacy stuff. I will then MIGRATE my PRO licence to the new server. So for all intents and purposes, lets say TowerB_7 is a fresh Unraid 7 install with nothing else, no parity and no data disks in it. Questions: 1) If I take a few data disks (e.g Disk1 and Disk2) from TowerA_6 and put those into TowerB_7. Then fire up unraid, I understand these will show as unmounted/unallocated. If i setup the new Unraid 7 array (4 devices) with NO parity disk assigned, but just assign the two disks as Disk1 and Disk2 - will i be able to start the array without unraid wanting to format the disks? 2) Assuming the answer to the above is "YES" (the data will be preserved and Disk1 and Disk2 will NOT be formatted), if I now allocated a NEW precleared disk as parity to the array, again will the data on Disk1 and Disk2 remain preserved? Is there any specific check box or settings I need to be aware of to ensure no data is lost? 3) Can I then just expand the array size and again physically move over data Disk3, Disk4 and Disk5 from TowerA_6 to TowerB_7 without any loss of data? VERY IMPORTANT - would I first need to unallocated the PARITY drive on TowerB_7 before taking this step? (would Unraid think it needs to clear Disk3, Disk4 and Disk5 due to an invalid parity?) Notes: I will only ever run 1 parity drive All disks from TowerA_6 are in XFS format I will continue to use XFS when i setup the new array on TowerB_7 (specifically when i expand the array) I'm sorry as some of this is likely REALLY stupid but i need to make sure im not about to make some stupid mistake and delete a bunch of data! Appreciate any help and assistance you can provide.

thanks... this post and the 3.3V mod saved me after the third SAS drive (Seagate ST10000NM0096) I attempted to use didn't power up. The first two SAS drives I used (different make/model) worked fine without any mod needed. Hope that helps someone in the future!

Hi Andy. Just wondered if you managed to resolve this issue? I am about to stick a DELL OEM Intel x540-T2 into my unraid server and am looking for any hints and tips - hence I stumbled on this forum post. Any info would be greatly appreciated. FWIW, my card has been tested in a Windows 11 box (using driver package 26.50, driver v4.1.197.0) and has firmware 18.0.0 currently installed. Using the Dell DUP tool, it tells me I can upgrade to fw 20.0.16...but have not done so yet as I can get a 10G connection from the card to my 10G switch. I might update firmware if i run into issues or find something that tells me i need to upgrade it. thanks

I've been toying with getting this case for a number of weeks / months and have been keeping a close eye on this thread.. Thanks for taking the time to report your findings and for posting the photos.

All three look okay. The drive temps are warm though. In the low to mid 40s. That is okay but I prefer to see them in the 30s. You might consider a little extra cooling. The ECC recovered attribute is a little unsettling, but modern drives store data with redundancy acknowledging that media related errors will exist and that the redundancy is used in the normal usage use case to detect and correct such errors. Seagate it's very upfront reporting this, whereas other drives either mask this activity our have it occur to a lesser extent. My slight personal bias against Seagate not withstanding, these drives have successfully passed the preclear. I suggest, as with any drive, that you continue to monitor the smart reports over time. thanks so much for looking at the logs. Agreed - the temps are a little hotter than ideal, but I livve in Australia and the ambient here was about 33 when i ran the preclear. I am actually looking to run the 6TB drives in a new enclosure and am currently investigating the best options for what my next unraid build will be. cheers

Hi folks, Can anyone take a look at the attached logs for preclear on three 6TB Seagate drives (ST6000DX000-1H217Z) and let me know if there is anything of concern please? There was some weird stuff about error rates which i didn't quite understand and thought may have been a bit suspect. I can post the _finish and _start logs if needed. many thanks p.s preclear on three 6TB disks simultaneously took a whopping 55hrs and 38mins preclear_rpt_Z4D0D6Y6_2015-03-27.txt preclear_rpt_Z4D0E7T7_2015-03-27.txt preclear_rpt_Z4D0711K_2015-03-27.txt

thanks once again for the reply - ive had a little more time to think and wanted to see if my hairbrained scheme would work! I started a new thread here : http://lime-technology.com/forum/index.php?topic=31500.0 cheers

haha all makes sense now! Just wondered if you had any more info or experience with the PICO PSU's? I was keen to try and get the two servers running quieter and sapping a little less juice to save on the old leccy. Only thing i was a little confuzzled about was which particular wattage/version of the PICO (or generic make) would meet my needs? The 4tb drives i have are all Hitachi 7K4000 (HDS724040ALE640) which according to the spec sheet [http://www.hgst.com/tech/techlib.nsf/techdocs/3C330019E6ED04A48825797700626F0D/$file/DS7K4000_ds.pdf] pull 2A each at start up. If i am reading the microserver spec sheet correctly [http://h18000.www1.hp.com/products/quickspecs/productbulletin.html#spectype=worldwide&type=html&docid=13716] then i think it needs 2A itself. Therefore I need something which can handle 12A for the 6 drives plus 2A for the microserver = 14A? (sorry this is a bit new to me so if im way off then you will have to excuse my ignorance!) Would you happen to know if any of these would be able to handle the peak startup load of my N54L/N36L when each is stuffed with 6 x 4tb Hitachi drives? Again, i think they can deliver 16A (200W / 12V) ? Z2-ATX-200 Genuine PICO Brand [http://www.pico-box.com/products.html] 160W/200W peak, 12V input DC-DC ATX Power Supply 24pin DC-DC ATX PSU 0-160 Watts, 12V input DC input PIN size of 5.5mm/2.5mm AVX Tantalum capacitors, USA Z3-ATX-200 Genuine Pico Brand [http://www.pico-box.com/products.html] 160W/200W peak, 16-24V input DC-DC ATX Power Supply 24pin DC-DC ATX PSU 0-160 Watts, 16-24V wide-range input DC input PIN size of 5.5mm/2.5mm AVX Tantalum capacitors, USA eBay item [http://www.ebay.com.au/itm/20-pin-DC-DC-12V-ATX-200W-Power-Supply-for-Mini-PC-Mini-ITX-/110960302536?pt=AU_Components&hash=item19d5bfd9c8&_uhb=1] 20 pin DC/DC 12V ATX 200W Power Supply for Mini PC Mini-ITX DC Input: 12V Power Output : 200W Input Current: Max. 15A Plus I need a suitable 200W power brick? Again not sure which ones I can use which have the correct specs to power the supplies? Really confused here, what wattage, voltage and amp spec would i need? I think whatever I end up getting I am going to have to be really careful with clearance to ensure the power supply clears the other components around the ATX connector on the microserver board - some careful measuring is gonna have to occur before buying anything. cheers and sorry for all the n00b questions!

As you mention, if the N36L can handle the 4tb drives then I may venture down the path of running two unraid servers and just spread the load over the two. I think that would be the most logical and straightforward way of using the spare server and drives (slowly replacing the 2tb drives in the N36L as an when needed) I was just thrown off as when i had looked into this last year I had read that the N36L couldn't handle 4tb drives - i think this is just limited to the boot drive not being able to handle anything larger than 2tb though. I'll give it a whirl and see how i get on - thanks for the reply

Hi, Its been a while since i was on the forums simply because my current Unraid setup (running 24/7/365) has been rock solid for over a year. Alas I come seeking some advice on how to upgrade/expand my setup. Current setup: HP Microserver N54L running unraid 5.0 RC11 PLUS (still need to up grade to the non-rc release at some stage - but as they say... "if it aint broke...dont try and fix it") 4 x 4tb drives in front bays 2 x 2tb drives in optical drive space (one utilising the esata port at the back, the other using the ODD sata port - running the BIOS mod which allows me to do this) I had previously run the older N36L microserver with 6 x 2tb drives but ran out of room and thus upgraded to the N54L for the 4tb drive support - happy days. Well as most of us are aware, the upgrade bug has kicked in as I am almost out of room on my N54L and need to look for additional storage options! So my slightly hair brained scheme was to try and utilise the unused N36L as additional drive storage to expand my N54L unraid array (after upgrading my PLUS key to the PRO key allowing me to use 24 drives in total). I guess my reasoning for trying this option first is that I already have 6 x 2tb drives sitting doing nothing as well as the actual N36L server doing a rather fine impersonation of a paperweight. So has anyone done this? Is it even possible? Any guidance or pointers would be really appreciated along with any additional hardware I would require (add in cards, cables etc...). Id love to just have the two servers sitting side by side (or stacked) providing me the necessary storage space for at least another year. I guess id be trying to use the N36L as a slightly over glorified external sata enclosure? many thanks for your time and input! (p.s if its any use at all I have a spare Adaptec 1430SA card laying about also doing nothing....)

does anyone have a guide to getting the CPU temperature to work from the unMenu (system info > CPU Info) please?

Hi, can you post a link to the exact file you used to patch the bios please? thanks

ok, i upgraded to 5.0 B9 today and still having the same issues where CPU temp isnt displayed and no sensors are detected... is there something which needs to be downloaded for this to work on the N36L ? thanks

thanks for the quick reply. im on 4.7 at the moment so probably the reason why its not working then. I did initially attempt to run 5.0 beta 8c but was getting way to many issues regarding the web admin page hanging when setting user shares... so i reverted to 4.7 just to get some testing done on my new toy mind me asking you to elaborate on the "probe" bit though - im not entirely sure what you meant by that? cheers

anyone able to get the CPU temp to display when using unmenu (system info --> CPU info), or speed fan control and info ? i ran sensors-detect and got : -bash: /usr/sbin/sensors-detect: /usr/bin/perl: bad interpreter: No such file or directory then pwmconfig and got: /usr/sbin/pwmconfig: No sensors found! (modprobe sensor modules?) interested to know if anyone had any luck with sensors on this microserver yet? thanks

found the answer to my own question! http://forum.wegotserved.com/index.php/topic/16427-whs-on-hp-proliant-microserver/page__view__findpost__p__104525 Hacked "new" BIOS details here: http://forum.wegotserved.com/index.php/topic/16427-whs-on-hp-proliant-microserver/page__view__findpost__p__104539 but beware I read mixed results and many people say that the latest hacked bios is missing some options?!? Think it may just be best to use the "old russian" hacked BIOS.

been reading lots of info (thanks to the great posts and guides!) Just a quick question... am i reading the post mentioned below correctly and now understand that we dont need the russian hacked bios as the official HP bios supports the feature to get the full speed from the motherboard sata port (used for the ODD) ? http://forum.wegotserved.com/index.php/topic/16427-whs-on-hp-proliant-microserver/page__view__findpost__p__104300 thanks!

Just wanted someone to quickly check my preclear results from a WD EARS drive (with jumper over 7 & 8 ) looks ok to me (this is my first time using pre-clear)... but if anyone can see anything strange then please let me know. I did notice this (see attached log): Nov 28 18:14:28 Tower kernel: end_request: I/O error, dev sdg, sector 2563489960 Nov 28 18:14:28 Tower kernel: Buffer I/O error on device sdg, logical block 320436245 This is the summary: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Home page is http://smartmontools.sourceforge.net/ Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: === START OF INFORMATION SECTION === Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Device Model: WDC WD20EARS-00MVWB0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Serial Number: WD-WMAZA1634XXX Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Firmware Version: 51.0AB51 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: User Capacity: 2,000,398,934,016 bytes Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Device is: Not in smartctl database [for details use: -P showall] Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ATA Version is: 8 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ATA Standard is: Exact ATA specification draft version not indicated Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Local Time is: Mon Nov 29 23:05:05 2010 GMT Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART support is: Available - device has SMART capability. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART support is: Enabled Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: === START OF READ SMART DATA SECTION === Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART overall-health self-assessment test result: PASSED Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: General SMART Values: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Offline data collection status: (0x84)^IOffline data collection activity Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Iwas suspended by an interrupting command from host. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Self-test execution status: ( 0)^IThe previous self-test routine completed Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Iwithout error or no self-test has ever Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Ibeen run. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Total time to complete Offline Nov 29 23:05:05 Tower preclear_disk-finish[7312]: data collection: ^I^I (37500) seconds. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Offline data collection Nov 29 23:05:05 Tower preclear_disk-finish[7312]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IAuto Offline data collection on/off support. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISuspend Offline collection upon new Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Icommand. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IOffline surface scan supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISelf-test supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IConveyance Self-test supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISelective Self-test supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART capabilities: (0x0003)^ISaves SMART data before entering Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Ipower-saving mode. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISupports SMART auto save timer. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Error logging capability: (0x01)^IError logging supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IGeneral Purpose Logging supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Short self-test routine Nov 29 23:05:05 Tower preclear_disk-finish[7312]: recommended polling time: ^I ( 2) minutes. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Extended self-test routine Nov 29 23:05:05 Tower preclear_disk-finish[7312]: recommended polling time: ^I ( 255) minutes. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Conveyance self-test routine Nov 29 23:05:05 Tower preclear_disk-finish[7312]: recommended polling time: ^I ( 5) minutes. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SCT capabilities: ^I (0x3035)^ISCT Status supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISCT Feature Control supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISCT Data Table supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART Attributes Data Structure revision number: 16 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Vendor Specific SMART Attributes with Thresholds: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1125 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 10 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 33 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 15 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART Error Log Version: 1 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: No Errors Logged Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART Self-test log structure revision number 1 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART Selective self-test log data structure revision number 1 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 1 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 2 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 3 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 4 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 5 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Selective self-test flags (0x0): Nov 29 23:05:05 Tower preclear_disk-finish[7312]: After scanning selected spans, do NOT read-scan remainder of disk. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: If Selective self-test is pending on power-up, resume after 0 minute delay. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-diff[7325]: ============================================================================ Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Disk /dev/sdg has been successfully precleared Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Ran 1 preclear-disk cycle Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Using :Read block size = 8225280 Bytes Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Last Cycle's Pre Read Time : 8:10:46 (67 MB/s) Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Last Cycle's Zeroing time : 9:17:46 (59 MB/s) Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Last Cycle's Post Read Time : 16:21:09 (33 MB/s) Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Last Cycle's Total Time : 33:50:49 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Total Elapsed Time 33:50:49 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Disk Start Temperature: 15C Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Current Disk Temperature: 21C, Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: ============================================================================ Nov 29 23:05:05 Tower preclear_disk-diff[7325]: S.M.A.R.T. error count differences detected after pre-clear Nov 29 23:05:05 Tower preclear_disk-diff[7325]: note, some 'raw' values may change, but not be an indication of a problem Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 19,20c19,20 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < Offline data collection status: (0x80)^IOffline data collection activity Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < ^I^I^I^I^Iwas never started. Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > Offline data collection status: (0x84)^IOffline data collection activity Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > ^I^I^I^I^Iwas suspended by an interrupting command from host. Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 54c54 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 58c58 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 63c63 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 8 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 15 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 67c67 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: ============================================================================ Nov 29 23:05:05 Tower preclear_disk-diff[7325]: excerpt from full log is attached. thanks PreClear_Excerpt_from_syslog.txt