Jump to content
Covecube Inc.

PocketDemon

Members
  • Content Count

    56
  • Joined

  • Last visited

  • Days Won

    2

PocketDemon last won the day on April 2

PocketDemon had the most liked content!

About PocketDemon

  • Rank
    Advanced Member

Recent Profile Visitors

195 profile views
  1. The safest option would always be by booting into "safe mode with command prompt" & using a DOS/command line updater - however it depends how Seagate's s/w works; since it's reasonable to assume that the big manufacturers know what they're doing... ...though, if it's using something generic to unofficial update, I would only recommend going for the DOS/Command Prompt version. (I'm not saying that using unofficial s/w in Windows will go wrong of course, so I have flashed GFX cards in Windows a couple of times - but that was obviously me making a calculated risk about my own kit; not what I'd publicly recommend to anyone else.) So, taking my Samsung SSDs as an example, the update s/w is Windows based & so that's what I'd use... …& the same for CD/DVD/BR drives... …& for my LSI card... …&.. ...whereas for something like unofficially updating individual OROMs on motherboards then I would always go for the command prompt option - or, with unofficial BIOSes, via the flash within the BIOS/UFEI. Then, with something like unofficially flashing HDDs or SSDs, I would personally pull all of the drives other than a single drive that I was looking to update (& a USB drive or DVD/BR drive for a disk with the s/w on of course) & connect it directly to the motherboard - as it limits the potential for things to go horrendously wrong.
  2. Always a good idea to at consider new versions of s/w & f/w & drivers & whatnot. Yeah, whilst it's probably not necessary as (touch wood) everything's working fine, I spasmodically (every month or two) have a look at the changelogs for the betas - http://dl.covecube.com/DrivePoolWindows/beta/download/ & http://dl.covecube.com/ScannerWindows/beta/download/ (for the 2 things I use) - to see whether it looks to be worthwhile to move forward... …& it's easy to revert to the previous versions that I know worked were there to be any issue.
  3. Have you enabled showing hidden files in File Explorer, as stated in the wiki, as it's certainly there in mine?
  4. http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings
  5. I knew that there was some discussion about DP & drives clicking going back &, having had some sleep, just had a quick search - & it was actually covered again a week & a half ago. So, as said, something (DP) competing with (probably) your Windows' Power Options settings. Yeah, the thread doesn't explain why it was enabled by default btw - but it's something you could look at.
  6. if you're leaving it as disabled then I honestly don't know why you didn't stick with the LSI card... Obviously your choice though. Otherwise, I guess in theory you could split every cable & wire in LEDs (& almost certainly resistors) part way along - but I've never seen any cables that natively have them... ...so the normal usage is with a backplane & a case with the LEDs. However, since my LSI card won't identify SATA drives with the 4U case I have, I just name & order the drives both consistently (ie both in the LSI Storage Manager & Computer Manager) & sensibly (so the drive names include a number relating to the position in the case - which also corresponds to the port number on the card). [Edit] Oh, & whilst my assumption was that you were allowing the 750 to spin the drives down - since that was the problem with the LSI card... ...it could alternatively be something competing with your "Turn off hard disk after..." settings in Windows' Power Options...
  7. I assume you looked at the spin down time in the HighPoint "Non-RAID Management Software" to see if it was coinciding with that - & also the delay before any scanning or monitoring s/w kicks in? Simply that 'an' option might be that you had competing s/w trying to respectively take things in & out of a spun down &/or idle power mode. Otherwise the most likely reason for clicking would usually be a sign of drive failure... ...cable failure would normally be seen as a drive dropping out... …&, unless the card's overheating (which would normally be one or more drives dropping out &/or BSOD), you physically damage part of them or there's some f/w issue (why you always check for updates), they either work or they don't.
  8. Right, addressing these in a way that hopefully makes sense... Firstly, this was looking at using the plugin you'd suggested to fulfil the OP's initial requirement that as little data as possible should ever be stored on the shonky 3rd drive. So they'd need the 'move existing data' bit enabled, otherwise it wouldn't move anything off of that drive if space became available on either of the other 2... ...which would be worse than the OP's idea of setting up a 99%/99%/1% rule, as that would at least move some data if it more than 1% of the capacity was filled. Secondly, part of the comment about the plugin was thinking aloud about how what it says it does vs how it'd practically work overall - as I think part of the description for it is misleading outside of an add data only environment - as it can't reasonably keep each set of data written together for all & ever whilst simultaneously placing data onto earlier drives where deletion's occurred &/or rebalancing to have the drives filled in order. (& using folder placement rules appropriate to the various drives' capacities, so that no disks were ever filled, was the only way that I could think of keep most of the data that would be written together to specific drives in the way that the plugin description described - which had nothing to do with using the *.* rule) So, whilst I fully accept that this specific element of what I'd written may have been OT, depending on what the OP actually saw as being valuable about that plugin of course, I think it was still worth thinking about... (Thirdly) ...however, x amount of it was also needed to explain why someone 'could' end up in a situation where, having filled the first drive (obviously I'm talking about one half of the duplication in the OP's situation) & had data on one or more other drives in the sequence, the thing was rebalancing semi-constantly to move data towards the lowest ordering of the drives. (see the first point) Now, the key point for the OP's initial requirement was that this 'could' end up being a significant disadvantage of using that added plugin depending on their usage... ...whereas, using the standard balancers & adding rules akin to how I'd suggested to achieve the OP's original task then the only time DP would need to rebalance stuff in normal usage would be if BOTH disks 1 & 2 were filled to 99% & more data was added; which would obviously hit the shonky 3rd drive... …& then some data was deleted so that there was space for that extra data to be moved off of the 3rd drive & onto either or both of the other two. Anyway, it's obviously just a discussion - but I believe that my approach would be less likely to cause any unforeseen consequences; d.t. the way the plugin you're suggesting would have to be set up to fulfil the OP's initial requirements.
  9. Whilst this would certainly work as an alt method, my reading of the plugin is that this benefit - "Files copied at the same time will tend to be on the same disk. Because those files were copied at the same time, it stands to reason that they might be related. It can be beneficial, in terms of file recovery, to have related files be placed on the same disk." - would only actually work long term if you were only ever adding files to the pool; never deleting them. (now it 'may' be the case that this is going to be the OP's actual usage, but I can see nothing that states that it is) Well, as soon as you've filled the 1st drive & are onto a 2nd drive, by deleting something from the 1st then either, assuming there's space for one or more (but not all of) the files the next set of data you write will end up being split between the 1st & 2nd drive - or the plugin will randomly move data from the 2nd to the 1st to fulfil the rule... …& either way then, whilst you'd have a lovely arrangement on day one, this would deteriorate over time. &, at least in theory, you 'could' end up in a situation where it was spending inordinate amounts of background time balancing & rebalancing to move data from the 2nd drive to the 1st... …& the 3rd drive to the 1st or 2nd... …&... ...as you deleted &/or replaced data over time. I mean it's not even the case that the OP would have pairs of drives with the same data on - since they're using 1 big drive for one half of the duplication & (up to) 3 small ones for the other. Yeah, the only way I'm aware of to actually keep data fixed to a drive within an environment where you are deleting/replacing files, is to not fill a/the drive/s - either by having spare capacity on a single drive or to have different placement rules for different folders/data types to keep spare capacity on all of the drives.
  10. Rather than setting the slow faulty drive to 1%, why not limit the placement of the folders to not include that drive... ...however, along with having duplication enabled & setting the File Placement of folders to 99% on the 3 primary drives... ...set the Balancers to prioritise the "Drive Usage Limiter" above the "Duplication Space Optimizer" - whilst disabling the "Prevent Drive Overfill" option... …& enable the "Allow files to be placed on other disks if the selected disks are full" option in the File Placement. Well, this should only allow data in the selected folders to be placed on the 4th drive if there's not enough space to duplicate to either the 1st or the 2nd & 3rd drives (it's not clear which is smaller) - & then move the data off of the 4th drive once there's space to do so... ...whereas your 1% would tend to result in the 4th drive always having some data on. As to creating a global setting ttbomk there's 2 potential options. 1. Either you could create a single folder that you place all of the other data folders on the pool into - & then do the placement limitation & whatnot from above... ...this would cover all of the data & folders - but would use up some of the max path length. (you could also map that main folder to a drive letter) 2. OR you could create a "*.*" Rule in the File Placement - & then do the placement limitation & whatnot from above... ...which would cover all of the data, not the folders - & would save a bit of the path length.
  11. My recollection is that Chris' issue with Highpoint was with SAS/SATA HBA cards with 'RocketRAID' (aka 'RAID on a Highpoint Rocket card') - which I believe also had driver compatibility issues with FreeNAS & whatnot... ...whereas the 750 simply doesn't use that which makes things much simpler. Shouldn't be an issue for the OP for the reason above, but I guess some of it may be about how much time you're prepared to spend searching for & trialling different drivers vs having something that'll just work... So, whilst he also doesn't recommend SIL controllers, adding a simple 4-bay DAS to my low spec 24/7 machine simply wouldn't work properly using either the onboard ASMedia eSATA (explicitly having PortMultiplier) or the ASMedia & Intel USB controllers; with the drives spasmodically dropping out several times a day irrespective of the driver version - which then obviously caused issues with DP... ...whereas a cheap StarTech SIL PCI-E eSATA controller &, whilst the latest SIL drivers seemed to have randomly stopped port-multiplication working, going back a couple of versions & it's rock solid. Conversely though, everyone loved the 24 port HP expanders - whereas, even after buying a HP card to flash the stupid thing to the latest f/w, I just found them painfully slow... ...so people expectations & experiences certainly vary. Yeah, so obviously the 750 isn't a performance card, as mentioned, but for a DP media backup usage (vs FreeNAS) then it should be perfectly adequate for the OP's usage. Otherwise, I've also no idea how the OP was getting a sustained 400MB/s write speed - & would also be interested to know about the testing method for that. Well, there's not a cache on that LSI card - so either something's misreporting the speeds; or there's another write cache somewhere in the setup; or, as you say, it's writing to a few drives simultaneously.
  12. Well, you're losing the ability to ever use SAS drives - though, whilst the 750 is a slower card with a lower total throughput, your current usage (given that you're using the Seagate archive drives & DP) is unlikely to ever make that a limiting issue. Then, imho, editing the registry is really no big deal - whether it's sorting out something stupid like altering the default search engine to make it region specific or trying to troubleshoot an issue with Windows or something like this... ...so it really depends on what the LSI card cost you (assuming you'll never use SAS otherwise you'll have to buy another card) - as if it was cheaper then I'd stick with what you've got &, if needed, edit the registry. Otherwise, within a price bracket, it's all about finding the best balance for your usage - so, for me - - losing the ability to spin down active drives on a LSI RAID card (as I don't want to flash it to IT mode - turning it into a HBA - where I could then use the registry edit) isn't important; as that machine's not on 24/7, only for specific tasks, & it removes the relatively small risk of drives not spinning up fast enough & dropping out. - whilst having a cache, BBU & the ability to use SAS drives are important for elements of what I use the machine for. But that's just prioritising what's important to me - not what anyone else should do.
  13. As noted before, I'm using a RAID controller, not a HBA, so you'd need to explore the f/w, drivers & s/w for your card. That said, a quick google search & there's this - - however, as far as I can see, 4&83E10FE&0&00E0 is not necessarily a fixed device ID - so you'd need to look in the registry for the equivalent.
  14. Yeah, I was about to post that I'd just tried HWMonitor today & it doesn't pick up my RAID card. Otherwise I have honestly no idea whether that's normal for the Seagate Archive drives as I use WD (plus there's a handful of ancient Samsungs that are refusing to die), though they are reported to be noisy... ...or are you using Stablebit Scanner as well? As I don't use LSI HBA cards, what I'd suggest is to have a look on https://www.broadcom.com/products/storage/host-bus-adapters/sas-9305-24i#downloads - with a view to updating the f/w & drivers, as well as seeing if the Management s/w & tools has any options... Though for some unknown reason it's only showing downloads for your card in under Archive, not Current.
  15. Ummm… Not at home to try things atm &, tbh, I'm used to LSI RAID cards where they have a Windows GUI for setting stuff up & monitoring & whatnot - which your HBA doesn't appear to use according to the relevant download page on the Broadcom site. If I had to make an educated guess though, I would imagine that HWMonitor - https://www.cpuid.com/softwares/hwmonitor.html - is the most likely thing to give the temp of the IOC; assuming that it actually has a sensor .
×
×
  • Create New...