If your Debian system has a firewall set up iptables you will need to allow access for port Now all we need to do is head back to our windows machine and fire up the iSCSI initiator as admin. Enter the ip of the target in the example Your target should show up in the Discovered targets section. If not, click Auto Configure.
You should see a new drive letter which points to the iSCSi target and you should now be able to move your files to a network or local drive. Once your data is moved off the RAID drives and verified good! Not for me sorry. Fool me once…yada yada.. You could void your warranty and install a version of linux to replace the OS. Note the possibility of bricking the unit is reasonably high.
Lastly, you could tuck the debian system you just built with the 4 external drives in a closet or server room and use that as your RAID5 file storage. Filed under Sides. Dear sir, I have the same problem as what you describe.
Unfortunately I am not as technical as you are. Do you have any other way to solve the problem? James Wong. Thank you JayB for suggesting my remote data recovery service. Linux mdadm software RAID recovery is my speciality. And yes I work from donations so the cost is low and not an issue. Hi there Thank you for your post! Disk1 had an error and now, the Volume can not be found. The software costs about EURO but you can test it before you have to buy it.
After you purchase the product, filesize is unlimited. In my case, the lost volume was rebuilt in a few seconds and i got all my data restored. I had 4TB data on the volume. I think Euro was worth it. Great news! Then it was only a matter of time until the copy process of 4TB data was finished. I have this same Seagate 4-bay NAS and drive 3 experienced a failure, but I was able to bring it back online after simply re-seating it. However, all of my data seems to be lost. Thanks for your help!
Couple of things. You will need 4 docks well you can do it with 3 to be able to access the data. Remember that your data is spread across ALL drives. You need to be able to mount at least 3 disks of the RAID array. First thing I would try is to power off the unit, and reseat the 2 drives.
There does seem to be a problem with them coming loose. Power back up and hopefully that solves your problem. NAS was working fine and accessing all the information, fault number 3 hard drive change and work well as a whole day, the next day the number Disk 2 fails, the disks reported me they were good, reassemble it, but missed the volume, all 4 discs are good ….
I have root access and installed mdadm, lvm2. The problem was that the Ext4 file system had a block size of My Debian live OS could only read block sizes at biggest.
So i googled for a solution and found a package called fuseext2 that can emulate the block size for the OS. I hope this helps anyone else having similar problems.
Thanks for posting that! Hope it helps someone else. Thanks again. I have been having problems getting Debian installed so I used CentOS, but have hit this block size issue. Have you any experience of this on CentOS 6? Well this time round the same Seagate NAS as before has had one drive fail, whereas the last time I had a problem no drives had failed but the NAS configuration had become corrupt.
I then swapped out the damaged drive for a brand new one as it was still under warranty. There was a button to adopt it so I clicked it. At this point I was very irritated that there was no place to be found where I could repair the raid 5 from within the NAS configuration page.
I followed the same steps as before Debian 7. Big smile after that. So I gave it a shot just for fun. I wanted to let you folks know that there is this feature hidden in the system. But I think the NAS needs to adopt the new drive first and then reboot before it will show the repair raid action. Regardless I would not trust it without having a spare backup of the data in case something goes wrong. Sorry late response: So I waited for the Raid 5 to rebuild after clicking the action button in the storage manager.
When I went to check the shared folders there were none. And when I navigated to the Seagate NAS from a windows machine there seemed like there were no files or folders on the system. This puzzled me because I could see that there was space being used but no files to see. So i started re-creating the same shared folders as there were before. Interestingly as the folders were created, they were populated with the original files.
So it did actually recover the files, but it did not keep the shared folder permissions. Needless to say that is a shit system and I will be migrating all the files onto a Linux file sharing server.
Thank you so much for this article and the details. I reached the 2nd assemble command and received a different message. I then took the 4 drives back to the BA and they started back up. Thanks for the article. However when I look at the array status for each of the drives one of the drives is different. They all show to be part of the same raid 5 array, they all show a clean status, but the first drive shows a status of A. The other two drives show the array status as AAA. The drive that shows two missing drives is device 2.
Any ideas? That may be a drive that has some bad sectors. However, I am able to see it and have successfully imaged all 3 drives. Please help if you have any ideas. It does not support ext4 extents, which the filesystem on the NAS will use. Any large files, such as the iscsi target LUN, will be using extents and will read as corrupted data using fuseext2 silently, even. Additionally, at that point, you can also optionally just mount the iscsi target directly instead of actually going through iscsi… the steps are basically:.
Thanks for the comment Vlad and the procedure. Just another reason to avoid the Live OS. However, none of the issues you described arose, and everything went very smoothly with no issues at all, even though after reading your problems, I was expecting major dramas. I bought it second-hand and it came with 3 x 1.
This is what happened. My NAS had 3 x 1. I used it on my home network i as a file server, and ii as a convenient place to store drive images of other computers while I worked on them.
The RAID 5 re-built itself without issues. Then last week, June , the 1. I decided to buy two new 2 TB drives, and replace both the remaining 1. I also planned to move the drive in Bay 4 back to Bay 3, but one step at a time.
It did the job flawlessly over the next 10 hours. My next task was to replace the 1. But then I read your article which described Drive 1 as being critical and having all the parity information on it. I was seriously concerned that if I removed Drive 1, and replaced it with a new empty drive, that the RAID would not work, and I would lose all my data.
I was impressed and relieved. Could it be that this firmware upgrade solves all the problems that led to the issues that you experienced? And because I have the spare empty drives, and I have lots of spare data that I could put onto them for testing, I can afford to scramble the RAID completely without fear of losing anything important.
Thanks again for your post, it has helped me understand the process of recovering data from RAIDs next time that I might need to. This issue with the product, is due to bugs in crappy firmware. This broke it even further… the web interface totally full of XML errors…. Another victim here, using a Seagate 4-drive Business Storage unit when drive 1 failed. Thanks for your article! Another, related problem has begun to appear with this product.
This is the issue of disk errors. The disk drive in mine, has bad sectors, and somewhat large sections of them in close proximity to each other 2TB drive. The crashed state is quite distinct the power button does nothing, and the buttons on the front panel do nothing, the stuff on the LCD remains static.
The only way to recover from this is to power-cycle the unit, and if you have it set-up to e-mail you status reports, it will send you a mail saying there was an abnormal error condition. But nobody has really done this. Hi, thanks for the guide, I have almost done it! There is just one more step to do: access the iSCSI disks from network.
Is there some other way? Is it possible to copy the LUN files to some other computer and try to mount them from there? Wanted to add my thanks for this post.
In addition, Drive 1 was the first failed drive on my unit, which left the BlackArmor admin GUI unavailable for me when Drive 2 reported a failure. Using your post as a guideline, I was able to build a Debian system and install the four drives in my gaming rig — which had plenty of available SATA ports — and behold! I found that only one drive was actually failed, got LVM to mount the array as a VG, and there was my data! I got through it without too much difficulty, and am currently recovering my data onto a clean device.
Seagate should be ashamed for their crap product and crappier support. This experience has pretty well cured me of buying another Seagate product for my home use. So happy I was able to help. Thanks so much for this! Managed to recover all required info from our little office NAS using the Debian approach. Anyway — thanks again for the excellent write up! You are commenting using your WordPress. You are commenting using your Google account.
You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. This site uses Akismet to reduce spam. Double-click the BlackArmor Discovery icon on your computer's Desktop. The application searches your company's computer network for BlackArmor servers and displays the devices in a list. The server's user interface opens.
Leave BlackArmor Manager open. A setup wizard opens for customizing your BlackArmor server. Follow the on-screen prompts to assign a unique name to your BlackArmor server to identify it on your network, enter a description for the server, set the device's time, and set up a unique password for the server. The BlackArmor Manager's main screen returns. Enter the person's full name and select administrator rights.
Click "Media" for the service you want the user to have access to on the server, as well as any other service listed within the new user wizard.
Enter a name for the sharing folder and a short description so others can recognize it on your computer's network. NFS Network File System lets the server retrieve and share files from different types of computers, such as those running Unix or Linux.
Click on the name of your BlackArmor server under the Volume heading you want to share. Nick Davis is a freelance writer specializing in technical, travel and entertainment articles. He holds a bachelor's degree in journalism from the University of Memphis and an associate degree in computer information systems from the State Technical Institute at Memphis.
He is currently living in Albuquerque, N.
0コメント