![]() I tried specifying the filetype (I believe that it's ext4 but, just in case, tried ext, ext2 ext3 and ext4) with no luck. I create a directory /mnt/nas and do a #mount /dev/vg8/lv8 /mnt/nas, but it says wrong fstype. Another quick #lvscan and I can see it as active. I do an #lvdisplay and confirm that it's not active and confirm it with #lvscan, so I do #modprobe dm-mod and then #vgchange -ay. ![]() I install lvm2 and do an #lvmdiskscan and I can see my volume, 1.82TB. Again though, no worries, let's apt-get lvm2. I found the largest one (it's 1.82TB) at /dev/md118 and tried to mount it. I can now do a #cat /proc/mdstat and see my degraded arrays, there were a bunch of them (8). When I plugged the drive in, and got the anticipated 'this is part of a RAID volume' type error. That's where things went tango uniform and where I'm hoping that the (awesome) Spiceworks community can jump in and save me. I've got a bunch of Ubuntu boxes at the shop, so my plan was to plug the drive up, scp the data to another NAS and be up and going in short order. The lady at Seagate that I spoke with told me that I should be able to take one of the drives out of the NAS, plug it into a Linux box and retrieve my data. Ultimately, called Seagate and, after a few minutes, they confirmed that it was dead and they are sending a replacement (good thing). ![]() After a few minutes of troubleshooting, I tried connecting it to LAN1, no link. Yesterday, there was no link light on the NAS or on the switch. Ultimately, we just used LAN2 and left LAN1 unplugged. The device has 2 network cards in it and, initially, we were trying to bond them together but that never worked (access to it was faster with a single NIC rather than any configuration of both). It's been in use now since June of 2013 and yesterday just 'stopped'. We have a 2 bay Seagate NAS that has 2 2TB drives in RAID1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |