NAS 200 Drives - How do I use Rescue CD ?

Discussion in 'Cisco/Linksys Network Storage Devices' started by Bryan O, Oct 8, 2011.

  1. Bryan O

    Bryan O Networkin' Nut Member

    Need some help. Noticed several of your posts and you have provided a lot of great content. My NAS200 has died... well won't respond. It seems to boot up and act like it is working, but I cannot communicate to it. I have tried several things... cables... IP addresses etc... but no luck. My router sees it, assigns it an IP address... but I cannot ping it, access through the web console or anything. Very weird...

    Anyways... I pulled the drives and I hooked them up to an secondary PC. I downloaded the Rescue CD you recommend and booted things up. But... I am not a Linux guy.

    I don't know what to do now. I am sure I need to mount the drive to access the content, but I have no idea how to do that. I am trying to fumble through the manual, but it is reading mostly Greek to me.

    Any help on accessing these drives would be a huge help... not to mention save my marriage because all of our digital photos were on the NAS200.

  2. jac_goudsmit

    jac_goudsmit Super Moderator Staff Member Member

    I'm sorry but working with SystemRescueCD requires some knowledge about working with Linux. I can't give you a simple how-to guide of how to copy your files, there are just too many steps involved and there are too many things that might happen, that I can't foresee in such a guide.

    Some hints to start with: I think SystemRescueCD tries to detect and mount all the drives it can find, so it should have mounted your NAS disks somewhere and it probably also mounted your PC's internal hard disks somewhere. You will need to find where the disks are, and then copy the important files to the other disk. You can use the mount command (without parameters) to see where everything is mounted but that won't tell you much if you can't read the output. Then you can copy your files using cp.

    I suggest you get some help from someone who knows more about Linux and who can come to your house to help you. Alternatively you could get a live Linux distro that has a GUI included so you can do things by just clicking and dragging.

    Anyway, if the NAS200 starts and gets an IP address, maybe it was just checking the disks and you didn't wait long enough to connect to it? With SystemRescueCD you can run the fsck program to check and fix the file systems on the disks MUCH faster, and then shut down cleanly so that when you put the disks back in the NAS it won't have to check and fix them again. If you can see on your router that the NAS is getting an IP address from the DHCP server, it proves that it's executing its startup scripts so it really is running. Don't give up!

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice