Jump to content
Covecube Inc.

PocketDemon

Members
  • Content Count

    62
  • Joined

  • Last visited

  • Days Won

    3

PocketDemon last won the day on May 30 2019

PocketDemon had the most liked content!

About PocketDemon

  • Rank
    Advanced Member

Recent Profile Visitors

428 profile views
  1. With the onboard asm1061 eSATA controllers on a handful of motherboards I've owned, whilst they'd work perfectly with a single drive, I had unresolvable issues with port multiplying due to the drives switching off & having to reboot to get them back on again - & completely lost the will to live trying different driver versions. Now, for historical reasons, I'd bought one that uses the Marvell 88SX7042 controller - in my case the StarTech PEXSATA24E, but there are others - &, whilst I couldn't get port multiplying to work beyond driver version 1.2.0.1049, it's been rock solid w
  2. Whilst YMMV, in my experience the cheaper multi-bay USB enclosures are nothing but trouble in terms of spasmodically disconnecting one or more drives - so, unless you've real money to spend, if you're after a cheap enclosure then it's eSATA all the way. So, given the options, a pcie SATA card would be the better option, imho, if cost is king... ...but it's your call as to whether using the server case or not is worth the extra for a new board.
  3. Having turned it off, I believe you also have to choose the "decrypt drive" option on the same Bitlocker page.
  4. Tbh, this sounds like it's nothing at all to do with DP, & instead is wholly an encryption problem. Now I'm guessing that it 'may' have been encrypted with Bitlocker - as that's the default Windows thing... (unless you were sent a USB drive with some bespoke s/w on or something) ...&, assuming that it is Bitlocker that's been used, the usual way to resolve this would be to go to Control Panel -> System and Security --> Bitlocker Drive Encryption... …unlock the drive, using the key you've been given, & then try to access it again. Then I can't t
  5. I'm not saying you're wrong, as I've never had this happen with a DP drive & I read the description that the OP completely differently - however my experience of permission issues didn't make the data wholly inaccessible... ...just limited what can be done with it. The way to test this would be to assign a letter to the specific drive & see if the data can be accessed AND if there's any limitations on ownership of the files. Then I suppose another option might be that DP is incompatible with whatever it's been protected with that needs a password - & so DP isn't picking
  6. The only thought I have is to ask if you've tried connecting it to a standard SATA port rather than the HBA card? Well, I know that I can pull SATA drives from my LSI card & they'll work on either an onboard Intel SATA controller (I've simply not tried AMD or SIL or whatever controller, so I'm not saying that they wouldn't work) or a random USB dock... …& it 'might' be the case that your Highpoint HBA writes something to the drive to identify it which Seagate's recovery service has screwed up. [Edit] Otherwise, it's really not ideal that you're having problems with
  7. 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; n
  8. 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.
  9. Have you enabled showing hidden files in File Explorer, as stated in the wiki, as it's certainly there in mine?
  10. http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings
  11. 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.
  12. 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) & sen
  13. 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 o
  14. 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, pa
  15. 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 i
×
×
  • Create New...