Results 1 to 2 of 2

Thread: Help, Verify filesystem (ext3) always freeze at specific inode

  1. #1
    Registered+
    Join Date
    Sep 2009
    Location
    Italy
    Posts
    23
    Thanks
    0
    Thanked
    0 times in 0 posts
    • ivzanc's system
      • Motherboard:
      • Gigabyte X48-DQ6
      • CPU:
      • Q9650
      • Memory:
      • 8BG -1066Mhz
      • Graphics card(s):
      • Radeon 4980-2048
      • PSU:
      • Enermax Infinity 720
      • Operating System:
      • Vista 64bit
      • Monitor(s):
      • Lcie Electron Blue 2 - 22"

    Question Help, Verify filesystem (ext3) always freeze at specific inode

    Hi guys,

    I have a problem with a raid1 set on my n5500...
    The execution of "verify filesystem" seems stop working always at inode 2738... led on harddisks continue blinking but logging is blocked.

    Stopping check is however possible and the unit seems normally work... after restart all data are accessible ... however uploading and downloading files from this RAID set appear to proceed with some interruptions, but no errors and overall speed is correct.

    My questions are: is a logical array problem?, an hdd hardware failure? , there is a way to check this before that cause a major issue?, someone have a solution to correct the filesystem problem?

    I'm a beginner in the Linux world and I know nothing about ext3 file system and how to check its structure (and correct it... ).

    Thanks in advance to everyone for the help.

  2. #2
    Registered+
    Join Date
    Sep 2009
    Location
    Italy
    Posts
    23
    Thanks
    0
    Thanked
    0 times in 0 posts
    • ivzanc's system
      • Motherboard:
      • Gigabyte X48-DQ6
      • CPU:
      • Q9650
      • Memory:
      • 8BG -1066Mhz
      • Graphics card(s):
      • Radeon 4980-2048
      • PSU:
      • Enermax Infinity 720
      • Operating System:
      • Vista 64bit
      • Monitor(s):
      • Lcie Electron Blue 2 - 22"

    Re: Help, Verify filesystem (ext3) always freeze at specific inode

    Solved ... (perhaps....)
    ....
    I have re-execute task another time... after one hour the block 2738 issue has been overcome (overall time 2 hours).
    the next execution of the task lasted only 45 minutes and completes successfully without error.

    bye

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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