Error browsing

Post Reply
ismaeltxu
Posts: 4
Joined: Thu Mar 03, 2016 3:35 pm

Error browsing

Post by ismaeltxu » Thu Mar 03, 2016 4:16 pm

Some weeks ago I had a problem with my LaCie 5 big Network 2 because one of the disk was in fault. Then I updated the firmware of the device, backup data and rebuild the RAID.

Everything went OK. And any data lost. Right.

When I started reordering the information in LaCie suddenly the communication with the device is lost and only get reconnect when I restart the unit.

Every time I copy files to LaCie, the device goes down. I can copy few little files but when I try to copy a whole directory the unit goes down an must to restart.

Today the communication was down and I've connected by http and this connection was on. When I went to File Explorer of the web of the device I saw the tree of my storage structure but when I tried open one branch I get (something like, I can't write it):
opendir(NAS://B--box/104/ Gallery 104) [function.opendir]: failed to open dir: "fsAccessWrapper::dir_opendir"

Can somebody help me?

Thanks

ismaeltxu
Posts: 4
Joined: Thu Mar 03, 2016 3:35 pm

Re: Error browsing

Post by ismaeltxu » Thu Mar 03, 2016 6:27 pm

I've downloaded the diagnostic.zip and now I try to upload it for you but not allowed.

I'm been reading the /var/log/messages but I don't understand anything. Could be this part helpful?:

Code: Select all

Mar  3 15:59:26 LaCie-5big kernel: [79227.950000] Filesystem "md4": xfs_log_force: error 5 returned.
Mar  3 15:59:56 LaCie-5big kernel: [79257.950000] Filesystem "md4": xfs_log_force: error 5 returned.
Mar  3 16:00:01 LaCie-5big /USR/SBIN/CRON[24136]: (root) CMD (/sbin/mem_snapshot.sh)
Mar  3 16:00:01 LaCie-5big /USR/SBIN/CRON[24141]: (root) CMD (/usr/sbin/logrotate /etc/logrotate.tab)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] python2.6: page allocation failure. order:1, mode:0x20
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c0033ee0>] (unwind_backtrace+0x0/0xe4) from [<c008f160>] (__alloc_pages_nodemask+0x4a8/0x4f8)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c008f160>] (__alloc_pages_nodemask+0x4a8/0x4f8) from [<c00ab60c>] (cache_alloc_refill+0x260/0x518)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c00ab60c>] (cache_alloc_refill+0x260/0x518) from [<c00aba24>] (kmem_cache_alloc+0x74/0xb0)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c00aba24>] (kmem_cache_alloc+0x74/0xb0) from [<c03957d4>] (sk_prot_alloc+0x2c/0xd0)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03957d4>] (sk_prot_alloc+0x2c/0xd0) from [<c0395e40>] (sk_clone+0x1c/0x16c)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c0395e40>] (sk_clone+0x1c/0x16c) from [<c03cbc00>] (inet_csk_clone+0x18/0x90)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03cbc00>] (inet_csk_clone+0x18/0x90) from [<c03dec5c>] (tcp_create_openreq_child+0x1c/0x318)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03dec5c>] (tcp_create_openreq_child+0x1c/0x318) from [<c03dd7bc>] (tcp_v4_syn_recv_sock+0x54/0x180)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03dd7bc>] (tcp_v4_syn_recv_sock+0x54/0x180) from [<c03df1b4>] (tcp_check_req+0x25c/0x3b0)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03df1b4>] (tcp_check_req+0x25c/0x3b0) from [<c03dcf0c>] (tcp_v4_do_rcv+0xac/0x1b4)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03dcf0c>] (tcp_v4_do_rcv+0xac/0x1b4) from [<c03de904>] (tcp_v4_rcv+0x440/0x6b8)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03de904>] (tcp_v4_rcv+0x440/0x6b8) from [<c03c2a5c>] (ip_local_deliver_finish+0x11c/0x1a4)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03c2a5c>] (ip_local_deliver_finish+0x11c/0x1a4) from [<c03c291c>] (ip_rcv_finish+0x368/0x38c)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03c291c>] (ip_rcv_finish+0x368/0x38c) from [<c03a1150>] (netif_receive_skb+0x514/0x55c)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03a1150>] (netif_receive_skb+0x514/0x55c) from [<c032ebf0>] (eth_poll+0xaac/0xf44)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c032ebf0>] (eth_poll+0xaac/0xf44) from [<c03a3c54>] (net_rx_action+0x8c/0x1c0)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c03a3c54>] (net_rx_action+0x8c/0x1c0) from [<c00652e4>] (__do_softirq+0x84/0x110)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c00652e4>] (__do_softirq+0x84/0x110) from [<c00655ac>] (irq_exit+0x48/0x94)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c00655ac>] (irq_exit+0x48/0x94) from [<c002d074>] (asm_do_IRQ+0x74/0x8c)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] [<c002d074>] (asm_do_IRQ+0x74/0x8c) from [<c002dbe0>] (__irq_usr+0x40/0xa0)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] Exception stack(0xd5ee5fb0 to 0xd5ee5ff8)
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 5fa0:                                     00000050 40459160 401981b0 00000000 
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 5fc0: 4064d8e0 00000000 00000000 0000001c 4064d8e0 00000000 401781e4 be9478a4 
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 5fe0: be947868 be947868 400c5778 400c5ad4 20000010 ffffffff                   
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] Mem-info:
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] Normal per-cpu:
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] CPU    0: hi:  186, btch:  31 usd:  80
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] Active_anon:9400 active_file:14931 inactive_anon:8906
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000]  inactive_file:84462 unevictable:0 dirty:12 writeback:0 unstable:0
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000]  free:923 slab:7015 mapped:5153 pagetables:354 bounce:0
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] Normal free:3692kB min:2884kB low:3604kB high:4324kB active_anon:37600kB inactive_anon:35624kB active_file:59724kB inactive_file:337848kB unevictable:0kB present:520192kB pages_scanned:0 all_unreclaimable? no
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] lowmem_reserve[]: 0 0
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] Normal: 883*4kB 0*8kB 2*16kB 2*32kB 1*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3692kB
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 99681 total pagecache pages
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 0 pages in swap cache
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] Swap cache stats: add 0, delete 0, find 0/0
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] Free swap  = 255928kB
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] Total swap = 255928kB
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 131072 pages of RAM
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 1281 free pages
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 2731 reserved pages
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 7015 slab pages
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 105139 pages shared
Mar  3 16:00:05 LaCie-5big kernel: [79267.000000] 0 pages swap cached

ismaeltxu
Posts: 4
Joined: Thu Mar 03, 2016 3:35 pm

Re: Error browsing

Post by ismaeltxu » Mon Mar 07, 2016 10:38 am

Could be right if I uninstall RAM (hardware) and install again?

fvdw
Posts: 777
Joined: Wed Mar 18, 2009 11:13 pm

Re: Error browsing

Post by fvdw » Mon Mar 07, 2016 9:07 pm

I think you might still have a bad disk, this kind of messages are not ok
xfs_log_force: error 5 returned
...
[79267.000000] python2.6: page allocation failure.
It also show tcp errors but that could be a result of hanging system when trying to read a file and sejnd the data read (no response from the disk..)

What did you do to replace the faulty disk ?

ismaeltxu
Posts: 4
Joined: Thu Mar 03, 2016 3:35 pm

Re: Error browsing

Post by ismaeltxu » Thu Mar 10, 2016 8:09 am

I did like put in instructions:
I turned off the device, get off the faulty hd, started up the device and by the web browser run the rebuild process.

Now, we are trying backup the whole disk (4TB more or less) and this week is running quite well: only one stop in all the week when we are downloading data from 2 or 3 computers at time. The most problems are for uploading information.

But today we're waiting our new NAS Synology DS1515 to put the five disk (extracted from LaCie) and start with another diferent NAS.

Post Reply