October 11, 200817 yr I feel like I may have seen something like this here, but I can't locate a resolution. I'm under 4.2.1. Here goes: Boot Up Array, everything is fine. Shut down array, insert new 1TB drive into slot 5 (Previously unoccupied) [slot 5 is motherboard controller port] Boot Up Array, Previously assigned Slot 15 with data now shows up as unassigned (I haven't assigned slot 5 yet, if I were to it would be an invalid expansion) Shut down array, remove new slot 5 drive Boot Up Array, everything is fine. It's peculiar that just the addition of the drive causes unRaid to freak out. Has anybody seen something similar? I'm still on 4.2.1 due to a 'if it ain't broke...' mentality. Would 4.3.x fix this? Just looking for a little guidance before I start mucking with data. Thanks
October 11, 200817 yr What do you mean by "slot"? Physical slots in your server and virtual slots in the unraid assignment page are only loosely correlated. Can't solve the specific problem, btw, but someone will pipe in to help you out. Bill
October 11, 200817 yr Author Looks like this was fixed between versions 4.3.2 and 4.3.3: Changes from 4.3.2 to 4.3.3 --------------------------- Bug fix: fixed problem where certain hard drives would be incorrectly seen as "missing". Changes from 4.3.1 to 4.3.2 --------------------------- Bug fix: if 16 or more disks connected, depending on the disks, system could improperly identify one or more disks. I have 4.4-Beta 2 online presently, and the problem has been resolved. If you see this issue, a software upgrade to 4.3.3. and beyond should take care of it.
Archived
This topic is now archived and is closed to further replies.