I can not access the hd on my NAS 210

Oxnas 810 based
Mijzelf
Posts: 6226
Joined: Mon Jun 16, 2008 10:45 am

Re: I can not access the hd on my NAS 210

Post by Mijzelf » Sat Apr 26, 2014 12:19 pm

OK. Your data partition is recognized, and the raid array is assembled. Yet the array is not mounted. Let's try to find out why not. Can you post the output of

Code: Select all

mkdir -p /tmp/mountpoint
dmesg -c >/dev/null
mount /dev/md0 /tmp/mountpoint
dmesg

bladebull
Posts: 46
Joined: Wed Apr 23, 2014 4:39 pm

Re: I can not access the hd on my NAS 210

Post by bladebull » Sat Apr 26, 2014 1:18 pm

Mijzelf wrote:OK. Your data partition is recognized, and the raid array is assembled. Yet the array is not mounted. Let's try to find out why not. Can you post the output of

Code: Select all

mkdir -p /tmp/mountpoint
dmesg -c >/dev/null
mount /dev/md0 /tmp/mountpoint
dmesg

sh-4.1# mkdir -p /tmp/mountpoint
sh-4.1# dmesg -c >/dev/null
sh-4.1# mount /dev/md0 /tmp/mountpoint
sh-4.1# dmesg
Filesystem "md0": Disabling barriers, not supported by the underlying device
XFS mounting filesystem md0
Starting XFS recovery on filesystem: md0 (logdev: internal)
XFS resetting qflags for filesystem md0
Filesystem "md0": corrupt dinode 61, (btree extents). Unmount and run xfs_repai
r.
Filesystem "md0": XFS internal error xfs_bmap_read_extents(1) at line 4551 of fi
le fs/xfs/xfs_bmap.c. Caller 0xbf04b188
[<c0025184>] (dump_stack+0x0/0x1c) from [<bf03e70c>] (xfs_error_report+0x5c/0x68
[xfs])
[<bf03e6b0>] (xfs_error_report+0x0/0x68 [xfs]) from [<bf0250cc>] (xfs_bmap_read_
extents+0x578/0x5d4 [xfs])
r5:00000000 r4:bf04b188
[<bf024b54>] (xfs_bmap_read_extents+0x0/0x5d4 [xfs]) from [<bf04b188>] (xfs_irea
d_extents+0x88/0xf8 [xfs])
[<bf04b100>] (xfs_iread_extents+0x0/0xf8 [xfs]) from [<bf0273a4>] (xfs_bunmapi+0
xaac/0x1040 [xfs])
r7:00000000 r6:00000000 r5:00000000 r4:0040c100
[<bf0268f8>] (xfs_bunmapi+0x0/0x1040 [xfs]) from [<bf04a7dc>] (xfs_itruncate_fin
ish+0x21c/0x3c0 [xfs])
[<bf04a5c0>] (xfs_itruncate_finish+0x0/0x3c0 [xfs]) from [<bf069c20>] (xfs_inact
ive+0x3dc/0x4bc [xfs])
[<bf069844>] (xfs_inactive+0x0/0x4bc [xfs]) from [<bf0767c0>] (xfs_fs_clear_inod
e+0x54/0x8c [xfs])
[<bf07676c>] (xfs_fs_clear_inode+0x0/0x8c [xfs]) from [<c009e3b8>] (clear_inode+
0x6c/0x160)
r7:00000000 r6:0040c100 r5:00000000 r4:c70d1ce0
[<c009e34c>] (clear_inode+0x0/0x160) from [<c009ea24>] (generic_delete_inode+0x1
2c/0x154)
r5:00000000 r4:c70d1ce0
[<c009e8f8>] (generic_delete_inode+0x0/0x154) from [<c009ebb4>] (generic_drop_in
ode+0x168/0x18c)
r5:c70d1ce0 r4:c70d1ce0
[<c009ea4c>] (generic_drop_inode+0x0/0x18c) from [<c009da10>] (iput+0x80/0xa0)
r7:00000000 r6:0040c100 r5:00000000 r4:c70d1ce0
[<c009d990>] (iput+0x0/0xa0) from [<bf057874>] (xlog_recover_process_iunlinks+0x
350/0x3f4 [xfs])
r5:00000000 r4:c1548080
[<bf057524>] (xlog_recover_process_iunlinks+0x0/0x3f4 [xfs]) from [<bf0579c0>] (
xlog_recover_finish+0xa8/0xb8 [xfs])
[<bf057918>] (xlog_recover_finish+0x0/0xb8 [xfs]) from [<bf05307c>] (xfs_log_mou
nt_finish+0x38/0x3c [xfs])
r5:00000000 r4:00000400
[<bf053044>] (xfs_log_mount_finish+0x0/0x3c [xfs]) from [<bf05c438>] (xfs_mountf
s+0x9e0/0xbb8 [xfs])
r7:c70d1e20 r6:00000004 r5:00000000 r4:00000000
[<bf05ba58>] (xfs_mountfs+0x0/0xbb8 [xfs]) from [<bf04ccbc>] (xfs_ioinit+0x14/0x
18 [xfs])
[<bf04cca8>] (xfs_ioinit+0x0/0x18 [xfs]) from [<bf0657a8>] (xfs_mount+0x340/0x39
0 [xfs])
[<bf065468>] (xfs_mount+0x0/0x390 [xfs]) from [<bf076b68>] (xfs_fs_fill_super+0x
c4/0x22c [xfs])
[<bf076aa4>] (xfs_fs_fill_super+0x0/0x22c [xfs]) from [<c008b838>] (get_sb_bdev+
0x150/0x180)
[<c008b6e8>] (get_sb_bdev+0x0/0x180) from [<bf076718>] (xfs_fs_get_sb+0x20/0x2c
[xfs])
r8:bf090364 r7:00000000 r6:00000000 r5:c788b000 r4:bf076aa4
[<bf0766f8>] (xfs_fs_get_sb+0x0/0x2c [xfs]) from [<c008a678>] (vfs_kern_mount+0x
58/0xac)
r4:c6c3b340
[<c008a620>] (vfs_kern_mount+0x0/0xac) from [<c008a728>] (do_kern_mount+0x3c/0xd
c)
r8:bf090364 r7:c788a000 r6:00000000 r5:c788b000 r4:00000000
[<c008a6ec>] (do_kern_mount+0x0/0xdc) from [<c00a241c>] (do_mount+0x154/0x688)
r9:c3c69ee8 r8:00000000 r7:c788a000 r6:c788b000 r5:00000000
r4:00000000
[<c00a22c8>] (do_mount+0x0/0x688) from [<c00a29f4>] (sys_mount+0xa4/0xd8)
[<c00a2950>] (sys_mount+0x0/0xd8) from [<c00265c0>] (ret_fast_syscall+0x0/0x2c)
r7:00000015 r6:00021250 r5:c0ed0000 r4:00000000
Filesystem "md0": XFS internal error xfs_trans_cancel at line 1163 of file fs/xf
s/xfs_trans.c. Caller 0xbf069c34
[<c0025184>] (dump_stack+0x0/0x1c) from [<bf03e70c>] (xfs_error_report+0x5c/0x68
[xfs])
[<bf03e6b0>] (xfs_error_report+0x0/0x68 [xfs]) from [<bf05f610>] (xfs_trans_canc
el+0x10c/0x134 [xfs])
r5:00000000 r4:0040c100
[<bf05f504>] (xfs_trans_cancel+0x0/0x134 [xfs]) from [<bf069c34>] (xfs_inactive+
0x3f0/0x4bc [xfs])
r8:00000000 r7:c70d1ce0 r6:c70d2c60 r5:00000000 r4:c3c69a50
[<bf069844>] (xfs_inactive+0x0/0x4bc [xfs]) from [<bf0767c0>] (xfs_fs_clear_inod
e+0x54/0x8c [xfs])
[<bf07676c>] (xfs_fs_clear_inode+0x0/0x8c [xfs]) from [<c009e3b8>] (clear_inode+
0x6c/0x160)
r7:00000000 r6:0040c100 r5:00000000 r4:c70d1ce0
[<c009e34c>] (clear_inode+0x0/0x160) from [<c009ea24>] (generic_delete_inode+0x1
2c/0x154)
r5:00000000 r4:c70d1ce0
[<c009e8f8>] (generic_delete_inode+0x0/0x154) from [<c009ebb4>] (generic_drop_in
ode+0x168/0x18c)
r5:c70d1ce0 r4:c70d1ce0
[<c009ea4c>] (generic_drop_inode+0x0/0x18c) from [<c009da10>] (iput+0x80/0xa0)
r7:00000000 r6:0040c100 r5:00000000 r4:c70d1ce0
[<c009d990>] (iput+0x0/0xa0) from [<bf057874>] (xlog_recover_process_iunlinks+0x
350/0x3f4 [xfs])
r5:00000000 r4:c1548080
[<bf057524>] (xlog_recover_process_iunlinks+0x0/0x3f4 [xfs]) from [<bf0579c0>] (
xlog_recover_finish+0xa8/0xb8 [xfs])
[<bf057918>] (xlog_recover_finish+0x0/0xb8 [xfs]) from [<bf05307c>] (xfs_log_mou
nt_finish+0x38/0x3c [xfs])
r5:00000000 r4:00000400
[<bf053044>] (xfs_log_mount_finish+0x0/0x3c [xfs]) from [<bf05c438>] (xfs_mountf
s+0x9e0/0xbb8 [xfs])
r7:c70d1e20 r6:00000004 r5:00000000 r4:00000000
[<bf05ba58>] (xfs_mountfs+0x0/0xbb8 [xfs]) from [<bf04ccbc>] (xfs_ioinit+0x14/0x
18 [xfs])
[<bf04cca8>] (xfs_ioinit+0x0/0x18 [xfs]) from [<bf0657a8>] (xfs_mount+0x340/0x39
0 [xfs])
[<bf065468>] (xfs_mount+0x0/0x390 [xfs]) from [<bf076b68>] (xfs_fs_fill_super+0x
c4/0x22c [xfs])
[<bf076aa4>] (xfs_fs_fill_super+0x0/0x22c [xfs]) from [<c008b838>] (get_sb_bdev+
0x150/0x180)
[<c008b6e8>] (get_sb_bdev+0x0/0x180) from [<bf076718>] (xfs_fs_get_sb+0x20/0x2c
[xfs])
r8:bf090364 r7:00000000 r6:00000000 r5:c788b000 r4:bf076aa4
[<bf0766f8>] (xfs_fs_get_sb+0x0/0x2c [xfs]) from [<c008a678>] (vfs_kern_mount+0x
58/0xac)
r4:c6c3b340
[<c008a620>] (vfs_kern_mount+0x0/0xac) from [<c008a728>] (do_kern_mount+0x3c/0xd
c)
r8:bf090364 r7:c788a000 r6:00000000 r5:c788b000 r4:00000000
[<c008a6ec>] (do_kern_mount+0x0/0xdc) from [<c00a241c>] (do_mount+0x154/0x688)
r9:c3c69ee8 r8:00000000 r7:c788a000 r6:c788b000 r5:00000000
r4:00000000
[<c00a22c8>] (do_mount+0x0/0x688) from [<c00a29f4>] (sys_mount+0xa4/0xd8)
[<c00a2950>] (sys_mount+0x0/0xd8) from [<c00265c0>] (ret_fast_syscall+0x0/0x2c)
r7:00000015 r6:00021250 r5:c0ed0000 r4:00000000
xfs_force_shutdown(md0,0x8) called from line 1164 of file fs/xfs/xfs_trans.c. R
eturn address = 0xbf05f624
Filesystem "md0": Corruption of in-memory data detected. Shutting down filesyst
em: md0
Please umount the filesystem, and rectify the problem(s)
Ending XFS recovery on filesystem: md0 (logdev: internal)
sh-4.1#

Mijzelf
Posts: 6226
Joined: Mon Jun 16, 2008 10:45 am

Re: I can not access the hd on my NAS 210

Post by Mijzelf » Sat Apr 26, 2014 1:53 pm

Right. You have an filesystem error on /dev/md0. The right action is already mentioned in the dmesg log: run xfs_repair. I don't know if that tool is included with the firmware, but you can just try:

Code: Select all

xfs_repair /dev/md0
However, if your data is really important, you should copy the filesystem before trying to repair. In most cases xfs_repair just does it's job fine, but sometimes it worsens the situation. I guess depending on the actual fault.
To copy the filesystem, you'll need a 2nd 3TB disk.

bladebull
Posts: 46
Joined: Wed Apr 23, 2014 4:39 pm

Re: I can not access the hd on my NAS 210

Post by bladebull » Sat Apr 26, 2014 2:00 pm

Mijzelf wrote:Right. You have an filesystem error on /dev/md0. The right action is already mentioned in the dmesg log: run xfs_repair. I don't know if that tool is included with the firmware, but you can just try:

Code: Select all

xfs_repair /dev/md0
However, if your data is really important, you should copy the filesystem before trying to repair. In most cases xfs_repair just does it's job fine, but sometimes it worsens the situation. I guess depending on the actual fault.
To copy the filesystem, you'll need a 2nd 3TB disk.
I have an external seagate 3tb usb

How do I copy my data?

Mijzelf
Posts: 6226
Joined: Mon Jun 16, 2008 10:45 am

Re: I can not access the hd on my NAS 210

Post by Mijzelf » Sat Apr 26, 2014 2:36 pm

Connect the disk to the NAS. It will be recognized as sdc. Check that with ' cat /proc/partitions '.
If it is sdc, execute

Code: Select all

dd if=/dev/md0 of=/dev/sdc bs=1M >/tmp/dd.log 2>&1 &
Do not make any typos! dd will happily overwrite *anything* you offer as target device. BTW, if stands for 'input file', while of stands for 'output file'.

The part '>/tmp/dd.log 2>&1' redirects the output to the file /tmp/dd.log, and the '&' at the end will put the action in background, so you can close the telnet shell. The copy action will run at 25MB/sec (which is the maximum throughput for an USB2 disk), so copying the 3TB will take about 120000 seconds, which is about 30 hours.

At any time you can check the status by executing ' cat /tmp/dd.log '. Unfortunately you will only get a message that the copying is started, and that it's finished (or some error occurred). There is no update in between.

bladebull
Posts: 46
Joined: Wed Apr 23, 2014 4:39 pm

Re: I can not access the hd on my NAS 210

Post by bladebull » Sat Apr 26, 2014 2:49 pm

Mijzelf wrote:Connect the disk to the NAS. It will be recognized as sdc. Check that with ' cat /proc/partitions '.
If it is sdc, execute

Code: Select all

dd if=/dev/md0 of=/dev/sdc bs=1M >/tmp/dd.log 2>&1 &
Do not make any typos! dd will happily overwrite *anything* you offer as target device. BTW, if stands for 'input file', while of stands for 'output file'.

The part '>/tmp/dd.log 2>&1' redirects the output to the file /tmp/dd.log, and the '&' at the end will put the action in background, so you can close the telnet shell. The copy action will run at 25MB/sec (which is the maximum throughput for an USB2 disk), so copying the 3TB will take about 120000 seconds, which is about 30 hours.

At any time you can check the status by executing ' cat /tmp/dd.log '. Unfortunately you will only get a message that the copying is started, and that it's finished (or some error occurred). There is no update in between.

I have movies, pictures and music on the NAS

I just need the pictures, there is an easier to get pictures only way?

Mijzelf
Posts: 6226
Joined: Mon Jun 16, 2008 10:45 am

Re: I can not access the hd on my NAS 210

Post by Mijzelf » Sat Apr 26, 2014 3:52 pm

There is a problem, the filesystem itself is damaged, so you can't access the individual files, only the whole filesystem as a block. Yet there are some possibilities. You can use photorec to recover the pictures alone.
First install it on your FFP stick:

Code: Select all

slacker -i photorec
Then run it

Code: Select all

photorec /dev/md0
Let it write the pictures on your USB disk. If you are satisfied with the result, you can try the xfs_repair.

bladebull
Posts: 46
Joined: Wed Apr 23, 2014 4:39 pm

Re: I can not access the hd on my NAS 210

Post by bladebull » Sat Apr 26, 2014 5:28 pm

Mijzelf wrote:Connect the disk to the NAS. It will be recognized as sdc. Check that with ' cat /proc/partitions '.
If it is sdc, execute

Code: Select all

dd if=/dev/md0 of=/dev/sdc bs=1M >/tmp/dd.log 2>&1 &
Do not make any typos! dd will happily overwrite *anything* you offer as target device. BTW, if stands for 'input file', while of stands for 'output file'.

The part '>/tmp/dd.log 2>&1' redirects the output to the file /tmp/dd.log, and the '&' at the end will put the action in background, so you can close the telnet shell. The copy action will run at 25MB/sec (which is the maximum throughput for an USB2 disk), so copying the 3TB will take about 120000 seconds, which is about 30 hours.

At any time you can check the status by executing ' cat /tmp/dd.log '. Unfortunately you will only get a message that the copying is started, and that it's finished (or some error occurred). There is no update in between.

sh-4.1# cat /proc/partitions
major minor #blocks name

7 0 109568 loop0
8 0 2930266584 sda
8 1 498688 sda1
8 2 2929766400 sda2
31 0 128 mtdblock0
31 1 1792 mtdblock1
31 2 1664 mtdblock2
31 3 448 mtdblock3
31 4 48 mtdblock4
31 5 8 mtdblock5
31 6 8 mtdblock6
9 0 2929766336 md0
8 16 1003520 sdb
8 17 15851 sdb1
8 18 987399 sdb2
8 32 2930266580 sdc
sh-4.1# dd if=/dev/md0 of=/dev/sdc bs=1M >/tmp/dd.log 2>&1 &
[1] 7333
sh-4.1# cat /tmp/dd.log
sh-4.1#

is right?

Mijzelf
Posts: 6226
Joined: Mon Jun 16, 2008 10:45 am

Re: I can not access the hd on my NAS 210

Post by Mijzelf » Sat Apr 26, 2014 7:30 pm

Yes. I just tried it here, and it turns out dd doesn't give *any* output until it's finished.

bladebull
Posts: 46
Joined: Wed Apr 23, 2014 4:39 pm

Re: I can not access the hd on my NAS 210

Post by bladebull » Sat Apr 26, 2014 9:50 pm

Mijzelf wrote:Yes. I just tried it here, and it turns out dd doesn't give *any* output until it's finished.

when finished I place the command repair and you notice

MrKrzYch00
Posts: 4
Joined: Fri Apr 25, 2014 11:35 pm

Re: I can not access the hd on my NAS 210

Post by MrKrzYch00 » Sun Apr 27, 2014 8:06 am

Interesting, I wonder how it happened that installing new firmware corrupted the xfs partition... Maybe just a concidence?

I myself would still run dd on my local computer, the NAS is pretty slow and copying 3TB of data may take few days if I'm not mistaken. Anyway, bladebull, if You want to use Your computer at the same time then there is windows alternative for dd named HDD Raw Copy Tool I personally used at some point when retrying my preparations of 4TB hdd. It's GUI and can put it as RAW image file to be mounted later.

bladebull
Posts: 46
Joined: Wed Apr 23, 2014 4:39 pm

Re: I can not access the hd on my NAS 210

Post by bladebull » Sun Apr 27, 2014 10:17 am

bladebull wrote:
Mijzelf wrote:Yes. I just tried it here, and it turns out dd doesn't give *any* output until it's finished.

when finished I place the command repair and you notice
I did not command, and still not giving any message

but it seems to me that already ended because looking at the admin page htm zyxel in status ... the cpu usage was at 100% yesterday

Today in this 0%

how can I determine if it was copied?

bladebull
Posts: 46
Joined: Wed Apr 23, 2014 4:39 pm

Re: I can not access the hd on my NAS 210

Post by bladebull » Sun Apr 27, 2014 10:21 am

MrKrzYch00 wrote:Interesting, I wonder how it happened that installing new firmware corrupted the xfs partition... Maybe just a concidence?

I myself would still run dd on my local computer, the NAS is pretty slow and copying 3TB of data may take few days if I'm not mistaken. Anyway, bladebull, if You want to use Your computer at the same time then there is windows alternative for dd named HDD Raw Copy Tool I personally used at some point when retrying my preparations of 4TB hdd. It's GUI and can put it as RAW image file to be mounted later.



this problem is already firwmare 1 year

how do i use this hdd raw copy tool?

I need step by step and my English is very bad so the base of the google translation

Mijzelf
Posts: 6226
Joined: Mon Jun 16, 2008 10:45 am

Re: I can not access the hd on my NAS 210

Post by Mijzelf » Sun Apr 27, 2014 10:26 am

bladebull wrote:how can I determine if it was copied?

Code: Select all

cat /tmp/dd.log
MrKrzYch00 wrote:I wonder how it happened that installing new firmware corrupted the xfs partition... Maybe just a concidence?
I certainly hope so. Updating the firmware doesn't actually touch the data partition. And it's the same kernel, so it can't be an xfs version quirk.
I myself would still run dd on my local computer, the NAS is pretty slow
I think in this case the USB disk is the limiting factor, and not the NAS. Besides, the NAS mey take more time, but it's still the most economic, in Wh/copied bytes.

bladebull
Posts: 46
Joined: Wed Apr 23, 2014 4:39 pm

Re: I can not access the hd on my NAS 210

Post by bladebull » Sun Apr 27, 2014 10:46 am

Mijzelf wrote:
bladebull wrote:how can I determine if it was copied?

Code: Select all

cat /tmp/dd.log
sh-4.1# cat /tmp/dd.log
sh-4.1# cat /tmp/dd.log
sh-4.1# cat /tmp/dd.log
sh-4.1#

no msg!!

and cpu usage 0%

the copie is end?

my hd usg is 3.0

Post Reply