|
Post by DennisE on Feb 21, 2016 0:23:33 GMT -6
I have four NDAS drives , network attached drives, and I haven't been into them since I installed windows 10. Yep you guessed it they don't work on windows 10. I reinstalled the software and it crashed windows 10 on reboot and I had to go into repair and run the restore point to get it back up again. Now I have to dig into some of the machines that won't install windows 10 and use them for access to my NDAS drives. I can always transfer the information I want backed up on the ndas by network to the machine that does work. This can be a long way around but if I want to use the ndas drives that will be the only way that I can use them.
Checked google and a lot of other people have the same problem that I had.
Dennis E
|
|
|
Post by Cherub (a.k.a. Steve L.) on Feb 21, 2016 23:46:02 GMT -6
Hi Dennis, are you saying this a problem that Win 10 has with network attached DASD in general, or that it works with most but not with yours? Seems like a major defect if WIN10's generally not working with networked storage.
|
|
|
Post by grega on Feb 22, 2016 11:46:38 GMT -6
The matrix below partially illustrates MS's limited support for "local" networked drives/tape etc. But the good news is dasd, sds, is supported for MS-Server, and for MS-Azure services. Since 90% plus of all users of these devices use either Linux (RHEL, Suse or Debian/Ubuntu) or Unix (AIX, BSD, HPUX) . . the market for home & soho is small. Even on Azure, the fastest growing data mgmt tool is Ubuntu & RHEL (Linux) because of MS-OS's limitations. Another very doable solution is to run any "Nix" OS on a VM (Virtual Box), or to run a "Live" Linux usb-flash-stick, because unlike Windows, Linux is designed to play nice with network storage and numerous file systems . . . the two most advanced computer file systems are only supported on Linux/Unix (btrfs and ZFS). The Live OS is a simple solution, . . no changes made to the hdd system, and full support for fat32 and ntfs. I have read that increased support is coming, but am not sure about the time-table - - perhaps a call to MS Support Services can clarify.
|
|
|
Post by DennisE on Feb 22, 2016 11:55:20 GMT -6
I know windows 10 does have problem with XIMETA,NETDISK models of ndas. It runs fine on windows xp and windows 7. I will have to test it on a stray machine and run Linux and see how it likes that.
This is just another reason to save a computer to run Windows 7 for this kind of problem.
Dennis E
|
|
|
Post by grega on Feb 22, 2016 12:12:16 GMT -6
Dennis, if you're thinking of testing out Linux . . I do recommend the following methods as you won't need to mess with partitioning, etc. > a RO (read only) system that either runs from the media or from RAM (the latter is much faster/better) . . see Parted Magic partedmagic.com/downloads/> a "Persistent" Live OS (allows user to make changes - - has "write" to FS enabled), > a full install to a USB Flash Stick. Best type of stick is a SanDisk of 32 GB or better (a version 3 usb is almost as fast as hdd) (this is my favorite method - - most secure and customizable). The above presumes your hardware is new enough to boot from live media via tweaking BIOS or UEFI settings. Here is a decent youtube tutorial on how to create a usb-stick full installed Linx OS: www.youtube.com/watch?v=fLYBXOVn6ow
|
|