I have the NSA 325 V2 and placed raid1 on disk1 while disk2 had not yet a volume
All Replies
-
mount: you must specify the filesystem type
Try
mount -t ext4 /dev/sda2 /mnt/mountpoint
sh: copy: not foundDid I really write copy? The command is cp.
0 -
/mnt/mountpoint # mdadm --stop /dev/md0 && mount -t ext4 /dev/sda2 /mnt/mountpoidmesntmdadm: stopped /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
/mnt/mountpoint #/mnt/mountpoint # cp -a * /i-data/3cc8587e/
cp: can't stat '*': No such file or directory
cp *cp
0 -
Just to clarify this was the original return information/mnt/mountpoint # mdadm --stop /dev/md0 && mount -t ext4 /dev/sda2 /mnt/mountpointmdadm: stopped /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
/mnt/mountpoint #/mnt/mountpoint # cp -a * /i-data/3cc8587e/
cp: can't stat '*': No such file or directory
0 -
What says
<div>mkdir /mnt/mountpoint</div><div><br></div><div>mdadm --stop /dev/md0 && mount -t ext4 /dev/sda2 /mnt/mountpoint</div><div><br></div><div>dmesg | tail<br></div>
0 -
Hi MijzelfI have entered~ # mkdir /mnt/mountpoint
mkdir: can't create directory '/mnt/mountpoint': File exists
~ # mdadm --stop /dev/md0 && mount -t ext4 /dev/sda2 /mnt/mountpoint
mdadm: stopped /dev/md0
dmesg mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or sodmesg | tailmd: md0 stopped######################################## HD0 awaked by mount ! #
#######################################
---> HD0 back to green on, off blink
Uncached vma c8cffb78 (addr 4028b000 flags 080000d5 phy 1dd32000) from pid 674
Uncached vma c8cffb78 (addr 4028b000 flags 080000d5 phy 1dd63000) from pid 674
Uncached vma c8cffb78 (addr 4028b000 flags 080000d5 phy 1dd60000) from pid 674
EXT4-fs (sda2): VFS: Can't find ext4 filesystem
~ #
0 -
Apparently it's not ext4. Try ext3 instead.
0 -
Hoi Mijzelf:BusyBox v1.17.2 (2017-06-23 10:40:08 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
~ # mdadm --stop /dev/md0 && mount -t ext2 /dev/sda2 /mnt/mountpoint
mdadm: stopped /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
~ # mdadm --stop /dev/md0 && mount -t ext3 /dev/sda2 /mnt/mountpoint
mdadm: stopped /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
~ # dmesg | tail
Uncached vma c8c59968 (addr 4028b000 flags 080000d5 phy 1dd32000) from pid 2111
Uncached vma c8c59968 (addr 4028b000 flags 080000d5 phy 1dd63000) from pid 2111
Uncached vma c8c59968 (addr 4028b000 flags 080000d5 phy 1dd60000) from pid 2111
VFS: Can't find an ext2 filesystem on dev sda2.
md: md0 stopped.
md: md0 stopped.
VFS: Can't find ext3 filesystem on dev sda2.
Uncached vma d750dc28 (addr 4028b000 flags 080000d5 phy 1dd32000) from pid 2256
Uncached vma d750dc28 (addr 4028b000 flags 080000d5 phy 1dd63000) from pid 2256
Uncached vma d750dc28 (addr 4028b000 flags 080000d5 phy 1dd60000) from pid 2256
~ # mount -t ext1 /dev/sda2 /mnt/mountpoint
mount: unknown filesystem type 'ext1'
~ # mdadm --stop /dev/md0 && mount -t ext1 /dev/sda2 /mnt/mountpoint
mdadm: stopped /dev/md0
mount: unknown filesystem type 'ext1'
~ # mdadm --stop /dev/md0 && mount -t ext2 /dev/sda2 /mnt/mountpoint
mdadm: stopped /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
~ # mdadm --stop /dev/md0 && mount -t ext3 /dev/sda2 /mnt/mountpoint
mdadm: stopped /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
~ # mdadm --stop /dev/md0 && mount -t ext4 /dev/sda2 /mnt/mountpoint
mdadm: stopped /dev/md0
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
~ # mdadm --stop /dev/md0 && mount -t ext5 /dev/sda2 /mnt/mountpoint
mdadm: stopped /dev/md0
mount: unknown filesystem type 'ext5'
~ # dmesg |tail
Uncached vma d750dc28 (addr 4028b000 flags 080000d5 phy 1dd63000) from pid 2256
Uncached vma d750dc28 (addr 4028b000 flags 080000d5 phy 1dd60000) from pid 2256
md: md0 stopped.
md: md0 stopped.
VFS: Can't find an ext2 filesystem on dev sda2.
md: md0 stopped.
VFS: Can't find ext3 filesystem on dev sda2.
md: md0 stopped.
EXT4-fs (sda2): VFS: Can't find ext4 filesystem
md: md0 stopped.
0 -
Right. So sda2 doesn't contain a valid ext[12345] volume. (ext5 doesn't exist, AFAIK, and ext1 was called ext. Don't know if that is still supported. ext2 is old).Your first post on June 17 tells md0 contains an ext[234] filesystem, and your last post on June 18 tells sda2 is (the only) member of md0. So I must be mistaken in my assumption that the start of the partition is also the start of the filesystem.Can you post the output of
mdadm --examine /dev/sd?2
How old was the existing raid array, before you converted it?0 -
Mijzelf:Here is the output:/dev/sda2:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : fe6cce5e:c2787799:d330641f:892b916a
Name : NSA325-v2:0 (local to host NSA325-v2)
Creation Time : Sat Jun 15 10:49:19 2019
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 976244928 (931.02 GiB 999.67 GB)
Array Size : 976244792 (931.02 GiB 999.67 GB)
Used Dev Size : 976244792 (931.02 GiB 999.67 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 870f56e2:da90ec23:6f0b1722:abde0849
Update Time : Mon Jun 17 19:52:15 2019
Checksum : e934af94 - correct
Events : 366
Device Role : Active device 0
Array State : A. ('A' == active, '.' == missing)
/dev/sdb2:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 3cc8587e:22cbb2ab:fead2960:f311196e
Name : NSA325-v2:1 (local to host NSA325-v2)
Creation Time : Sat Jun 15 10:56:37 2019
Raid Level : linear
Raid Devices : 1
Avail Dev Size : 1952996928 (1862.52 GiB 1999.87 GB)
Used Dev Size : 0
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : fc4704f1:da35344d:bef3f7f7:b2385146
Update Time : Sat Jun 15 10:56:37 2019
Checksum : 6a743ae0 - correct
Events : 0
Rounding : 0K
Device Role : Active device 0
Array State : A ('A' == active, '.' == missing)
mdadm: cannot open /dev/sdc2: No such device or address
mdadm: cannot open /dev/sdd2: No such device or address
mdadm: cannot open /dev/sde2: No such device or address
mdadm: cannot open /dev/sdf2: No such device or address
mdadm: cannot open /dev/sdg2: No such device or address
mdadm: cannot open /dev/sdh2: No such device or address
mdadm: cannot open /dev/sdi2: No such device or address
mdadm: cannot open /dev/sdj2: No such device or address
mdadm: cannot open /dev/sdk2: No such device or address
mdadm: cannot open /dev/sdl2: No such device or address
mdadm: cannot open /dev/sdm2: No such device or address
mdadm: cannot open /dev/sdn2: No such device or address
mdadm: cannot open /dev/sdo2: No such device or address
mdadm: cannot open /dev/sdp2: No such device or address
mdadm: cannot open /dev/sdq2: No such device or address
mdadm: cannot open /dev/sdr2: No such device or address
mdadm: cannot open /dev/sds2: No such device or address
mdadm: cannot open /dev/sdt2: No such device or address
mdadm: cannot open /dev/sdu2: No such device or address
mdadm: cannot open /dev/sdv2: No such device or address
mdadm: cannot open /dev/sdw2: No such device or address
mdadm: cannot open /dev/sdx2: No such device or address
mdadm: cannot open /dev/sdy2: No such device or address
mdadm: cannot open /dev/sdz2: No such device or addressBefore the conversion the NAS was only a one TB drive. I added another 2Tb drive and tried to convert the one TB Drive to Raid1.
0 -
<quote>Before the conversion the NAS was only a one TB drive. I added another 2Tb drive and tried to convert the one TB Drive to Raid1.</quote>But how old was it?Here you see an array of my 325:
/dev/sda2:<br> Magic : a92b4efc<br> Version : 0.90.00<br> UUID : 3a22b091:bc91e802:3febb798:91bfbafd<br> Creation Time : Fri May 4 21:08:15 2012<br> Raid Level : linear<br> Raid Devices : 1<br> Total Devices : 1<br>Preferred Minor : 0<br><br> Update Time : Fri May 4 21:08:15 2012<br> State : active<br> Active Devices : 1<br>Working Devices : 1<br> Failed Devices : 0<br> Spare Devices : 0<br> Checksum : 10d4ace4 - correct<br> Events : 1<br><br> Rounding : 64K<br>
As you can see it is created in 2012, andt uses metadata version 0.90.00, while your linear array sdb2, created in 2019, uses metadata version 1.2. So apparently ZyXEL switched default metadata version somewhere in this years.That matters, as you can read here. For 0.9 the header is at the end, and for 1.2 the header is at the start. So if the firmware converted an 0.9 linear array to an 1.2 raid1 array by simply re-creating the array, it has overwritten the start of the filesystem.I think that can be repaired, ext3/4 is quite a robust filesystem, but repairing a filesystem from an wrong assumed data start is not a good idea, of course.Do you have an extra (external?) harddisk of at least 1TB which could be used? In that case we could create a bit-by-bit copy of the disk from the start of the partition, and try to repair that, and if that fails create a copy from the current start of the filesystem, and try to repair that.
0
Guru Member
Freshman MemberCategories
- All Categories
- 414 Beta Program
- 2.3K Nebula
- 132 Nebula Ideas
- 92 Nebula Status and Incidents
- 5.4K Security
- 183 USG FLEX H Series
- 258 Security Ideas
- 1.4K Switch
- 71 Switch Ideas
- 1K Wireless
- 37 Wireless Ideas
- 6.2K Consumer Product
- 237 Service & License
- 374 News and Release
- 79 Security Advisories
- 24 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2.9K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 80 About Community
- 69 Security Highlight
