Tutorial: How to access DSM's Data & System partitions


Recommended Posts

  • 1 month later...
  • 1 month later...
On 4/8/2019 at 6:42 PM, XciD69 said:

Perfect, It's working.

 

Just take care, with ubuntu 18, mdadm had been updated and tutorial commands aren't working. Go on ubuntu 16

 

What is not working exactly so I can update the tutorial?

Link to post
Share on other sites

I installed Ubuntu 18.04.2 LTS (Bionic Beaver) and Ubuntu 18.10 (Cosmic Cuttlefish). Installed mdadm on both. Looked at the mdadm help and the -AU (--assemble --update) options seem to be available. The byteorder option under update seems to be available as well. Version of mdadm used is v4.1-rc1.

 

So I am not sure what you did or perhaps I am missing something.

Link to post
Share on other sites
  • 1 year later...
В 13.03.2017 в 07:20, Polanskiman сказал:

mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1

Dear, i can't mount system partition... (need a edit the /etc/default.....

i Have a 5 Disk named at sda,sdb,sdc,sdd,sde and this Single disk without RAID config.... SimpleRAID

after command mdadm -AU byteorder /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
 the system answer me "mdadm: device /dev/sda1 exists but is not an md array."

but after command sudo fdisk -l | grep /dev/sd  system answer is:
 

Disk /dev/sda: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sda1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sda2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sda3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sdc: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdc1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sdc2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sdc3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdb1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sdb2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sdb3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sdf: 111.81 GiB, 120034123776 bytes, 234441648 sectors
/dev/sdf1          2048   4982527   4980480   2.4G fd Linux raid autodetect
/dev/sdf2       4982528   9176831   4194304     2G fd Linux raid autodetect
/dev/sdf3       9437184 234236831 224799648 107.2G fd Linux raid autodetect
Disk /dev/sdd: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdd1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sdd2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sdd3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sde: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sde1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sde2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sde3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect

after mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /de
v/sde1 ...

mdadm: No super block found on /dev/sda1 (Expected magic a92b4efc, got fc4e2ba9)
mdadm: no RAID superblock on /dev/sda1
mdadm: /dev/sda1 has no superblock - assembly aborted

whats i am do wrong????

Edited by loveburn
Link to post
Share on other sites
  • 5 weeks later...
On 4/10/2021 at 1:21 PM, loveburn said:

Dear, i can't mount system partition... (need a edit the /etc/default.....

i Have a 5 Disk named at sda,sdb,sdc,sdd,sde and this Single disk without RAID config.... SimpleRAID

after command mdadm -AU byteorder /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
 the system answer me "mdadm: device /dev/sda1 exists but is not an md array."

but after command sudo fdisk -l | grep /dev/sd  system answer is:
 


Disk /dev/sda: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sda1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sda2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sda3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sdc: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdc1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sdc2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sdc3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdb1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sdb2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sdb3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sdf: 111.81 GiB, 120034123776 bytes, 234441648 sectors
/dev/sdf1          2048   4982527   4980480   2.4G fd Linux raid autodetect
/dev/sdf2       4982528   9176831   4194304     2G fd Linux raid autodetect
/dev/sdf3       9437184 234236831 224799648 107.2G fd Linux raid autodetect
Disk /dev/sdd: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sdd1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sdd2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sdd3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect
Disk /dev/sde: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sde1          2048    4982527    4980480  2.4G fd Linux raid autodetect
/dev/sde2       4982528    9176831    4194304    2G fd Linux raid autodetect
/dev/sde3       9437184 3906824351 3897387168  1.8T fd Linux raid autodetect

after mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /de
v/sde1 ...


mdadm: No super block found on /dev/sda1 (Expected magic a92b4efc, got fc4e2ba9)
mdadm: no RAID superblock on /dev/sda1
mdadm: /dev/sda1 has no superblock - assembly aborted

whats i am do wrong????

Having the exact same issue, did you find the solution??

Link to post
Share on other sites
  • 2 months later...

Hello,

 

I'm trying to mount my system disk only using 1 of the 4 disks on my Synology. The reason is, is that I need to fix a specific directory on the System drive which I accidently corrupted in my NAS.

 

If I run the command you mention though:

mdadm -AU byteorder /dev/md0 /dev/sda1

 

It shows me:

mdadm: No super block foudn on /dev/sda1: (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sda1
mdadm: /dev/sda1 has no superblock - assembly aborted

 

I'm really confused on what's going on here. I hope someone can help me :)?

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.