General NAS-Central Forums

Welcome to the NAS community
It is currently Sat May 27, 2017 7:18 pm

All times are UTC




Post new topic Reply to topic  [ 3 posts ] 
Author Message
PostPosted: Sat Jun 20, 2015 12:13 am 
Offline

Joined: Sat Jun 13, 2015 3:09 pm
Posts: 2
I wonder the Jedis @ nas-central
if someone can help me, I'll find him/her here.
2big2 2bigtroubletoo :(

it stopped working during files write.
2x2TB - RAID0

I followed this http://www.aandcp.com/lacie-2big-network-2-data-recovery and everything went well 'til
mount /dev/md5 /mnt

then I get
mount: can't find /dev/md5/mnt in /etc/fstab or /etc/mtab

the system is now a bit sick, the search in launcher doesn't list the apps any more, the shut down will hang. Some process keep running...
I did
mdadm --stop /dev/md5

but
mdadm: Cannot get exclusive access to /dev/md5:Perhaps a running process, mounted filesystem or active volume group?


partition id's on disk0 look strange to me

fdisk -c=dos -u=cylinders -l /dev/sdb
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xc85fb34c

Device Boot Start End Blocks Id System
/dev/sdb1 1 250 2008093+ 5 Extended
/dev/sdb2 251 243201 1951503907+ 83 Linux
/dev/sdb5 1 32 256977 82 Linux swap / Solaris
/dev/sdb6 33 33 8001 83 Linux
/dev/sdb7 34 34 8001 83 Linux
/dev/sdb8 35 140 851413+ 83 Linux
/dev/sdb9 141 249 875511 83 Linux
/dev/sdb10 250 250 8001 83 Linux

... on disk 1
fdisk -c=dos -u=cylinders -l /dev/sdc
Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x3b3d05ec

Device Boot Start End Blocks Id System
/dev/sdc1 1 250 2008093+ 5 Extended
/dev/sdc2 251 243201 1951503907+ 83 Linux
/dev/sdc5 1 32 256977 82 Linux swap / Solaris
/dev/sdc6 33 33 8001 83 Linux
/dev/sdc7 34 34 8001 83 Linux
/dev/sdc8 35 140 851413+ 83 Linux
/dev/sdc9 141 249 875511 83 Linux
/dev/sdc10 250 250 8001 83 Linux


compared to the disk0 and disk1 on 2x250GB test set formatted with the procedure "Installing_firmware_on_fresh_disks_(2Big_2)"

fdisk -c=dos -u=cylinders -l /dev/sdd
Disk /dev/sdd: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000f26c1

Device Boot Start End Blocks Id System
/dev/sdd1 1 250 2008093+ 5 Extended
/dev/sdd2 251 30401 242187907+ fd Linux raid autodetect
/dev/sdd5 1 32 256977 fd Linux raid autodetect
/dev/sdd6 33 33 8001 83 Linux
/dev/sdd7 34 34 8001 fd Linux raid autodetect
/dev/sdd8 35 140 851413+ fd Linux raid autodetect
/dev/sdd9 141 249 875511 fd Linux raid autodetect
/dev/sdd10 250 250 8001 83 Linux

fdisk -c=dos -u=cylinders -l /dev/sde
Disk /dev/sde: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sde1 1 250 2008093+ 5 Extended
/dev/sde2 251 30401 242187907+ 83 Linux
/dev/sde5 1 32 256977 82 Linux swap / Solaris
/dev/sde6 33 33 8001 83 Linux
/dev/sde7 34 34 8001 83 Linux
/dev/sde8 35 140 851413+ 83 Linux
/dev/sde9 141 249 875511 83 Linux
/dev/sde10 250 250 8001 83 Linux

... and I guess changing partition ID's on the disk0 will destroy data...

Thanks a lot for any suggestion

by the way... I'm working with disk clones, not the originals. Clones has been done with a docking cloning station


Top
 Profile  
 
PostPosted: Sat Jun 20, 2015 7:59 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 5995
Quote:
mount /dev/md5 /mnt

then I get
mount: can't find /dev/md5/mnt in /etc/fstab or /etc/mtab
You made a typo, or your copy&paste behaves strange. The command is
Code:
mount <device> <mountpoint>
Your device is /dev/md5, the mountpoint is /mnt. But instead mount got a single argument /dev/md5/mnt, so the space in between is lost.

Mount *can* handle a single argument, in that case it searches the second one in a database, /dev/fstab. (If you always mount the same partition on the same mountpoint, this is nice). But of coutse /dev/md5/mnt is not in the database, hence the error.

The partition ID's are nothing to worry about. Actually they are ignored. Changing the id doesn't kill your data. It's still ignored.

Don't know about that 'mdadm --stop' error.


Top
 Profile  
 
PostPosted: Sat Jun 20, 2015 10:28 am 
Offline

Joined: Sat Jun 13, 2015 3:09 pm
Posts: 2
Hi Mijzelf, thanks so much for pay attention for so a stupid mistake... :oops:
I wrote it everywhere right but in terminal...
Now I'll look to find out and stop the process keeping /dev/md5, /dev/sdb2, /dev/sdc2 busy then reassemble and mount ;)


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 3 guests


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

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group