[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 22/10/10 09:46, Paul Hirst wrote:
On Thu, 2010-10-21 at 23:01 +0100, Rob Beard wrote:You might want to try mdadm -A /dev/md1 --level=linear /dev/sdd /dev/sdeDoesn't the software RAID stuff write some metadata to the end of the device? You might overwrite something you intended to keep. How much this matters to you depends on how much you really want the data back. If you just want to try something simple and aren't too fussed if you trash the disks then it's worth giving it a go. However I noticed that the stock nbd-server program has a multiple file option so I suspect you could make use of that. I notice there is an nbd-server package in the Ubuntu repositories (I don't recall which distro you are using)
I've given it a quick try but not had much luck...I'm running Ubuntu 10.10 on my laptop, 8.04 on my server and I booted my wife's PC from an Ubuntu 10.10 Live CD.
I've managed to get nbd working, at least to the point where it will connect but it's only seeing one drive.
Reading the man page it looks to me like I have to name the devices sequentially, so I symlinked /dev/sda to /dev/drive0 and /dev/sdb to /dev/drive1
I then ran the command... nbd-server 1083 /dev/drive0 -r -m It didn't give any output but according to ps it was running. I then connected from my server using nbd-client... nbd-client 192.168.0.2 1083 /dev/nbd0 I get the output: Negotiation: ..size = 488386584KB bs=1024, sz=488386584When I do an fdisk -l it doesn't show up the nbd device however if I run fdisk /dev/nbd0 I get this:
Disk /dev/nbd0: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x66a2b67c
Device Boot Start End Blocks Id System
/dev/nbd0p1 1 121602 976768033+ 83 Linux
I then tried mounting /dev/nbd0 and that asked me to specify a
filesystem type (so I tried ext3). That didn't work.
I then tried mounting /dev/nbd0p1 and it came up with an error saying the special device /dev/nbd0p1 doesn't exist.
So I'm a bit stuck now.Either way it only seems to be detecting a 500GB drive. However on the machine running nbd-server both drives are detected as 500GB drives.
Rob -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq