tomsliwowski
-
Posts
18 -
Joined
-
Last visited
Posts posted by tomsliwowski
-
-
So I see the iso for Server 2019 sitting in MSDN and I'm, of course, itching to do an in-place upgrade of my Server 2016 setup. In a (very) rare moment of caution I figured I'd ask about if DrivePool and Scanner have been tested on 2019. So...have they? Any issues I should know about before taking the plunge?
-
40 minutes ago, Christopher (Drashna) said:
You could.
But it's not really ideal for that. Specifically, it's an "iSCSI" device. So the drive or drives show up like a physical disk, and can be added to the pool.
But it's a bit more of a complicated setup.
I'm looking to have some sort of parity and redundancy that the Drobo provides (I'm kind of wary of running my deathwish drive pool).
The goal is that at some point, my entire pool will be just made up of individual Drobo iSCSI volumes.
If you have a simpler and financially equivalent solution I'm more than happy to hear it. -
So I'm thinking of picking up a used Drobo Pro (DRPR1-A) for like $250 from a guy on Facebook. Now I'm fairly sure this thing is limited to volumes of 16GB in size which isn't a big deal if I can use DrivePool on my Server 2016 box to combine a couple of volumes into one pool. Is something like this supported? Keep in mind this would be my first Drobo anything (they were always WAY out of my price range for what they are) so please excuse my ignorance in case this whole thing is a ludicrous idea.
Thanks!
-
Nice setup. Where did you get that case cause 45 drives doesn't seem to have it on sale by itself.
-
Do NOT run it with "/scan".
While, this option is pretty awesome, it skips a number of checks, include the Volume Bitmap. You need to run this offline only, meaning without the "/scan" flag.
This is an issue that I ran into myself and it tricked me. (as well as Alex initially).
So running it with /scan didn't find anything and your explanation that it skips the volume bitmap part seems a good explanation as to why it didn't find anything bad.
Now running chkdsk /F then running another chkdsk to verify no other issues are found is the correct approach, right?
-
So running chkdsk /F fixed the issue. It said that the issue was space that was marked as used but was really free. So far I reset the filesystem health status in Scanner to unchecked and ran the scanner on both 3TB drives and am currently running it on the 8TB drive. Both 3TBs now came back as normal.
-
OK, I'm not sure what the deal is but now a third 3TB drive has come up with the same error. I can understand 2 disks having the same issue at the same time but 3 out of 4 pool members seems a bit....unlikely.
There has been nothing recently done on this server outside of upgrading from 2012 R2 to 2016. I believe this is the first time the drives got scanned since the 2016 upgrade so could that have something to do with these results?
-
I will let Chris explain the chkdsk options and what they do - as some are more comprehensive than others
if not done already check the smart values for both disks - although its not showing bad sectors at the moment - it may not have picked them up yet or the disk has remapped them already - hence the smart check
What was the error on the other disk?
The SMART values appear fine and both drives show no imminent failures expected.
The other disk had the same kind of error in Scanner but was fixed with whatever operation ran when I clicked to fix the issue in Scanner (I assume chkdsk).
-
So I woke up this morning to some alerts from Scanner that 2 of my drives had filesystem issues (both drives are in a pool).Running the link to fix the drive within the Scanner fixed one drive right away but my 8TB drive failed and asked me to run chkdsk manually. I assigned the drive a letter and chkdsk reported the following:
Stage 3: Examining security descriptors ... Security descriptor verification completed. 11604 data files processed. The Volume Bitmap is incorrect. Windows has checked the file system and found problems.
Running it with the /scan switch found no issues but running it without it did. Here is the full output of both commands run back to back:
PS C:\Users\Administrator> chkdsk.exe g: /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 208384 file records processed. File verification completed. 6400 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 231592 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Security descriptor verification completed. 11604 data files processed. Windows has scanned the file system and found no problems. No further action is required. 7630883 MB total disk space. 5479076 MB in 188976 files. 77960 KB in 11606 indexes. 0 KB in bad sectors. 513531 KB in use by the system. 65536 KB occupied by the log file. 2151229 MB available on disk. 4096 bytes in each allocation unit. 1953506303 total allocation units on disk. 550714792 allocation units available on disk. PS C:\Users\Administrator> chkdsk.exe g: The type of the file system is NTFS. WARNING! /F parameter not specified. Running CHKDSK in read-only mode. Stage 1: Examining basic file system structure ... 208384 file records processed. File verification completed. 6400 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 231592 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Security descriptor verification completed. 11604 data files processed. The Volume Bitmap is incorrect. Windows has checked the file system and found problems. Please run chkdsk /scan to find the problems and queue them for repair. 7630883 MB total disk space. 5479076 MB in 188976 files. 77960 KB in 11606 indexes. 0 KB in bad sectors. 513531 KB in use by the system. 65536 KB occupied by the log file. 2151229 MB available on disk. 4096 bytes in each allocation unit. 1953506303 total allocation units on disk. 550714792 allocation units available on disk.Is this an issue and if so, can it be safely fixed or am I looking at a drive replacement?
-
However, just like Windows 10, any version of our software will run on it without problem. However, the 2.2.0.651 version should work better.
How ready for production use is 2.2.0.651? I'm a bit hesitant using a beta release on my pool.
-
Now that Server 2016 is generally available, I was wondering if DrivePool and Scanner are compatible with it. I'm currently running both on Server 2012 R2 but feel the need to upgrade to 2016 (yes, I know there is no good reason to but I really want to have the new shiny toy).
-
Is this something new in the 2.x version of DrivePool? I don't recall this ever happening on my WHS 2011 server running DrivePool 1.x.
Also how big of a performance hit would it have?
-
So after restoring my data from a HDD loss (covered here: http://community.covecube.com/index.php?/topic/2037-scanner-didnt-find-my-2tb-red-was-going-bad)I noticed a weird issue with my music library.
I restore the whole library to an external drive using CrashPlan and then I copied the directory to my drive pool, overwriting all existing files. Everything seemed all nice until I added a new album to one of the sub directories. Subsonic wouldn't find anything and after some troubleshooting with the developer it was discovered that the modified time was not being updated on the parent directory.
Here is how the library is laid out:
E:\ServerFolders\Music\<artist>\<album>
When I add a new file or directory inside an <artist> directory, I expect the modified time of the <artist> directory to also update.
I was able to force a timestamp modification by running the following in powershell:
$update = get-date Set-ItemProperty -Path E:\ServerFolders\Music\ -Name LastWriteTime -Value $update
This is only a simple band-aid since the timestamp won't be updated the next time I add another album.
The REALLY weird thing is that it seems to be inconsistent. Like some directories update just fine while others do not.
Is there some kind of NTFS flag that needs to be re-set? How can I even start troubleshooting this?
Here is my server setup:
Windows Server 2012 R2 Standard
Core i5 3570K @ stock speed
16GB DDR3 RAM
OS drive:
Sandisk 120GB SSD
E:\ Storage Pool:
1x 8TB RED
2x 3TB RED
1x 2TB RED
-
I guess that is what happened. Sorry if I came off as hostile, it was just a huge pain in the ass to restore music/pictures/docs from crashplan and then to randomly find corrupted videos from the files I didn't have backed up in crashplan :-/
-
Just to follow up. I tried it in two USB enclosures and also tried plugging it directly to a SATA2 port. Same deal.
The drive looks like it was failing for a while because prior to it being replaced I did notice that things like reading or writing to the storage pool was rather slow (over the network it would start at 50MB/sec then slow down to <1MB then burst back up over and over again). This would indicate that the drive was going bad already.
-
So I've had scanner + drivepool running in my WHS 2011 box for 3 or so years. I recently purchased an 8TB RED to replace on of my 2TB RED drives.
I properly shut the box down, replaced the 2TB with the 8TB and placed the 2TB in an external USB enclosure. I added the 8TB disk to the pool and then tried to have drivepool remove the 2TB drive. I kept getting errors when trying to remove the drive so I decided to see if I could save the data by going into the drive and manually copying the contents. This took almost a day to get about 1.6GB of data and when I looked at what was copied I noticed that it was all corrupted (video which was unplayable or with crazy artifacts, pictures that were corrupted, music that sounded distorted, doc files that were unable to be opened). Luckily I had crashplan backing up the stuff I couldn't replace so the loss wasn't monumental.
My question is why did scanner not flag this drive as bad? I've had drives in the past report as "about to fail" and I was able to replace them in time but this drive went from "almost unreadable" to "will no longer recognize" without warning. The scanner said it had scanned the drive a few weeks prior,
-
I tried to upgrade my existing 1.3.0.7534 version with the latest stable but got an error upon installation that the Add-In was invalid. I re-downloaded the binary thinking something got corrupted during download and tried to install again. Now the installation errors saying that the application is already installed.
Checking the Add-ins tab on the WHS2011 console it shows version 1.3.7556 installed but the DrivePool section still shows the old version number in the lower right hand side.
Did the install actually complete the first time and the version on the DrivePool section is a typo? If not, how can I safely get the latest version installed on my system. I have about 5TB of data in my pool which I would really hate to loose.
Thanks!
Server 2019 compatibility?
in General
Posted
That's exactly what I am planning to do. Glad to hear it's working. I'll probably do my upgrade tonight.....fingers crossed.