Visit Open-E website
Results 1 to 6 of 6

Thread: Problems with access to a network drive

  1. #1

    Default Problems with access to a network drive

    Hello!
    Sorry fo my bad english. Open-E NAS-R3 - 8 HDD (8*1Tb) – Seagate ST31000340NS
    Have a next problem. There are three network drive, for example - Air, Capture, Edit.
    Copying video to disk "Edit" - storage has stopped with error-“No access. Remove the write protection” in Windows notification area. Empirically found that this problem occurs when working with network drive "Edit". Work with "Air" and "Capture"- all normal. In the boot process everything is fine - without any errors. System loaded normally, but when you try copy on “Edit” again this error repeated again and again.
    In system events (web-interface log in)- warning messages.

    Critical_errors.log contains this:

    [spoiler]2010/09/07 13:38:30|Pid: 10701, comm: smbd Not tainted 2.6.25.13-oe32 #61
    2010/09/07 13:38:30|[<c012241e>] <6>sd 5:0:0:0: [sdb] warn_on_slowpath+0x3e/0x60
    2010/09/07 13:38:30|Result: hostbyte=0x00 driverbyte=0x06
    2010/09/07 13:38:30|[<c01371d6>] enqueue_hrtimer+0xa6/0x110
    2010/09/07 13:38:30|[<c02d791a>] vsnprintf+0x2ca/0x550
    2010/09/07 13:38:30|[<c0122a44>] call_console_drivers+0x74/0x100
    2010/09/07 13:38:30|[<c01231a2>] release_console_sem+0x92/0xa0
    2010/09/07 13:38:30|[<c01231a2>] release_console_sem+0x92/0xa0
    2010/09/07 13:38:30|[<c01933b6>] mark_buffer_dirty+0x96/0xa0
    2010/09/07 13:38:30|[<c01c301a>] ext3_commit_super+0x3a/0x50
    2010/09/07 13:38:30|[<c01c057f>] ext3_handle_error+0x3f/0xa0
    2010/09/07 13:38:30|[<c01c061c>] ext3_error+0x3c/0x50
    2010/09/07 13:38:30|[<c01bba18>] __ext3_get_inode_loc+0x1c8/0x210
    2010/09/07 13:38:30|[<c01bc509>] ext3_reserve_inode_write+0x19/0x60
    2010/09/07 13:38:30|[<c01bc561>] ext3_mark_inode_dirty+0x11/0x40
    2010/09/07 13:38:30|[<c01bc5ed>] ext3_dirty_inode+0x5d/0x70
    2010/09/07 13:38:30|[<c018e797>] __mark_inode_dirty+0xc7/0x150
    2010/09/07 13:38:30|[<c018699f>] file_update_time+0x8f/0xc0
    2010/09/07 13:38:30|[<c015452b>] __generic_file_aio_write_nolock+0x22b/0x530
    2010/09/07 13:38:30|[<c047207e>] do_sock_read+0xae/0xc0
    2010/09/07 13:38:30|[<c01848a1>] __d_lookup+0xa1/0x100
    2010/09/07 13:38:30|[<c0154963>] generic_file_aio_write+0x63/0xf0
    2010/09/07 13:38:30|[<c01b7a5b>] ext3_file_write+0x1b/0xa0
    2010/09/07 13:38:30|[<c0173652>] do_sync_write+0xc2/0x120
    2010/09/07 13:38:30|[<c0134580>] autoremove_wake_function+0x0/0x30
    2010/09/07 13:38:30|[<c0188243>] mntput_no_expire+0x13/0x60
    2010/09/07 13:38:30|[<c0188243>] <6>sd 5:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x06
    2010/09/07 13:38:30|mntput_no_expire+0x13/0x60
    2010/09/07 13:38:30|[<c0172019>] sys_chdir+0x49/0x60
    2010/09/07 13:38:30|[<c02b3c0c>] security_file_permission+0xc/0x10
    2010/09/07 13:38:30|[<c01732af>] rw_verify_area+0x4f/0xb0
    2010/09/07 13:38:30|[<c0173590>] do_sync_write+0x0/0x120
    2010/09/07 13:38:30|[<c017372f>] vfs_write+0x7f/0x120
    2010/09/07 13:38:30|[<c017387c>] sys_write+0x3c/0x70
    2010/09/07 13:38:30|[<c0103a42>] syscall_call+0x7/0xb
    2010/09/07 13:38:30|=======================
    2010/09/07 13:50:28|Result: hostbyte=0x00 driverbyte=0x06
    2010/09/07 13:50:28|Pid: 7989, comm: kjournald Not tainted 2.6.25.13-oe32 #61
    2010/09/07 13:50:28|[<c012241e>] warn_on_slowpath+0x3e/0x60
    2010/09/07 13:50:28|[<c01193b3>] hrtick_set+0x83/0x100
    2010/09/07 13:50:28|[<c0516ae2>] __sched_text_start+0x202/0x4b0
    2010/09/07 13:50:28|[<c0433a47>] dm_unplug_all+0x17/0x30
    2010/09/07 13:50:28|[<c02c6e5a>] blk_unplug+0xa/0x10
    2010/09/07 13:50:28|[<c05172a9>] __wait_on_bit+0x59/0x70
    2010/09/07 13:50:28|[<c01922b0>] sync_buffer+0x0/0x40
    2010/09/07 13:50:28|[<c01922b0>] sync_buffer+0x0/0x40
    2010/09/07 13:50:28|[<c051734c>] out_of_line_wait_on_bit+0x8c/0xa0
    2010/09/07 13:50:28|[<c01345b0>] wake_bit_function+0x0/0x40
    2010/09/07 13:50:28|[<c01933b6>] mark_buffer_dirty+0x96/0xa0
    2010/09/07 13:50:28|[<c01c8e88>] __journal_unfile_buffer+0x8/0x20
    2010/09/07 13:50:28|[<c01c94e6>] journal_refile_buffer+0x26/0x60
    2010/09/07 13:50:28|[<c01c9fe2>] journal_commit_transaction+0x6d2/0x950
    2010/09/07 13:50:28|[<c0134580>] autoremove_wake_function+0x0/0x30
    2010/09/07 13:50:28|[<c0134580>] autoremove_wake_function+0x0/0x30
    2010/09/07 13:50:28|[<c012aa11>] try_to_del_timer_sync+0x41/0x50
    2010/09/07 13:50:28|[<c01cbadc>] kjournald+0x9c/0x1d0
    2010/09/07 13:50:28|[<c0134580>] autoremove_wake_function+0x0/0x30
    2010/09/07 13:50:28|[<c0134580>] autoremove_wake_function+0x0/0x30
    2010/09/07 13:50:28|[<c011de7b>] complete+0x2b/0x40
    2010/09/07 13:50:28|[<c01cba40>] kjournald+0x0/0x1d0
    2010/09/07 13:50:28|[<c0134094>] kthread+0x44/0x70
    2010/09/07 13:50:28|[<c0134050>] kthread+0x0/0x70
    2010/09/07 13:50:28|[<c0104c47>] kernel_thread_helper+0x7/0x10
    2010/09/07 13:50:28|=======================[/spoiler]

  2. #2

    Default

    Please run the Repair Filesystem in the Extended tools also make sure that you are on the latest version of the NAS-R3 below.

    NAS-R3 build 3570

    The new version update of DSS V5 up 49 build 3570 is ready for download from our FTP:

    URL: ftp://software:enterforupdate@ftp.op...49_build_3570/
    (This update is for version 5.0 up 49 build3294 and 5.0 up49 build 3553 ONLY!)
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  3. #3

    Default

    Is this safe (operation with Repair Filesystem) for data on storage drives?

  4. #4

    Default

    Yes or re-install and then check the raid health from the vendor.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  5. #5

    Default

    Hello!
    Using the tool Repair Filesystem helped only partially. The problem was complex - from time to time system freezes and only hard reset returns it to work. In the log was something like a "bad stripe". Found a possible complex problem with Adaptec / ICP Storage Manager

    http://ask.adaptec.com/scripts/adapt...ted=1172018702

    and Seagate Barracuda

    http://ask.adaptec.com/scripts/adapt...i=&p_topview=1.

    Had to update the HDD firmware to recommended and build the raid array again (backup your data!!!). 5 months NAS working as a clock . Maybe my experience will help for someone. Thread can be closed.
    And thanks for the help!!!

  6. #6

    Default

    Thanks for the update and yes this could help others!
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •