Jump to content
Division-M Community

seePyou

Members
  • Content Count

    9
  • Joined

  • Last visited

    Never
  1. Hello, first of all, I've tried to see if the knowledge base could offer the answer, but this created more questions, so here they are. a) I do not see any duplicated folders! You know those with the dollar sign. Where are they? Hidden files are displayed, so it's not that! Could it be that I'm not seeing them because all my HDDs are driveless and the only drives are C: for the system and D: for the pool? My D: pool has another folder of a long alphanumeric name. Should that be there? [*]I thought that this was different and hidden for every HDD in the pool, so why am I seeing it, and why only one? The name is {9960EDF7-1D41-49F8-99A2-DCD2E772893E} [*]Inside that folder there are some groups of other folders, similarly formated: [*]Some that start and end in underscores: _682734_ [*]Some that are again alphanumeric but of random character length: 96a914e824a575fba885a0402b1010 [*]Some that end in (dot)temp: MSI2e93.tmp All in all these are 401MB out of the total storage of 11.25TB out of 14.5TB, so they are not too much space wasting, but I'm just curious So if this helps, this pool was first built by creating an empty pool, copying things in the folders, and the final four drives I just merged from a previous pool. Purely informational of course, but I'd like to know just in case there is something I should do. Thank you!
  2. This is now solved and ASRock support provided me with the answer. When I connected the SATA ports to the ICYBOX, that made them see the connection as eSATA. Since the secondary ASMedia controller is not eSATA capable, it was throwing these errors. The same would happen with the Intel Z77 as this controller has the option to be set as eSATA Enabled from the BIOS, but it was far more resilient, apparently, and this is why it did not throw as many errors as the ASMedia controller. Enabling eSATA on all ports of the Z77, since they would continue to be plugged in two ICYBOX, and connecting the remaining two drives directly to the motherboard SATA ports of the ASMedia controller solved all problems.
  3. I tried it anyway... and it does work. So now I've moved my disks to different controller slots on the motherboard while it was shut down, and DB did not have any issue with it when the machine was booted up. KB article maybe?
  4. Hello guys, Does Drive Bender have any issue if I take a drive added in the pool and hot swap it with another in the pool? I'm trying to troubleshoot connection issues, so I want to take DB7 and plug it in the slot for DB1, and take DB1 and put it where DB7 was. Can this be done on the fly? Should I do this with the server shut down? Or is it simply not a good idea? Thank you in advance!
  5. Thank you for your response. There is no paging file placed on any individual drive, as they are not assigned letters. There is only C: and D:, with D: being the pool from DB. Also, the OS virtual memory is set only on C: with D: being set to none.
  6. Hello all, I'm wondering if you know of any issues with Asrock Z77 Pro4 onboard secondary controller and WD RED 3TB drives. I built a new system on Win 2008 R2 with drive bender and I have been plagued with issues about them. I have three WD REDs and five other drives. The M/B gives eight SATA ports, 4 of which are SATA 6 and two of these are on the extra controller. From the specs: - 2 x SATA3 6.0 Gb/s connectors by Intel? Z77, support RAID (RAID 0, RAID 1, RAID 5, RAID 10, Intel? Rapid Storage and Intel? Smart Response Technology), NCQ, AHCI and Hot Plug functions - 2 x SATA3 6.0 Gb/s connectors by ASMedia ASM1061, support NCQ, AHCI and Hot Plug functions Now I have all WD RED drives connected to SATA 6 ports, and two of them are on the ASMedia controller. I am getting many messages like these: An error was detected on device \Device\Harddisk7\DR7 during a paging operation. The device, \Device\Harddisk6\DR6, is not ready for access yet. The driver detected a controller error on \Device\Ide\IdePort6. There are about 1500 error messages of the last type, most of them about 6 and 7 (the ASMedia controller) but some very few others from 4 and 5 (3 total over a month since I built it) All drives are plugged in to ICYBOX MB454SPF-B 4x3.5" enclosures. If anyone can advise me on how to go about troubleshooting this, I'd appreciate it.
  7. never mind, I just pulled the drive out, uninstalled DB, reinstalled and started from scratch from an empty drive. I think the issue was with starting from scratch from a converted drive that was not given a Pool mount point... but this theory is not for me to chase... This thread should now be closed.
  8. Well, I solved one thing; Windows drive management shows a DB1 drive that was not given a letter. I gave it the letter F: and then I could see the guid folders. That has not helped though about the inability to write to the drive. I am logged in as the Administrator (there is only one more user and that is a Standard user that I made after installing the OS) but when I try to create a new folder in the root of the DB1 I am unable to. The root already contains two folders and I can create/delete anything whithin those two folders.
  9. Hello all, I've been using WHS 1 for some time, but over the past years I have been struggling with it with constant errors. So I decided to move on to something else, and that was Win2008R2 and DriveBender (DB). When I converted my hard drive to a pooled one I was not asked as such what drive letter I want it as, so it took the one that the drive had, E: However when I see it in Windows Explorer there are no GUID folders. One further complication is that I'm getting Recycle Bin Corrupted errors that I have no permissions to fix, and I cannot manually create a folder in drive E: from Windows Explorer. Anyone has an idea where I went wrong?
×
×
  • Create New...