Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Physical:
500GB and 2TB drive in my DNS-323 w/ fw v.109.
Logical:
RAID-1 (maximum size) 498G across the 500GB and 2TB drive, the remaining 1.5TB was set to JBOD. All ext2.
What works:
I can mount the RAID-1 partition of either 500GB or 2TB drive
root@ubuntu:/# mount -t ext2 /dev/sda2 /mnt/1
root@ubuntu:/# ls -al /mnt/1
total 4198436
drwxrwxrwx 9 root root 4096 2010-11-20 17:36 .
drwxr-xr-x 4 root root 80 2010-11-20 23:41 ..
<deleted>
drwx------ 2 root root 4096 2010-11-20 23:23 .systemfile
What doesn't work:
Since the JBOD consists entirely from the 2TB volume shouldn't it contain all that is needed to mount the volume?
I cannot mount the JBOD partition of the remaining 2TB drive
root@ubuntu:/# mount -t ext2 /dev/sda3 /mnt/2
mount: wrong fs type, bad option, bad superblock on /dev/sda3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
root@ubuntu:/# fdisk /dev/sda
The number of cylinders for this disk is set to 121604.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sda: 1000.2 GB, 1000227396608 bytes
255 heads, 63 sectors/track, 121604 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 66 530113+ 82 Linux swap / Solaris
/dev/sda2 131 60702 486544590 83 Linux
/dev/sda3 60703 243201 1465923217+ 83 Linux
/dev/sda4 67 130 514080 83 Linux
Partition table entries are not in disk order
Command (m for help):
Any ideas?
Offline
NFN_NLN wrote:
Physical:
Any ideas?
This is closest I've come so far:
root@ubuntu:/home/ubuntu# mdadm --build /dev/md0 -l linear -n 1 /dev/sdb3
mdadm: '1' is an unusual number of drives for an array, so it is probably
a mistake. If you really mean it you will need to specify --force before
setting the number of drives.
root@ubuntu:/home/ubuntu# mdadm --build /dev/md0 -l linear -n 1 /dev/sdb3 --force
mdadm: array /dev/md0 built and started.
root@ubuntu:/home/ubuntu# mdadm --detail /dev/md0
/dev/md0:
Version :
Creation Time : Sun Nov 21 02:56:13 2010
Raid Level : linear
Array Size : 1465923200 (1398.01 GiB 1501.11 GB)
Raid Devices : 1
Total Devices : 1
Preferred Minor : 0
Update Time : Sun Nov 21 02:56:14 2010
State : clean
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
Rounding : 64K
Number Major Minor RaidDevice State
0 8 19 0 active sync /dev/sdb3
root@ubuntu:/home/ubuntu# mkdir /ok
root@ubuntu:/home/ubuntu# mount /dev/md0 /ok
mount: unknown filesystem type 'linux_raid_member'
root@ubuntu:/home/ubuntu# mount -t ext2 /dev/md0 /ok
mount: /dev/md0 already mounted or /ok busy
"linux_raid_member" is the same thing I receive when I try to mount a RAID-1 volume but then I force it to ext2.
I thought I was on to something but it always says busy.
Does anyone know the mechanism for JBOD? They must use mdadm for linux?
Offline
FILE mdadm.conf:
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=1878593b:d3ce0c47:a1c9ccf7:62de83be
ARRAY /dev/md1 level=linear num-devices=2 UUID=87b46af0:b4dd436a:a5c0e208:407b46b2
FILE raidtab:
raiddev /dev/md0
raid-level raid1
nr-raid-disks 2
chunk-size 64
persistent-superblock 1
device /dev/sda2
raid-disk 0
device /dev/sdb2
raid-disk 1
raiddev /dev/md1
raid-level linear
nr-raid-disks 2
chunk-size 64
persistent-superblock 1
device /dev/sda3
raid-disk 0
device /dev/sdb3
raid-disk 1
Version 1.3
I found these files under /mnt/.systemfile
It appears to create a linear RAID by concatenating /dev/sda3 and /dev/sdb3 even though sda3 will effectively be 0 size. There must be some header details on sda3 that come first. Will try mounting w/ both disks in place.
Offline
I'm not sure if I understand what you're actually trying to do...
To mount your partitions (either raid or jbod) you should mount the /dev/mdX devices, not /dev/sdXX
Offline
bgravato wrote:
I'm not sure if I understand what you're actually trying to do...
To mount your partitions (either raid or jbod) you should mount the /dev/mdX devices, not /dev/sdXX
I was trying to recover the data from the JBOD portion of the disks, which I did:
root@ubuntu:/mnt/sda4/.systemfile# mdadm --assemble /dev/md1 -u 87b46af0:b4dd436a:a5c0e208:407b46b2 /dev/sda3 /dev/sdb3
mdadm: /dev/md1 has been started with 2 drives.
root@ubuntu:/mnt/sda4/.systemfile# mkdir /mnt/linear
root@ubuntu:/mnt/sda4/.systemfile# mount -t ext2 /dev/md1 /mnt/linear
root@ubuntu:/mnt/sda4/.systemfile# cd /mnt/linear/
root@ubuntu:/mnt/linear# ls
Media
root@ubuntu:/mnt/linear# cd Media/
The problem was the DNS-323 lays down the worst possible schema. With a 500G and 2TB drive I mirrored the 500GB and left the 1.5TB as JBOD. It DOES NOT create a single partition on the 2TB drive. I would consider this a major flaw. What's the point of 1.5TB being dependant on .5MB on the other drive?
Offline