JCristina
Members
-
Joined
-
Last visited
-
After the latest stable release 6.7.2 Hot-Swap does not work. Example. Added another drive into an available drive bay but the drive does not show up in Unassigned_Devices. (see 1st image) Rescaned from terminal: rescan_scsi_bus (see 2nd image) Drive now shows up as an Unassigned_Device (see 3rd image) Additional information: I also tried to uninstall Unassigned_Devices and Re-install and that did not work either. The only other thing that worked was to [ REBOOT ] the server which also immediately displayed the missing drive. Could it be that there is an issue with hot-swapping drives and auto repolling/scanning for changes in the SCSI subsystem? If anyone is having this issue where drives are not showing up when swapped into your server, REBOOT or run command rescan-scsi-bus from the terminal. Note: @testdasi was kind enough to provide the later remedy. Any additional method of a permanent fix would be appreciated.
-
Great point. Question about Unassigned Devices. I was transfering data via a USB 3.1 bare drive HUB the last time I build the array. Is it "faster" to simply plug in the drive with data and under Unassigned Devices hit MOUNT and copy the files over? Thanks
-
Love to hear you findings. Honestly, itimpi, I'm truly shocked there are not more people interested in the topic of data transport between their UNRAID device and any other device to assure data accessibility. Strange as that's the point of UNRAID vs RAID .. IMHO. 😏
-
I will try the plain-jane Linux method of trading the files. Question: were you set as xfs or btrfs ?
-
Great suggestion. Could just make a simply 16GB USB thumb drive with lite weight Linux distro and try it. I know some don't find this important but for me the main reason for unraid was the ability to not get locked into a raid manufacture's hardware for me and the security of knowing that even when sh*t hit's the fan there I could just throw a drive into a hub and pull the data off of it. Can't wait to hear other peoples work arounds...
-
ouch! I guess then the question would be, if not Paragon then who or what can be used to read in UNRAID drives that are force to be removed due to an emergency? One of the big draws for me was the ability to not require a proprietary system which forces the user to fix the server they have or all their data is rendered usable. Example: If one was working on a project and their server went down, fixing or send away a big box raid array device would be costly but more importantly to time consuming. The idea of the "un" raid was intriguing for this fact. Now ... Well ... :(
-
No I did not encrypted. I simply ran them through preclear and set them as active from unassigned and turned on the array. Thanks for the question.
-
Just recently I pulled 2 8TB Seagates Compute (SMR) drives to replace them with 2 8TB IronWolf Drives and found problem. Please let me know what I did wrong. My understand was that since UNRAID was not a RAID I would be able to pull any drive (minus parity) and access the data using my USB 3.1 Drive HUB or other enclosure. Well, I tried this theory and found that the drive which had 5TB out of 8TB used showed up as empty. See screenshot attached. ( DISK 4 & DISK 5 ) I have all the data archived so it's not an issue but since I'm rebuilding this array from scratch I want make sure the new setup drive array will be fully readable outside of the server just in case there was a hardware failure. Please advise and thank you in advance for taking the time!
