July 18, 201114 yr I did some searching on the forum and wasn't able to come up with an answer on my own, so pardon the new post. Here's the situation: My old media server was running windows 2003, with 4 1.5 TB drives running in a software RAID-5. I recently purchased unRAID, and built out a new server that is currently running 5 2TB drives, 4 for data and 1 for parity. All was/is running perfectly. After quite a long time of transferring data, i emptied the old server's contents into the new one. So now, after breaking down the old RAID, and adding one of the 1.5TB drives to the unRAID box, i can't seem to add it to the existing media server share. I precleared the drive using the script found on this forum, added it in on the web GUI, and it was recognized as valid, and i can access it using the "disk5" share. However, even though i have the share set to use all available drives, it doesn't add the disk5 space to the available space on the media server share. I also tried explicitly telling the share to use "disk1,disk2,disk3,disk4,disk5", but i still don't get the extra space from the 1.5 drive. Is this normal? The only thing i can think that would cause this behavior is that it's a smaller drive, but i wanted to make sure. Your thoughts, gentlemen? Thanks in advance! -J
July 18, 201114 yr I did some searching on the forum and wasn't able to come up with an answer on my own, so pardon the new post. Here's the situation: My old media server was running windows 2003, with 4 1.5 TB drives running in a software RAID-5. I recently purchased unRAID, and built out a new server that is currently running 5 2TB drives, 4 for data and 1 for parity. All was/is running perfectly. After quite a long time of transferring data, i emptied the old server's contents into the new one. So now, after breaking down the old RAID, and adding one of the 1.5TB drives to the unRAID box, i can't seem to add it to the existing media server share. I precleared the drive using the script found on this forum, added it in on the web GUI, and it was recognized as valid, and i can access it using the "disk5" share. However, even though i have the share set to use all available drives, it doesn't add the disk5 space to the available space on the media server share. I also tried explicitly telling the share to use "disk1,disk2,disk3,disk4,disk5", but i still don't get the extra space from the 1.5 drive. Is this normal? The only thing i can think that would cause this behavior is that it's a smaller drive, but i wanted to make sure. Your thoughts, gentlemen? Thanks in advance! -J We need the version of unRAID you are running and a syslog. There is a troubleshooting link in my sig that should give you direction on how to get to the syslog.
July 18, 201114 yr Author Apologies, i should've thought to include that to begin with. I'm currently running Unraid 5.0B7 (happened to be the latest version available at time of purchase), and the syslog pastebin is available here: http://pastebin.com/XWtD9EyF Relevant log segment begins 7/18 at around 11:30, as that's when the preclear script finished and i added it into the array. /dev/sdf is the 1.5 TB drive in question.
July 18, 201114 yr Apologies, i should've thought to include that to begin with. I'm currently running Unraid 5.0B7 (happened to be the latest version available at time of purchase), and the syslog pastebin is available here: http://pastebin.com/XWtD9EyF Relevant log segment begins 7/18 at around 11:30, as that's when the preclear script finished and i added it into the array. /dev/sdf is the 1.5 TB drive in question. Try updating to the latest 5.0b9 release and see if that fixes the issue. If it does not post back here with another syslog.
July 18, 201114 yr I think you have to reboot or something like that. The new space is there even if it's not showing. Peter
July 18, 201114 yr And some of the 5b7 and 5b8 versions were not showing/updating free space - which I believe is fixed in 5b9. As lionelhutz said, a reboot would sometime fix this, but a pain. Shawn
July 18, 201114 yr Author Happy to report that upgrading to 5.0B9 fixed the problem (or just rebooting did, either way, i'm back up and running!). Thanks a ton guys!
Archived
This topic is now archived and is closed to further replies.