The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I own a NAS that has a total capacity of 6TB. More than enough for my business needs.
Till today I've been using a 3TB HDD as backup and it worked perfectly... versions... all OK, but of course I'm running out of space.
Would you recommend the Seagate STEL6000200 HDD?
It's 6TB of capacity and the USB3.0 port seems what I need.
Seagate's got such a bad reputation is recent years decades I wouldn't take one even if given to me for free. And that's actually happened - I was given a system that had a set of mirrored Seagate drives - one was already dead, and the other failed within the following month.
All Seagate drives I've ever purchased are dead. I've retired functional drives from other companies because they just got too small, not because they stopped working.
IMO: If you're going to insist on Seagate as a backup drive, then back up in pairs, at least.
Personally I haven't had the bad experience of Seagate, the opposite actually.
Their average fail rate is about the same as any other manufacturer. According to (some fairly old) statistics from google, who buys a lot of hard drives from all manufacturers.
But what all manufacturers have in common is that they very often have systematic errors, so if one drive fails, usually most drives from the same batch or even model fails at the same time.
Therefore my recommendation is to buy a Synology diskstation or a Qnap or something similar, and fill it up with disks from different manufacturers.
That said, one should still check out current statistics[^], and you should NOT buy Seagate ST4000DMxxx, and the stats for certain Western digital disks doesn't look to shiny either.
At the moment it looks like Hitachi is the way to go. (which I personally have had extremely bad experience with )
had one client with a Synology box (admittedly low end) stacked with 2 mirrored WD drives,
less than a year in started reporting SMART fails on both drives. Went through the return/replace of drives, but problems kept coming back. I took a look at the forums on Synology's own website, seemed others with sometimes even days old new WD's having problems. Of course Synology's reply "update the software, rebuild the RAID, if that fails change the drives" (just like MS, if the upgrade fails, reinstall). WD - drives are fine but we'll give you another [often refirbished] just to be sure.
To save the client spending on more drives (now after warranty) I took the supposed worst of the current 2 drives and threw it in a desktop PC, full reformatted it (many hours), and had it duplicate what they were putting on the NAS (from original sources of course) - been flawless in both work and regular SMART tests while the 2nd (now single drive) still in the NAS is picking up more errors. (Moving that 2nd drive a job for another day.)
1. check compatibility NAS to drives beyond what manufacturer claims - check forums etc
2. For sure: if it's Synology NAS avoid WD drives, not sure whos fault but it's not a happy mix.
Signature ready for installation. Please Reboot now.
I'd have to say my experience with Seagate drives is fine: my NAS has 4 * 4TB Seagate drives (ST4000DM000-1F2168) organised as RAID 5 that have run 24/7 since early 2015 and - so far - no problems at all.
My USB (air gapped) image backup drives are also Seagate and are all fine as well - I can't remember when I got them, but they well and truly predate the Seagate NAS.
In fact, the only HDD failures I've had in the last 15 years have all been Maxtor drives of various sizes.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
Actually I am totally uninterested (not disinterested as is now commonly used). However there was a time when grammar like in the above message title would alert one to a scam. Now I'm not so sure. It could be from Apple. Who knows, who cares.
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
AIUI, a chess engine uses some sort of minmax algorithm, but a minmax algorithm would search for a path that guarantees the least worst option - and since a chess engine assigns integral points for pieces, it seems that the score should be some integral value. What's going on here? (I presume that there must be a few folks here that are in both the set of chess players and the set of folks who do artificial intelligence.)
Usually a Mobility score is also part of the equation, with a non-integral weight. If you're interpolating between game phases (using different scoring for the opening, midgame and endgame and interpolating to avoid sharp discontinuities at phase transitions) of course many scores will not be integral.
(I'm going to use the Stockfish engine as example. I don't know how other engines do this, but it could be the same.)
Short answer: Stockfish does output an integral score but your chess interface divides it by 100.
Internally, Stockfish does have an integral value as score. This value is rather big (looking at just the piece values[^], the value of a pawn in the midgame is 171 and the value of the queen is 2526) and it's also not just the piece values, there is also a bunch of bonuses and penalties[^] to adjust this value.
When Stockfish tells you how it evaluates a position, it won't give you its internal value, but it will give you the score in "centipawns"[^]. (1 pawn = 100 centipawns) So if Stockfish's raw output says "200", it means that you have an advantage of 2 pawns.
But even that number is still provided by Stockfish as an integer. Your chess interface, however, may decide to show you the evaluation in pawns rather than centipawns, thus dividing Stockfish's centipawn evaluation by 100.
The quick brown ProgramFOX jumps right over the Lazy<Dog>.
@randor had mentioned that I could take a look at the dump file to get more info.
However, at the time the DMP file got delete so I was unable to go further.
My machine rebooted and this time I still have the 997MB DMP file (which is crazy) and I opened it up with WinDbg.
Here's what I see...
I know it's a lot of info but just thought it might be interesting.
You can see that it looks like it is the PCI.sys driver that failed.
Reason I'm Mentioning This
I mention this out of interest and to see if anyone else has had a situation with their Win10 PC rebooting itself like this while not in use.
Just a discussion, not looking for an answer. I know better than to believe we would ever be able to run a cryptic thing like this down. This is the Way of Windows, a magical land where the magic often fails.
A driver has failed to complete a power IRP within a specific time.
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe680b6184040, The thread currently holding on to the Pnp lock.
Arg4: ffff87012fc7d910, nt!TRIAGE_9F_PNP on Win7 and higher
Implicit thread is now ffffe680`b6184040
SYSTEM_PRODUCT_NAME: Satellite S55t-B
BIOS_VENDOR: INSYDE Corp.
BASEBOARD_MANUFACTURER: Type2 - Board Vendor Name1
BASEBOARD_PRODUCT: Type2 - Board Product Name1
BASEBOARD_VERSION: Type2 - Board Version
DRVPOWERSTATE_SUBCODE: 4IMAGE_NAME: pci.sys
FAULTING_MODULE: fffff80b9ac70000 pci
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
ANALYSIS_SESSION_TIME: 03-17-2018 12:04:23.0467
ANALYSIS_VERSION: 10.0.17074.1002 amd64fre
ffff8701`2fc7d8d8 fffff800`3608fbc4 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffe680`b6184040 : nt!KeBugCheckEx
ffff8701`2fc7d8e0 fffff800`362c6916 : ffff8701`2fc7db10 ffffd680`92cce180 ffffd680`92cce180 000000e6`7551f100 : nt!PnpBugcheckPowerTimeout+0x60
ffff8701`2fc7d940 fffff800`35f58923 : ffffd680`92cce180 00000000`00000000 ffff8701`2fc7db18 00000000`00000000 : nt!PopBuildDeviceNotifyListWatchdog+0x16
ffff8701`2fc7d970 fffff800`35f599bd : 00000000`00000018 00000000`00000000 00000000`00252ac4 ffffd680`92cce180 : nt!KiProcessExpiredTimerList+0x153
ffff8701`2fc7da60 fffff800`3600cdfa : 00000000`00000001 ffffd680`92cce180 00000000`00000000 ffffd680`92cdc200 : nt!KiRetireDpcList+0x43d
ffff8701`2fc7dc60 00000000`00000000 : ffff8701`2fc7e000 ffff8701`2fc78000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: .thread ; .cxr ; kb
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OSBUILD_TIMESTAMP: 2018-03-01 00:36:55
Last Visit: 31-Dec-99 18:00 Last Update: 18-Mar-18 19:54