Any linux bods out there??

Mr_Toad

S0litaire wrote: »

The OP is connecting directly into the NAS via puTTy. so he should be able to mount the partition but it getting an error.

I understand that, I'm wondering why?

It's not the normal way to access a NAS device.

S0litaire

masonn wrote: »

I understand that, I'm wondering why?

It's not the normal way to access a NAS device.

It is if you need to do diagnostic test of the disks and to access the NAS's OS directly

The drives are not mounting so accessing the NAS directly is the only way (short of removing the drives) to access the drives.

Pauls

.......And finally I get back to my NAS trouble.

The drive in question is a western digital, mybook world edition 1TB with a single drive, just like this one

So I'm guessing I have a partition table issue?

Mondez

Try running "mdadm --examine --scan" and post what the output is. It looks like for whatever reason the raid device that the main data partition belongs to is either no longer recognised or no longer active. This command should tell us what raid devices there should be.

Pauls

Mondez wrote: »

Try running "mdadm --examine --scan" and post what the output is. It looks like for whatever reason the raid device that the main data partition belongs to is either no longer recognised or no longer active. This command should tell us what raid devices there should be.

~ # mdadm --examine --scan
mdadm: No devices listed in /etc/mdadm.conf

What it really means is that /etc/mdadm.conf doesn't exist


Update : I've just found this info which appears to be the same model drive (though my model no is wd10000h1nc-00). There's also this in case it helps

Mondez

Hmm, try "cat /proc/mdstat" and see what that says. While you are at it, let me know what "cat /etc/fstab" says too.

Pauls

Mondez wrote: »

Hmm, try "cat /proc/mdstat" and see what that says. While you are at it, let me know what "cat /etc/fstab" says too.

/etc # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1]
md1 : active raid1 sda2[0]
256896 blocks [2/1] [U_]

md3 : active raid1 sda3[0]
987904 blocks [2/1] [U_]

md2 : active raid1 sda4[0]
973522880 blocks [2/1] [U_]

md0 : active raid1 sda1[0]
1959872 blocks [2/1] [U_]

unused devices: <none>



and


/etc # cat /etc/fstab
cat: /etc/fstab: No such file or directory

Mondez

Try mounting /dev/md2, that looks like its the device that uses /dev/sda4. I'm guessing that this point you don't need telling how to use "cd" and "ls" to see if your data is there right?

Pauls

Mondez wrote: »

Try mounting /dev/md2, that looks like its the device that uses /dev/sda4. I'm guessing that this point you don't need telling how to use "cd" and "ls" to see if your data is there right?

I'm actually a developer by trade, I've dabbled in all sorts of stuff. I'm quite happy with the general unix stuff, but this is a bit more involved than I'm used to


My Mount is failing like so......

/dev # mount -t ext3 /dev/md2 /media/temp
mount: Mounting /dev/md2 on /media/temp failed: Invalid argument

When I list dev/md2 I'm getting this...........

/ # ls -l /dev/md2
brw-r

---

1 root root 9, 2 Jul 13 2010 /dev/md2

Mondez

Try mounting it without specifying -t ext3 and see if that makes a difference. You could also try running fsck.ext3 on it if it still won't mount to ensure it has a valid ext3 filesystem on it.