Jump to content
Covecube Inc.


  • Posts

  • Joined

  • Last visited

psykix's Achievements

Advanced Member

Advanced Member (3/3)



  1. I've read quite a few posts, but they are a couple of years old now. Could someone please confirm the best settings for CloudDrive for Plex? The GDrive will be used exclusively for media. Mostly 1080p, but would be great if I could get 4K working too (not remuxes). Also the chunk size? My internet connection is 80Mbps down, 18Mbps up if that has any bearing on the settings. Thanks.
  2. My Gen8 is rocking a E3-1265LV2 and it seems that even that may not be supported. Strange that I wasn't given any warning or anything when I installed. Oh well, you live and learn I guess!
  3. Yeah.. I put it all down to ESXi 6.7 - have never used that version before, but have used 6.5U2 and that was fine. 6.7 is very very odd. Performance all over the place. Main reason for running VMWare is that I run an SSD in the ODD bay, and 4 x 4TB drives in the bays. This means that to boot from the ODD into Windows 10, then I need to use a SD card fudge. That works great, but every time there is a major Windows update then it fails to install because it thinks I am trying to install onto a USB drive. Have to remove the drives in the bays, boot into windows, update windows, redo the SD card and then put the drives back into the bays. What a faff!!
  4. Oh, and just to add. I was using the beta version of the scanner. On the reinstall with the same version, the drives are reported as the correct size. Something really whacky with that ESXi 6.7 (I've used VMWare in the past on this Gen8 without issues)
  5. I've blown away my ESXi 6.7 (the performance on my Gen8 was abysmal, and no idea why). Changed the drives back to AHCI and reinstalled Windows 10 on bare metal. Now all my files are fine again. No idea what the issue was with VMWare, but I did send you all the logs, maybe you could take a look when you get a boredom moment! I'll add to the ticket, because in my haste I forgot to deactivate the licenses - doh! Cheers :-)
  6. Trying to copy one of those out of the pool elsewhere or trying to play some of the media files results in error 0x80070057 the parameter is incorrect. Everything just feels a little flaky at the moment. One other thing.. I converted the drives from AHCI to individual RAID 0 arrays, and passed them through as RDM to the VM. Previously this would prevent S.M.A.R.T. reporting, but that now works. Did something change? EDIT: Weirdly, I can copy and paste the problem files around the pool, but not from the pool to another drive.
  7. My drives should be 3.64Tb, but show as 1.64Tb. In the file system part they report correctly. Any idea?
  8. I get different results also with each scan. I'm currently running a burst test.
  9. I'm having a similar issue on a Samsung 850 EVO. I thought any unreadable sectors on a SSD should get remapped? Samsung Magician reports the drive as "Good" I'm trying to figure if I need to RMA this drive. The server it is in hasn't shown any adverse effects so far.
  10. For-some-reason,space-bar-doesn't-work-on-this-forum-using-Microsoft-Edge-browser! I-can't-find-memory-dump.Maybe-latest-windows-insider-update-removed-it?
  11. I've never had an issue until the latest beta version of Drivepool, and downgrading has fixed the issue, so something has changed in latest beta.
  12. Oh, and in case it helps, the crash was reporting an NTFS.SYS problem. Strangely, if one item was added to Sab, then all was fine - add a load of items to the queue and it would green screen Windows and orphan the queue.
  13. I've spent days and days trying to get to the bottom of green screen of death on Windows 10... I kept blaming the new version of Sabnzbd, but since there were no issues posted on their forums was beginning to think that was not the culprit, despite the green screen only ever occurring when using Sab. Realised I had been prompted to update Drivepool... Have downgraded back to non beta version of Drivepool and now all is fine again. There's a serious issue with the latest beta...
  14. psykix

    IO retries.

    Never mind. I should have searched! I see that the above is expected behaviour due to being an emulated drive.
  15. psykix

    IO retries.

    Any idea why I am seeing the following regularly in my event log? Don't seem to have any adverse effects, all disks showing as healthy and scanned. This is reported on Drive 5 - which is the Drivepool with a volume label. Log Name: System Source: disk Date: 15/05/2017 16:17:21 Event ID: 153 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: PLEXSERVER Description: The IO operation at logical block address 0x1 for Disk 5 (PDO name: \Device\0000002d) was retried. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="disk" /> <EventID Qualifiers="32772">153</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-05-15T15:17:21.896448700Z" /> <EventRecordID>10759</EventRecordID> <Channel>System</Channel> <Computer>PLEXSERVER</Computer> <Security /> </System> <EventData> <Data>\Device\Harddisk5\DR5</Data> <Data>0x1</Data> <Data>5</Data> <Data>\Device\0000002d</Data> <Binary>0F01040004002C0000000000990004800000000000000000000000000000000000000000000000000000048A</Binary> </EventData> </Event>
  • Create New...