On 10/18/2017 08:06 PM, dfc wrote: > On Wed, 2017-10-18 at 22:28 +0200, Rudy Zijlstra wrote: >> USB is indeed not the best choice. Rudy, you master of understatement! >>> My main question is whether inserting the 5 disks into another >>> JBOD chasis is likely to work? >> >> Yes, this should work. With a little luck you would not even need >> to force it, as with a component failure all disks should have >> lost connection at the same time. I would be shocked if these disk *won't* assemble. Assembly might need --force if any writes were in flight, but I doubt it. >> You could test each disk separately -- as long as you only read >> from them. Only reading is to ensure that no changes are done that >> make later > > Thanks, I will try reading disks and then install in a new chasis. Just put them in a chassis and try to assemble. If it succeeds, you are done. If assembly fails, report what mdadm had to say. >> re-build of the raid difficult. >>> In particular is mdadm "smart enough" to find all the components >>> and/or do I need to do something to help it along? In fact, our >>> IT person has suggested that the data may well be lost. >> >> Your IT person apparently either thinks the HW failure caused >> extensive damage, or wants you to do something different, or... is >> not very knowledgeable about this type of setup. Yeah, it does sound like somebody is out of their depth. >>> Also, since I first used the JBOD with software raid I came to >>> realize that the usb connection is not a good choice (though I >>> have never had problems). What sort of connection (at the low >>> price end of the market for HDD enclosures) would be better? >>> eSata or something else? >> >> eSATA would work. But depends on the type of enclusure you can get. >> I leave that to people based in USA, who know what is available >> there. eSATA with a port multiplier should be fine. It's spend a bit more for a JBOD with a SAS port and a suitable PCIe adapter. Phil -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
