Blackarmor Nas 1d Driver For Mac
Hi, this might get long, but I need some help here. I bought two 440's with the 1TB drives in them, raid-5, and updated the firmware to get the iSCSI features.
After some initial bumps, I got it working, to a point. There was always a 2TB limitation on them, even though support assured me that windows could recognize the devices up to 16TB. Using one as a backup B2D for backup exec (2012), I started running out of space, and had to constantly reduce my retention periods. Space was becoming an issue.
So I talked with support again about upgrading the devices with 3TB drives, and they said no problem at all. For what it's worth, they are very nice, and generally helpful at Seagate support, but limited in their scope at times. I upgraded, and again through some bumps and bruises, ultimately had to wipe them, but got them set up and striped. Of course when trying to initialize the drive on the 2008 server, I get the infamous 'the drive cannot find the sector requested', to which support says they've never heard of that problem, yet google seems to disagree. After days and days of trying to get it to work, I gave up, joined the units to the domain, and tried using folder shares.
One worked, for a little while, I was able to run backups to it and had a cool 8.05TB of usable space. Then out of nowhere, backup exec choked and couldn't connect anymore. The 2nd drive was never able to connect using the AD permissions. It simply prompts a username/password box and won't accept anything, no matter what configuration I set on the NAS AD permissions.
Even setting it to 'public' only allows some computers access, and while it works today, it may not work tomorrow. Support had me convinced that the unit is simply defective and needs to be replaced, until the backup NAS started having issues (as noted in the last paragraph), I ended up resetting all the permissions, and still cannot access it either now. Same pop-up dialogue, same denied access. Set it to public and now backup exec can access it again (for now). My problem is that I have no idea how long access (as public) will last, and I have a lot of reservations about having them fully accessible on the domain. Oh, and MAC's still can't access them, which is the whole reason I bought the 2nd device, for our file-intensive marketing department, who all use MAC. I don't know what to do at this point, so I'm here asking for suggestions.
I've exhausted google and seagate support, and have made no progress. ISCSI- don't work. AD- don't work. And yes, I do have the latest firmware update and have gone as far as doing factory resets on both (which takes 2+ days with striping raid-5 on 3TB drives). Thanks for any input on this! Limey- I did scour the previous threads, but instead of replying to older discussions, I figured it was best to create a new one.
I did re-read the one topic, and saw the admin was able to mimic his AD on the local permissions to allow access that way. He was clearly not happy about having to hand-key all the groups, users, and PWD's; and I would be equally as unhappy about that, but it does seem like a good fallback solution. Dataless- I bought them almost 3 years ago. They've offered to replace them with refurbs, but I'm convinced that it's not a hardware defect as much as a software problem, and setting up a replacement unit will only be a bigger headache. Any chance we can all join together and push Seagate to go back and fix these problems and deliver a solution via new firmware? Kprivigyi wrote: I can get them both joined to domain, and they see the AD users and groups.
Lets me assign them without any issues. The only problem is when I try to connect to the device outside of the GUI, like using windows explorer.
I get prompted for u/p and it won't take anything. Even it's own local admin user.
Try joining to Workgroup, reboot and then rejoin. You have nothing to lose.
Blackarmor Nas 1d Driver For Mac
I would get the exact symptoms you're describing. Would be able to access np via the GUI, but nothing via Windows Explorer. I really wish I could go back to using them as iSCSI devices. I didn't need to join them to the domain, and they operated as a virtual HDD on the server. Easy to apply AD folder permissions. But they won't initialize (as described in my OP).
Again, when I used to call them for support on that specific problem, they deemed it was a hardware problem, and left it at that. It seems to be a fallback position in support departments these days. Instead of replicating issues and turning issues over to a dev team for a fix, they just blame the hardware. Hoping for the magical solution still. I do have them working as 'public' folders, which was never my first choice, but working beats not working. I did try that at least 5 times per device. One device I was able to access at first via AD permissions, and when I first called into support, it was focused on the one that wouldn't.
But I'm guessing a short interruption in power or signal (as you suggested) caused the one that did work to stop. And no amount of unjoining, rebooting, re-joining ever got an AD connection to work again, so at that point, both units identically didn't work with AD. With support, I even did a factory reset on the one that never worked with AD, and nothing changed.
You are probably right about the 2TB limit, I don't recall how exactly I had initialized it when I first set up the iSCSI. But now that it's upgraded with 3TB drives, I can't initialize it at all- I knew I would need to go with GPT, but nothing will get past that error. I've seen a lot of forums with people having the same issue, but no solutions seem to have been found. Seagate support officially says 'It should work, it works here. Must be defective hardware'; and that's the end of that.
So far, after 3 days of using both in public folder mode, we're still up and connecting, so I guess the lowest common denominator is the only solution, other than setting up folder permissions manually using the internal security, which I just don't have time for this week. I was kind of hoping someone from Seagate would pop in, ask me the right questions, and tell me something key that I didn't know. Wishful thinking:). Hardware BA NAS 440 with 4, 2TB drives. Replacing 2TB Seagate drives with Seagate 3TB GPT drives and running into the 'Foreign Harware' issue. I tried several different configurations and reviewed the forums without finding a solid solution. In a final attempt I formatted and partitioned the 3TB GPT drives to 2TB MBR in hopes that the NAS would see it.
It not only has seen the drives but all 3TB (2.73TB) of the drives. It is resizing all the drives now to form the new volume.
I will post again when complete for status. Edited Jan 15, 2017 at 20:25 UTC.