Jump to content
XPEnology Community

Need a favor please


Diverge

Recommended Posts

Can someone who has xpenology setup in ESXI, or possibly any setup w/ a SHR array do me a favor and SSH into their box and run this command and paste the output here?

 

sfdisk -l 

 

And also:

fdisk -l

 

I need to see how the partitions are laid out. I'm trying to repair my arrays partition tables. Thanks in advance :smile:

Edited by Guest
Link to comment
Share on other sites

This is what mine looks like. Hope that helps.

 

ESXi> sfdisk -l
/dev/sda1	            256	        4980735	        4980480	 fd  
/dev/sda2	        4980736	        9175039	        4194304	 fd  
/dev/sda3	        9437184	     1953511007	     1944073824	  f  
/dev/sda5	        9453280	      488383007	      478929728	 fd  
/dev/sda6	      488399104	      976759007	      488359904	 fd  


/dev/sdb1	            256	        4980735	        4980480	 fd  
/dev/sdb2	        4980736	        9175039	        4194304	 fd  
/dev/sdb3	        9437184	      976759007	      967321824	  f  
/dev/sdb5	        9453280	      488383007	      478929728	 fd  
/dev/sdb6	      488399104	      976759007	      488359904	 fd  


/dev/sdc1	            256	        4980735	        4980480	 fd  
/dev/sdc2	        4980736	        9175039	        4194304	 fd  
/dev/sdc3	        9437184	      488383007	      478945824	  f  
/dev/sdc5	        9453280	      488383007	      478929728	 fd  


/dev/md01	              0	        4980351	        4980352	  0  


/dev/md11	              0	        4194175	        4194176	  0  


Error: /dev/md2: unrecognised disk label
get disk fail


Error: /dev/md3: unrecognised disk label
get disk fail


Link to comment
Share on other sites

Thankyou! That helps me a lot.

 

One question about your setup. I see it is a 3 disk array. But how many data volume partitions do you have within DSM? Just one, or two?

 

My guess is 2, since it mentions md2 and md3 and there looks to be 2 logical partitions (sda5 and sda6).

Link to comment
Share on other sites

link > https://dl.dropboxusercontent.com/u/348 ... torage.jpg

 

 

SYNOLOGY> sfdisk -l

 

/dev/sda1                   256         4980735         4980480  fd
/dev/sda2               4980736         9175039         4194304  fd
/dev/sda5               9453280      5860519007      5851065728  fd


/dev/sdb1                   256         4980735         4980480  fd
/dev/sdb2               4980736         9175039         4194304  fd
/dev/sdb5               9453280      5860519007      5851065728  fd


/dev/sdc1                   256         4980735         4980480  fd
/dev/sdc2               4980736         9175039         4194304  fd
/dev/sdc5               9453280      5860519007      5851065728  fd


/dev/sdd1                   256         4980735         4980480  fd
/dev/sdd2               4980736         9175039         4194304  fd
/dev/sdd5               9453280      5860519007      5851065728  fd


/dev/sde1                   256         4980735         4980480  fd
/dev/sde2               4980736         9175039         4194304  fd
/dev/sde5               9453280      5860519007      5851065728  fd


/dev/sdf1                   256         4980735         4980480  fd
/dev/sdf2               4980736         9175039         4194304  fd
/dev/sdf5               9453280      5860519007      5851065728  fd


/dev/md01                     0         4980351         4980352   0


/dev/md11                     0         4194175         4194176   0


Error: /dev/md2: unrecognised disk label
get disk fail


/dev/sdv1                    63           32129           32067  83

Link to comment
Share on other sites

Thanks 'interested'!

 

This throws me in a loop and confuses me. Your array doesn't have an sdx3 partition.

 

Basically I'm trying to piece back together my array, without knowing all the partitions that existed. My array in it's broken state consisted of the following:

DiskStation> sfdisk -l
/dev/sda1                   256         4980735         4980480  fd
/dev/sda2               4980736         9175039         4194304  fd
/dev/sda3               9437184      3907015007      3897577824   f


/dev/sdb1                   256         4980735         4980480  fd
/dev/sdb2               4980736         9175039         4194304  fd


/dev/sdc1                   256         4980735         4980480  fd
/dev/sdc2               4980736         9175039         4194304  fd


/dev/md01                     0         4980351         4980352   0


/dev/md11                     0         4194175         4194176   0

 

With testdisk I found my data partition. I confirmed that I did find my data partition, by manually putting it together using losetup. Got all my data off it, and now trying to fix it to learn how. I outlined what I did here if anyone is interested: http://forum.synology.com/enu/viewtopic ... 15&t=71546

 

Based on graymouser's info I wrote a new partition table to all my drives. I assume my array consisted of the DSM partition sd[abc]1, the swap sd[abc]2, then an extended partion sd[adb]3. then logical partition sd[abc]5. Everything I had correlated to graymousers array setup, but he had different sized drives, so his end point for his data partition is different. But I don't know why I can't build the array manually with the new sd[abc]5 partitions vs creating loop devices w/ losetup. I can still see my data if I create loop devices again and assemble the array with them rather then the partitions.

 

Here's my current setup w/ my recently rewritten partition tables:

 

DiskStation> sfdisk -l
/dev/sda1                   256         4980735         4980480  fd
/dev/sda2               4980736         9175039         4194304  fd
/dev/sda3               9437184      3907015007      3897577824   f
/dev/sda5               9453280      3907012583      3897559304  fd


/dev/sdb1                   256         4980735         4980480  fd
/dev/sdb2               4980736         9175039         4194304  fd
/dev/sdb3               9437184      3907015007      3897577824   f
/dev/sdb5               9453280      3907012583      3897559304  fd


/dev/sdc1                   256         4980735         4980480  fd
/dev/sdc2               4980736         9175039         4194304  fd
/dev/sdc3               9437184      3907015007      3897577824   f
/dev/sdc5               9453280      3907012583      3897559304  fd


/dev/md01                     0         4980351         4980352   0


/dev/md11                     0         4194175         4194176   0

 

The only thing I can think of is somehow I have the wrong end point for partition 5.

 

Any expert advice is welcome, and more sfdisk -l info from other peoples systems will be helpful :smile:

Link to comment
Share on other sites

Thankyou! That helps me a lot.

 

One question about your setup. I see it is a 3 disk array. But how many data volume partitions do you have within DSM? Just one, or two?

 

My guess is 2, since it mentions md2 and md3 and there looks to be 2 logical partitions (sda5 and sda6).

 

I have 1 data volume partition. I'm not sure about md2 or md3 but I can do some investigation when I get home tonight.

Link to comment
Share on other sites

Thankyou! That helps me a lot.

 

One question about your setup. I see it is a 3 disk array. But how many data volume partitions do you have within DSM? Just one, or two?

 

My guess is 2, since it mentions md2 and md3 and there looks to be 2 logical partitions (sda5 and sda6).

 

I have 1 data volume partition. I'm not sure about md2 or md3 but I can do some investigation when I get home tonight.

 

Thanks for the reply. Things just got even weirder, but I'm still curious on how this all works. Eventually if I can't figure it out or corrupt the drive contents I'm gonna start over fresh (since I have all the data off it now), so I'll see how my partition layout is supposed to be and how it differs from everyone who posts here.

Link to comment
Share on other sites

Can you guys that posted your info also do a:

fdisk -l

 

so I can see partition types :smile: Maybe I created my #5 partition with the wrong type.

 

SYNOLOGY> fdisk -l
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sdb: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1      267350  2147483647+ ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sdc: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdc1               1      267350  2147483647+ ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sdd: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdd1               1      267350  2147483647+ ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sda: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      267350  2147483647+ ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sdf: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdf1               1      267350  2147483647+ ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sde: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sde1               1      267350  2147483647+ ee EFI GPT

Disk /dev/sdv: 4004 MB, 4004511744 bytes
255 heads, 63 sectors/track, 486 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks  Id System
/dev/sdv1   *           1           2       16033+ 83 Linux

Link to comment
Share on other sites

Like you see, all my hardware is written in my signature.

 

I have to admit, that I did have some problems in the beginning with DSM4.1-2668, but the good people on this forum helped me ...

 

With this hardware I can run almost everythink & the comsumption is low - now with 6x3TB disk > 55W.

 

What can I say, I love it ....

 

https://dl.dropboxusercontent.com/u/34829066/Synology/Slike/E3222327.JPG

 

Regards.

Link to comment
Share on other sites

Like you see, all my hardware is written in my signature.

 

I have to admit, that I did have some problems in the beginning with DSM4.1-2668, but the good people on this forum helped me ...

 

With this hardware I can run almost everythink & the comsumption is low - now with 6x3TB disk > 55W.

 

What can I say, I love it ....

 

https://dl.dropboxusercontent.com/u/34829066/Synology/Slike/E3222327.JPG

 

Regards.

 

Nice, I have a Lian-LI PC-V354 collecting dust. Been thinking maybe I should build my EXSI into it, and ditch the smaller Lian LI Q16 (since I don't really need it at my TV for WMC anymore, using virtualized windows and a Xbox 360 for WMC extender).

Link to comment
Share on other sites

×
×
  • Create New...