Jump to content
XPEnology Community

Pismo

Rookie
 View Profile  See their activity

  • Posts

    2

  • Joined

  • Last visited

 Content Type 

Posts posted by Pismo

    NEW DSM 5.1-5004 AVAILABLE !!

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hey Guys,

     

    i have installed DSM 5.1 on my test system and i did boot but without my drive getting mounted als already mentioned. (See attached image)

     

    But when i did some investigation of de log files (see relevant parts of DMESG below ) i found out that:

    - My disk is detected

    - (3) Partitions where created in a Raid 1 configuration

    - 2 of the 3 Partitions are mounted (SWAP en System)

    - the 3 one (data) is not mounted because is is missing a super block

     

    Could this be the reason why the disks are disappearing, and how can we over come the missing super block issue ?

     

    Login Screen Diskstation

    Post init
Init: Unable to mount /dev filesystem: No such device
=================== start  udevd ================
===trigger device plug event =====

DiskStation login:

     

    Fragment DMESG |GREP MD

    [    2.521864] md: Autodetecting RAID arrays.
[    2.557755] md: invalid raid superblock magic on sda3
[    2.557759] md: sda3 does not have a valid v0.90 superblock, not importing!
[    2.557768] md: Scanned 3 and added 2 devices.
[    2.557769] md: autorun ...
[    2.557771] md: considering sda1 ...
[    2.557776] md:  adding sda1 ...
[    2.557779] md: sda2 has different UUID to sda1
[    2.557783] md: created md0
[    2.557786] md: bind
[    2.557800] md: running: 
[    2.557881] md/raid1:md0: active with 1 out of 12 mirrors
[    2.557894] md0: detected capacity change from 0 to 2549940224
[    2.557929] md: considering sda2 ...
[    2.557932] md:  adding sda2 ...
[    2.558072] md: created md1
[    2.558073] md: bind
[    2.558081] md: running: 
[    2.558149] md/raid1:md1: active with 1 out of 12 mirrors
[    2.558163] md1: detected capacity change from 0 to 2147418112
[    2.558200] md: ... autorun DONE.
[    2.588148]  md1: unknown partition table
[    2.619514]  md0: unknown partition table
[    2.627526] EXT4-fs (md0): barriers disabled
[    2.664578] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: 
[    2.755146] Adding 2097084k swap on /dev/md1.  Priority:-1 extents:1 across:2097084k 
[   12.564551] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1
[   13.059297] EXT4-fs (md0): re-mounted. Opts: (null)
[   16.126338] Adding 2097084k swap on /dev/md1.  Priority:-1 extents:1 across:2097084k 

[   18.187065] systemd-udevd[12176]: starting version 204
[   19.844557] md: md2 stopped.
[   20.158934] ata1.00: cmd 60/08:00:08:00:90/00:00:00:00:00/40 tag 0 ncq 4096 in
[   20.336575] ata1.00: cmd 60/08:00:08:00:90/00:00:00:00:00/40 tag 0 ncq 4096 in
[   20.514303] ata1.00: cmd 60/08:00:08:00:90/00:00:00:00:00/40 tag 0 ncq 4096 in
[   20.691952] ata1.00: cmd 60/08:00:08:00:90/00:00:00:00:00/40 tag 0 ncq 4096 in
[   20.869715] ata1.00: cmd 60/08:00:08:00:90/00:00:00:00:00/40 tag 0 ncq 4096 in
[   21.047414] ata1.00: cmd 60/08:00:08:00:90/00:00:00:00:00/40 tag 0 ncq 4096 in
[   21.048569] md: disabled device sda3, could not read superblock.
[   21.048573] md: sda3 does not have a valid v1.2 superblock, not importing!
[   21.048580] md: md_import_device returned -22
[   21.049702] md: md2 stopped.
[   21.213691] md: md2 stopped.

     

    Very interesting as when you create an RAID1 under Linux with mdadm command you get the following hint for the bootloader:

    mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90

     

    So maybe nanoboot does create the RAID in a different way which isn't supported in DSM 5.1 anymore or uses an outdated version of madam.

    Or the kernel is too old.

     

    [root@localhost ~]# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1
mdadm: Note: this array has metadata at the start and
   may not be suitable as a boot device.  If you plan to
   store '/boot' on this device please ensure that
   your boot-loader understands md/v1.x metadata, or use
   --metadata=0.90
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
[root@localhost ~]#

     

    More Infos can be found here for example:

    http://www.thomas-krenn.com/de/wiki/Linux_Software_RAID

×
×
  • Create New...