NAS326 problem - part 2 - help is needed - Volume is down
        
            Options        
            
        
                
                    Janikovo                
                
                    Posts: 24 
  Freshman Member                
            
                        
            
  Freshman Member                
            
                    Hello all,
and especially @Mijzelf
You probably know my problem with one faulty disk on NAS326 (linear, jbod).
Look here: https://homeforum.zyxel.com/discussion/3827/nas326-problem/p1
Problem is how to "assemble" NAS volume (or array back) without losing data.
So, I managed with ddrescue copied 99.999% of that faulty disk to the news HDD same size.
Installed the new disk to NAS, but the situation is as follows:










What should I do now ?
Please an advice
and Thanks.
#NAS_June_2020
                
                and especially @Mijzelf
You probably know my problem with one faulty disk on NAS326 (linear, jbod).
Look here: https://homeforum.zyxel.com/discussion/3827/nas326-problem/p1
Problem is how to "assemble" NAS volume (or array back) without losing data.
So, I managed with ddrescue copied 99.999% of that faulty disk to the news HDD same size.
Installed the new disk to NAS, but the situation is as follows:










What should I do now ?
Please an advice
and Thanks.
#NAS_June_2020
0    
            All Replies
- 
            The array is assembled, but it fails to mount. So try running fsck:e2fsck /dev/md20
 - 
            OK,
i tried add -n to e2fsck
and it show this:~ # e2fsck -n /dev/md2e2fsck 1.42.12 (29-Aug-2014)Warning! /dev/md2 is in use.ext2fs_open2: Bad magic number in super-blocke2fsck: Superblock invalid, trying backup blocks...e2fsck: Bad magic number in super-block while trying to open /dev/md2The superblock could not be read or does not describe a valid ext2/ext3/ext4filesystem. If the device is valid and it really contains an ext2/ext3/ext4filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock:e2fsck -b 8193 <device>ore2fsck -b 32768 <device>
btw:
mdadm --stop /dev/md2:~ # mdadm --stop /dev/md2mdadm: Cannot get exclusive access to /dev/md2:Perhaps a running process, mounted filesystem or active volume group?So, I cant stop md2
How could I assemble volume (array) without losing data ?0 - 
            So, I cant stop md2
You can't stop md2, because it's busy. md2 is not mounted, so there must be something else. I should have looked further, apart from md2 there is also a dm-1 in /proc/partitions, which is slightly smaller than md2. So inside your raid array there is a 'logical volume', and that logical volume is the one containing the file system.
So try
e2fsck /dev/dm-1
I am not sure if that dm-1 devicenode is inside /dev/. If /dev/dm-1 cannot be found, try
find /dev/ grep dm
to find the path to the devicenode.
0 
Categories
- All Categories
 - 439 Beta Program
 - 2.8K Nebula
 - 200 Nebula Ideas
 - 126 Nebula Status and Incidents
 - 6.3K Security
 - 499 USG FLEX H Series
 - 323 Security Ideas
 - 1.6K Switch
 - 84 Switch Ideas
 - 1.3K Wireless
 - 49 Wireless Ideas
 - 6.8K Consumer Product
 - 287 Service & License
 - 457 News and Release
 - 89 Security Advisories
 - 31 Education Center
 - 10 [Campaign] Zyxel Network Detective
 - 4.3K FAQ
 - 34 Documents
 - 34 Nebula Monthly Express
 - 85 About Community
 - 96 Security Highlight
 
  Guru Member