December 4, 200718 yr I was trying to get a understanding of user share and trying to figure out how to get the directories to sit at the root level. I changed a few shares here and there. Then I tried to take the array offline, and I wasn't even paying attention much when I clicked on the button. Then next thing I know, the free space column for disk2 just became "Unformatted"!!! What did I just do? I don't remember getting a prompt to do something to disk2. This alarms me quite a bit. Why was it so easy to destory a disk? Granted, it was operator error, but it's a bit too easy! Can it be brought back? Fortunately, I had just finished copying disk2 yesterday so the original files are still there. But what did I just do? I want to make sure I don't do it by accident again!
December 4, 200718 yr Author Ok, after a quick search, it appears that the gui just got confused and I might have clicked on refresh too quickly after I took the array offline. Someone had a similar problem, and fortunately I didn't format the disk, I just took it offline and brought it back up. It showed up as if nothing happened... Is this a known bug? It freak the hell out of me.
December 4, 200718 yr If you click on the "stop" button to stop the array, and a file is in use or a terminal session has its working directory on that drive, then that drive won't unmount, so the array won't stop. But the other drives that do unmount will sometimes show as "unformatted" until the server or the array is stopped and restarted.
December 5, 200718 yr Author If you click on the "stop" button to stop the array, and a file is in use or a terminal session has its working directory on that drive, then that drive won't unmount, so the array won't stop. But the other drives that do unmount will sometimes show as "unformatted" until the server or the array is stopped and restarted. That's exactly it, I had a telnet session in /mnt/disk1. For some reason it's disk2 that showed up as unformatted. After getting of /mnt, I was able to stop the array properly.
August 1, 200817 yr Just fyi i hit this bug in 4.3.3. 8 out of 10 disks showed as unformatted. Disproportionately scary bug
Archived
This topic is now archived and is closed to further replies.