Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

reiserfsck --check /dev/md13 HELP ERROR

Featured Replies

Hi there I am trying to get the data off disc 13. I do not think the parity is correct so I want to try and get the data off.

 

What do I need to do next?

I have copied and pasted the output from reiserfsck.

 

 

 

Will read-only check consistency of the filesystem on /dev/md13

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

 

The problem has occurred looks like a hardware problem. If you have

bad blocks, we advise you to get a new hard drive, because once you

get one bad block  that the disk  drive internals  cannot hide from

your sight,the chances of getting more are generally said to become

much higher  (precise statistics are unknown to us), and  this disk

drive is probably not expensive enough  for you to you to risk your

time and  data on it.  If you don't want to follow that follow that

advice then  if you have just a few bad blocks,  try writing to the

bad blocks  and see if the drive remaps  the bad blocks (that means

it takes a block  it has  in reserve  and allocates  it for use for

of that block number).  If it cannot remap the block,  use badblock

option (-B) with  reiserfs utils to handle this block correctly.

 

bread: Cannot read the block (2): (Input/output error).

 

Aborted (core dumped)

root@Tower:~#

  • Author

Here is the smart report

 

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Model Family:    SAMSUNG SpinPoint F1 DT series

Device Model:    SAMSUNG HD103UJ

Serial Number:    S13PJDWQ812999

Firmware Version: 1AA01113

User Capacity:    1,000,204,886,016 bytes

Device is:        In smartctl database [for details use: -P show]

ATA Version is:  8

ATA Standard is:  ATA-8-ACS revision 3b

Local Time is:    Wed Jul 24 19:21:15 2013 NDT

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

 

General SMART Values:

Offline data collection status:  (0x00) Offline data collection activity

was never started.

Auto Offline Data Collection: Disabled.

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: (11733) 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: ( 196) minutes.

Conveyance self-test routine

recommended polling time: (  21) minutes.

SCT capabilities:       (0x003f) SCT Status supported.

SCT Error Recovery Control supported.

SCT Feature Control supported.

SCT Data Table supported.

 

SMART Attributes Data Structure revision number: 16

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  100  100  051    Pre-fail  Always      -      0

  3 Spin_Up_Time            0x0007  076  076  011    Pre-fail  Always      -      7960

  4 Start_Stop_Count        0x0032  099  099  000    Old_age  Always      -      919

  5 Reallocated_Sector_Ct  0x0033  100  100  010    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x000f  100  100  051    Pre-fail  Always      -      0

  8 Seek_Time_Performance  0x0025  100  100  015    Pre-fail  Offline      -      0

  9 Power_On_Hours          0x0032  094  094  000    Old_age  Always      -      31142

10 Spin_Retry_Count        0x0033  100  100  051    Pre-fail  Always      -      1

11 Calibration_Retry_Count 0x0012  100  100  000    Old_age  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      172

13 Read_Soft_Error_Rate    0x000e  100  100  000    Old_age  Always      -      0

183 Runtime_Bad_Block      0x0032  100  100  000    Old_age  Always      -      0

184 End-to-End_Error        0x0033  025  025  000    Pre-fail  Always      -      75

187 Reported_Uncorrect      0x0032  100  100  000    Old_age  Always      -      0

188 Command_Timeout        0x0032  100  100  000    Old_age  Always      -      0

190 Airflow_Temperature_Cel 0x0022  063  046  000    Old_age  Always      -      37 (Min/Max 30/37)

194 Temperature_Celsius    0x0022  055  045  000    Old_age  Always      -      45 (0 28 45 30)

195 Hardware_ECC_Recovered  0x001a  100  100  000    Old_age  Always      -      1879

196 Reallocated_Event_Count 0x0032  100  100  000    Old_age  Always      -      0

197 Current_Pending_Sector  0x0012  100  100  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0030  100  100  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x003e  100  100  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x000a  100  100  000    Old_age  Always      -      1

201 Soft_Read_Error_Rate    0x000a  253  253  000    Old_age  Always      -      0

 

SMART Error Log Version: 1

No Errors Logged

 

SMART Self-test log structure revision number 1

No self-tests have been logged.  [To run self-tests, use: smartctl -t]

 

 

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.

  • Author

Here is

Partition info.

 

 

 

Disk /dev/sdq: 1000.2 GB, 1000204886016 bytes

1 heads, 63 sectors/track, 31008336 cylinders

Units = cylinders of 63 * 512 = 32256 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start        End      Blocks  Id  System

/dev/sdq1              2    31008336  976762552+  83  Linux

Partition 1 does not end on cylinder boundary.

Try running --check on the /dev/sdX device label, where X is the correct letter assignment.

Try running --check on the /dev/sdX device label, where X is the correct letter assignment.

NO!!!!!!!!!!!!!

 

The file system is on the first partition, NOT the raw device.,    dgachk gave you wrong advice.  The command he asked you to run will result in reiserfsck sataing it cannot find the superblock... since it is NOT where you are asking it to look.

 

You must run the command on the FIRST PARTITION. (when not using the "md" devices at /dev/mdX which automatically point to the first partition on each disk) 

 

The device name for the first partition of the physical disk has a trailing "1" in its name.

reiserfsck --check /dev/sdq1

 

Note that by correcting anything on the raw device that parity is NOT maintained and that you must subsequently run a correcting parity sync to fix parity and get it in sync.

 

Joe L.

 

 

 

If the array is started in Maintenance mode, then you could run

reiserfsck --check /dev/md13

Because you are using the array device this would maintain parity (if it happens to be valid at this point).  Also because you are using the array device name you do not need to specify the partition as this has already been mapped to the relevant md device.

  • Author

Thanks for the help so far.

 

So the progress I made so far

 

I got the data "Fixed and mounted the drive" but the files are damaged :(

 

So then I did the trust the parity procedure and moved disc 13 to the cache position and the drive contents seem fine even though I though the parity was incorrect.

 

So now I am going to copy the contents from the parity disc 13 to another drive on my server.

 

Then once that completes I will move disc 13 back to the normal position and rebuild the data.

 

 

Then I am guessing I will need reiserfsk --check to ensure the drive is correct and then test some of the contents. And then I can recheck parity.

Does this seem like the best option??

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.