/i-data/md0 is not the actual mountpoint of the data partition. The actual mountpoint is /i-data/<Some-Hexcode>. /i-data/md0 is a symlink to symlink to the actual mountpoint. So it seems the 'in between' symlink isn't there.

Using

Code:

cat /proc/mounts

you can see where /dev/md0 is mounted, and use mc to have a look. If /dev/md0 is not mounted, mount it manually, and look if your files are there.

/i-data/md0 is not the actual mountpoint of the data partition. The actual mountpoint is /i-data/<Some-Hexcode>. /i-data/md0 is a symlink to symlink to the actual mountpoint. So it seems the 'in between' symlink isn't there.

Using

Code:

cat /proc/mounts

you can see where /dev/md0 is mounted, and use mc to have a look. If /dev/md0 is not mounted, mount it manually, and look if your files are there.

I guess you are accessing your box via telnet? In that case you have a limited shell, which doesn't support the function keys. As a work around you can use <ESC><5> instead of <F5>. Or enable sshd, and login over ssh, which gives you a more feature rich shell.

Actually I don't know. I have only experience with the NSA220 and NSA325, which both accept empty disks, and then can be initialized through the webpage. But I vaguely remember the the NSA210 needed some external software to initialize the disk in the NAS. But I can be mistaken.

Actually I don't know. I have only experience with the NSA220 and NSA325, which both accept empty disks, and then can be initialized through the webpage. But I vaguely remember the the NSA210 needed some external software to initialize the disk in the NAS. But I can be mistaken.

Who is online

Users browsing this forum: No registered users and 5 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum