Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 40

Thread: Files with I/O Errors preventing access to full folders?

  1. #11
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    I downloaded Testdisk and Photorec to my new computer with Windows 7 and am trying to read it from there. When running, i receive:

    Code:
    Select a media <use Arrow keys, then press Enter>:
    >Disk /dev/sda - 1000GB / 931 GiB <RO> - TOSHIBA
    
    >[Proceed] [Quit]
    I click proceed, and this is where the step-by-step somewhat loses me. I receive:

    Code:
     Partition                  Start        End    Size in sectors
      No partition             0   0  1 121601  80 63 1953525168 [Whole disk]
    * HPFS - NTFS              0  32 33    25 126 37     407552 [SYSTEM]
    P HPFS - NTFS             25 126 38 118858  49 39 1909047296
    P HPFS - NTFS          118858  49 40 121588  24 36   43855872 [Recovery]
    P FAT32 LBA            121588  24 37 121601  25 24     208896 [HP_TOOLS]
    
    >[Search] [Options] [File Opt] [Quit]
    My image.dd file is no longer on my external harddrive, and now in a folder on this new computer's internal. What are the next steps I should take?
    Last edited by SineSpe; June 18th, 2013 at 06:50 PM.

  2. #12
    Join Date
    Mar 2010
    Location
    India
    Beans
    7,721
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by SineSpe View Post
    My image.dd file is no longer on my external harddrive, and now in a folder on this new computer's internal. What are the next steps I should take?
    Running photorec or testdisk without parameters will make them work only on the physical drives. To make it work on the image, you have to run it with the path to the image as its option, like I posted in post #9 earlier (it was for Ubuntu however).

    For example, if the path of the photorec_win.exe program (that you double-click to run it) is "D:\testdisk_xyz\win\photorec_win.exe", the path of the "image.dd" file is "E:\backup\image.dd", you will have to run photorec from command prompt as -
    Code:
    cd D:\testdisk_xyz\win
    photorec_win.exe E:\backup\image.dd
    This will start photorec with the image file instead of your physical drive. The rest of the options will be same as with physical drive.

    PS:
    I have personally found testdisk/photorec to work better when running on Linux. So if you can use it on a Live session (preferably Live usb to save settings), try that instead.
    Last edited by varunendra; June 18th, 2013 at 07:37 PM.
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  3. #13
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    So right now, i believe Photorec is running. I've attached a screenshot of that progress to this post.

    Quote Originally Posted by mips View Post
    Some things might already not be possible to recover.

    Create an image file of the drive or partition using GNU ddrescue and ensure you enable the log file. Once you have an image you can mount it and try to recover from it. You can also use tools like testdisk/photorec on the image.

    You can also have a look at https://help.ubuntu.com/community/DataRecovery

    Do me a favour and post the S.M.A.R.T. info for the drive here, you can get that info using the smartctl command or you can use a gui called GSmartControl.
    This is the SMART information i received by commanding sudo smartctl --all /dev/sda3 :

    Code:
    xubuntu@xubuntu:~/Desktop$ sudo smartctl --all /dev/sda3
    smartctl 5.43 2012-06-30 r3573 [i686-linux-3.5.0-17-generic] (local build)
    Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
    
    === START OF INFORMATION SECTION ===
    Model Family:     Seagate Momentus 5400.6
    Device Model:     ST9320325AS
    Serial Number:    5VD1X5P9
    LU WWN Device Id: 5 000c50 0217228f7
    Firmware Version: 0003DEM1
    User Capacity:    320,072,933,376 bytes [320 GB]
    Sector Size:      512 bytes logical/physical
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   8
    ATA Standard is:  ATA-8-ACS revision 4
    Local Time is:    Tue Jun 18 22:56:16 2013 UTC
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    See vendor-specific Attribute list for marginal Attributes.
    
    General SMART Values:
    Offline data collection status:  (0x82)    Offline data collection activity
                        was completed without error.
                        Auto Offline Data Collection: Enabled.
    Self-test execution status:      (   0)    The previous self-test routine completed
                        without error or no self-test has ever 
                        been run.
    Total time to complete Offline 
    data collection:         (    0) seconds.
    Offline data collection
    capabilities:              (0x7b) SMART execute Offline immediate.
                        Auto Offline data collection on/off support.
                        Suspend Offline collection upon new
                        command.
                        Offline surface scan supported.
                        Self-test supported.
                        Conveyance Self-test supported.
                        Selective Self-test supported.
    SMART capabilities:            (0x0003)    Saves SMART data before entering
                        power-saving mode.
                        Supports SMART auto save timer.
    Error logging capability:        (0x01)    Error logging supported.
                        General Purpose Logging supported.
    Short self-test routine 
    recommended polling time:      (   2) minutes.
    Extended self-test routine
    recommended polling time:      (  99) minutes.
    Conveyance self-test routine
    recommended polling time:      (   3) minutes.
    SCT capabilities:            (0x103f)    SCT Status supported.
                        SCT Error Recovery Control supported.
                        SCT Feature Control supported.
                        SCT Data Table supported.
    
    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x000f   110   074   006    Pre-fail  Always       -       27781091
      3 Spin_Up_Time            0x0003   099   097   085    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3277
      5 Reallocated_Sector_Ct   0x0033   089   089   036    Pre-fail  Always       -       243
      7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail  Always       -       4459252319
      9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6607
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   097   097   020    Old_age   Always       -       3175
    184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
    187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       65535
    188 Command_Timeout         0x0032   100   001   000    Old_age   Always       -       17180199630
    189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
    190 Airflow_Temperature_Cel 0x0022   059   037   045    Old_age   Always   In_the_past 41 (0 255 42 25 0)
    191 G-Sense_Error_Rate      0x0032   098   098   000    Old_age   Always       -       4097
    192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       5
    193 Load_Cycle_Count        0x0032   075   075   000    Old_age   Always       -       50757
    194 Temperature_Celsius     0x0022   041   063   000    Old_age   Always       -       41 (0 9 0 0 0)
    195 Hardware_ECC_Recovered  0x001a   050   045   000    Old_age   Always       -       27781091
    197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       423
    198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       423
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       3
    240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       224558070110496
    241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3087503864
    242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2345006459
    254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0
    
    SMART Error Log Version: 1
    ATA Error Count: 3280 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    
    Error 3280 occurred at disk power-on lifetime: 6591 hours (274 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:40:41.201  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:41.193  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:41.179  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:41.169  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:41.158  READ FPDMA QUEUED
    
    Error 3279 occurred at disk power-on lifetime: 6591 hours (274 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:40:22.878  READ FPDMA QUEUED
      27 00 00 00 00 00 e0 00      05:40:22.876  READ NATIVE MAX ADDRESS EXT
      ec 00 00 00 00 00 a0 00      05:40:22.875  IDENTIFY DEVICE
      ef 03 46 00 00 00 a0 00      05:40:22.874  SET FEATURES [Set transfer mode]
      27 00 00 00 00 00 e0 00      05:40:22.874  READ NATIVE MAX ADDRESS EXT
    
    Error 3278 occurred at disk power-on lifetime: 6591 hours (274 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:40:19.848  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:19.485  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:19.464  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:19.464  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:19.067  READ FPDMA QUEUED
    
    Error 3277 occurred at disk power-on lifetime: 6591 hours (274 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:40:00.205  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:00.183  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:00.162  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:00.139  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:00.117  READ FPDMA QUEUED
    
    Error 3276 occurred at disk power-on lifetime: 6591 hours (274 days + 15 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:39:54.112  READ FPDMA QUEUED
      27 00 00 00 00 00 e0 00      05:39:54.111  READ NATIVE MAX ADDRESS EXT
      ec 00 00 00 00 00 a0 00      05:39:54.110  IDENTIFY DEVICE
      ef 03 46 00 00 00 a0 00      05:39:54.109  SET FEATURES [Set transfer mode]
      27 00 00 00 00 00 e0 00      05:39:54.109  READ NATIVE MAX ADDRESS EXT
    
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Short offline       Completed: read failure       90%      6564         50765010
    # 2  Short offline       Completed without error       00%      5051         -
    # 3  Short offline       Completed without error       00%      4914         -
    # 4  Short offline       Completed without error       00%      4761         -
    # 5  Short offline       Completed without error       00%      4321         -
    # 6  Short offline       Completed without error       00%      4232         -
    # 7  Short offline       Completed without error       00%      4070         -
    # 8  Short offline       Completed without error       00%      3890         -
    # 9  Short offline       Completed without error       00%      3698         -
    #10  Short offline       Completed without error       00%      3454         -
    #11  Short offline       Completed without error       00%      3199         -
    #12  Short offline       Completed without error       00%      3157         -
    #13  Short offline       Completed without error       00%      3125         -
    #14  Short offline       Completed without error       00%      2947         -
    #15  Short offline       Completed without error       00%      2730         -
    #16  Short offline       Aborted by host               60%      2558         -
    #17  Short offline       Completed without error       00%      2164         -
    #18  Short offline       Aborted by host               90%      2164         -
    #19  Short offline       Completed without error       00%      1909         -
    #20  Short offline       Completed without error       00%         0         -
    
    SMART Selective self-test log data structure revision number 1
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Not_testing
        2        0        0  Not_testing
        3        0        0  Not_testing
        4        0        0  Not_testing
        5        0        0  Not_testing
    Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    Attached Images Attached Images
    Last edited by SineSpe; June 19th, 2013 at 12:02 AM.

  4. #14
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    Now the estimated time to completion is at about 112 hours. The amount of files found hasn't increased from 32,147 within the past couples hours, and the program keeps returning to read this one sector 19870288.

    I've read that the program may think a file is too small and is returning to that sector to see if any pieces fit, or something to that nature. Can anyone elaborate more on this for me? What's going on in my case, and is waiting the only solution? Thank you.

  5. #15
    Join Date
    Mar 2010
    Location
    India
    Beans
    7,721
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by SineSpe View Post
    Now the estimated time to completion is at about 112 hours. The amount of files found hasn't increased from 32,147 within the past couples hours, and the program keeps returning to read this one sector 19870288.
    I've never experienced that myself, nor have any idea why this could be happening.

    When it returns, does it sequentially increase again (with same speed)? If so, it is hopeless. Stop it and try the following if possible (or leave it running if there is some hopeful progress).

    Although if you "Stop" the recovery process, photorec is supposed to prompt you to "resume" from where it left when you stopped it (only one time, if you choose "No", it won't ask on next run), but I'm not very certain of that.

    * If the image was divided in partitions, you may choose to scan individual partitions to divide the job. Unfortunately, there is no other way to tell photorec to do a partial scan of a drive (apart from choosing to scan only "free space" which is helpful in recovering deleted files).

    * Otherwise, you may choose to 'exclude' certain file types which you are not interested in, hoping it may help skipping some problematic blocks. But I'm not sure if it will promp you to 'resume' if settings are changed.

    FWIW, I recently recovered data (selecting only pictures and video formats) from a physically crashed 320 GB hard disk in about 19 hours ! That was, in my experience, way too slow than I normally expect. But then again, "Get Data Back" (a top notch commercial tool from runtime software) took even longer with no better results.
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  6. #16
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by varunendra View Post
    * If the image was divided in partitions, you may choose to scan individual partitions to divide the job. Unfortunately, there is no other way to tell photorec to do a partial scan of a drive (apart from choosing to scan only "free space" which is helpful in recovering deleted files).

    * Otherwise, you may choose to 'exclude' certain file types which you are not interested in, hoping it may help skipping some problematic blocks. But I'm not sure if it will promp you to 'resume' if settings are changed.

    FWIW, I recently recovered data (selecting only pictures and video formats) from a physically crashed 320 GB hard disk in about 19 hours ! That was, in my experience, way too slow than I normally expect. But then again, "Get Data Back" (a top notch commercial tool from runtime software) took even longer with no better results.
    I found one person's account of having a similar problem to this and this was their take on it: "..the explanation is probably this: After each file Photorec finds it is trying to piece together a large previously found fragment with whatever comes after the newly found file. This means the large file fragment is read over and over again and only a small fraction of the time is spent reading new data. Does this explanation seem reasonable?"

    This person said that eventually, Photorec completed its business with the one sector and was able to continue reading files normally. I might leave it overnight and see what it does. Regardless...

    How would i have Photorec extract only the files with, say, picture, video, audio and word formats? Keep in mind, there are apparent "read errors" on the image, so i'm guessing this would be why i'm having a problem with this sector.
    Last edited by SineSpe; June 19th, 2013 at 04:57 AM.

  7. #17
    Join Date
    Mar 2010
    Location
    India
    Beans
    7,721
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by SineSpe View Post
    How would i have Photorec extract only the files with, say, picture, video, audio and word formats? Keep in mind, there are apparent "read errors" on the image, so i'm guessing this would be why i'm having a problem with this sector.
    Yes, I remember the image had read errors, that's why I asked if the progress was linear with same speed each time it falls back or jumps to newer sectors (or in a faster speed).

    The filter to look for specific file-types only has to be enabled before starting the scan. Since you seem to have made quite some progress now, I think you should leave it going as it is.

    The setting is under "Options" by the way (described in the step-by-step guide)
    Last edited by varunendra; June 19th, 2013 at 08:39 AM.
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  8. #18
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by varunendra View Post
    Yes, I remember the image had read errors, that's why I asked if the progress was linear with same speed each time it falls back or jumps to newer sectors (or in a faster speed).

    The filter to look for specific file-types only has to be enabled before starting the scan. Since you seem to have made quite some progress now, I think you should leave it going as it is.

    The setting is under "Options" by the way (described in the step-by-step guide)
    When it falls back to the weird sector, it does take quite a bit longer than when moving on the the next sector. I'd say it will only read the next sector for a few seconds until it falls back again.

    I've had the scan going for 13 hours now. Within the first two hours, i reached this weird sector, and after 11 additional hours, no new files have been recovered. I'm stuck around 32,147 files and an estimated time of 377 hours. I think what i'll do is leave it going overnight (about another 8 hours or so). If it's still getting hung up on this sector, I'll save what i have, start over and have Photorec only recover images, videos, audio, documents, i suppose. There's really no need for me to recover things i'm not looking to keep.

    If by the time i start over, we can find a way to skip/ignore these weird sectors, that would be great, in case the process gets caught up again.

  9. #19
    Join Date
    Aug 2005
    Beans
    5,990

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by SineSpe View Post
    This is the SMART information i received by commanding sudo smartctl --all /dev/sda3 :
    1. That drive is shot/broken.
    2. You're image you have of 278GB is not complete, dd does not work well with bad sectors/faulty drives. You're missing about 40GB of data.
    3. See post#10 again wrt GNU ddrescue, make sure you use a log file see the flag settings. Run it in the forward direction (normal) and when it starts picking up errors run it in reverse until it hits errors. Next run it in the forward direction again and let it do it's job. Read the documentation and subscribe to the mailing list if you have questions or need help. It's a very powerful tool. Only image the faulty partition you need to get data from and not the entire drive (assuming you have multiple partitions).

    Right now you are wasting your time working on a incomplete image.

  10. #20
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by mips View Post
    1. That drive is shot/broken.
    2. You're image you have of 278GB is not complete, dd does not work well with bad sectors/faulty drives. You're missing about 40GB of data.
    3. See post#10 again wrt GNU ddrescue, make sure you use a log file see the flag settings. Run it in the forward direction (normal) and when it starts picking up errors run it in reverse until it hits errors. Next run it in the forward direction again and let it do it's job. Read the documentation and subscribe to the mailing list if you have questions or need help. It's a very powerful tool. Only image the faulty partition you need to get data from and not the entire drive (assuming you have multiple partitions).

    Right now you are wasting your time working on a incomplete image.
    That's disappointing news considering that when i woke up, Photorec had worked its way past the weird sector. It's completed now with about 219,219 files. There's no harm in continuing to try, having the time.

    Quote Originally Posted by mips View Post
    Create an image file of the drive or partition using GNU ddrescue and ensure you enable the log file. Once you have an image you can mount it and try to recover from it. You can also use tools like testdisk/photorec on the image.

    You can also have a look at https://help.ubuntu.com/community/DataRecovery
    I'll see what I can do regarding GNU ddrescue. Will i need Lzip as well, or can i do without? In the meantime, out of curiosity, what feedback from Gsmartctl told you the hard drive was shot?

    EDIT: Also, i'm kind of stumped on how to get this program to work. I've downloaded the ddrescue 1.16 files and extracted them from the index (http://mirror.anl.gov/pub/gnu/ddrescue/), but i'm not sure where to go from here. Will the program work if on a USB, since my old computer is running from CD?
    Last edited by SineSpe; June 19th, 2013 at 05:00 PM.

Page 2 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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