October 12, 201114 yr After I upgraded I tried running Utils/New Permissions as instructed. It appeared to have worked but I was having problems with disk5. I couldn't seem to write to the disk. I found this thread http://lime-technology.com/forum/index.php?topic=15115.0 and followed the instructions to run a single disk via terminal. What resulted was; chown: changing ownership of 'mnt/disk5/' : Read-only file system In the above thread, prostuff1 advised the OP to do a reiserfsck --check. Is this what I should do as well? I have attached my syslog, thanks in advance. sys1.txt
October 13, 201114 yr This shows that disk5 has been mounted read only due to a file system corruption Oct 12 16:21:02 ensconce kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 Oct 12 16:21:02 ensconce kernel: REISERFS error (device md5): vs-5150 search_by_key: invalid format found in block 45537045. Fsck? Oct 12 16:21:02 ensconce kernel: REISERFS (device md5): Remounting filesystem read-only To perform a file system check follow the directions here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
October 13, 201114 yr Author thanks. After a reiserfsck --check on the disk it reported run reiserfsck --rebuild-tree. Looks like it will be a while.
October 13, 201114 yr Author Where do I view 'stdout'? When I got up this morning the reiserfsck --rebuild-tree looked like it has finished. But when I try to remount the drive 'mount /dev/md5 /mnt/disk5' terminal reports that the mount point does not exists.
October 13, 201114 yr Author Just did another reiserfsk --check. Terminal reports 'bad root block 0 (--rebuild-tree did not complete) Can anyone advise on how to proceed? thanks.
October 13, 201114 yr Run rebuild tree again. The telnet window must remain open for the duration. It is safer to use the console or the screen utility.
October 14, 201114 yr Author thanks dgaschk. I am running these commands via IMPI... i'll report back once it's finished.
October 14, 201114 yr Author is this normal while --rebuild-tree? Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721280/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721288/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721296/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721304/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721312/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721320/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721328/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721336/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721344/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721352/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721360/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721368/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721376/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721384/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721392/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721400/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721408/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721416/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721424/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721432/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721440/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721448/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721456/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721464/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721472/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721480/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721488/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721496/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721504/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721512/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721520/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721528/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721536/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721544/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721552/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721560/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721568/5, count: 1 (Errors) Oct 13 23:16:56 ensconce kernel: md: disk5 read error (Errors) Oct 13 23:16:56 ensconce kernel: handle_stripe read error: 356721576/5, count: 1 (Errors) Oct 13 23:16:58 ensconce kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)
October 14, 201114 yr Those are read errors. If your running reiserfsck on disk5 that is a bad sign. Let it finish and then post a smart report for disk5.
October 16, 201114 yr Author alright. So I after patiently waiting for reiserfsck --rebuild-tree to complete for ~31 hours console reports; The problem has occurred looks like a hardware problem (perhaps memory). Send us a bug report if the second run dies at the same block number. build_the_tree: Nothing but leaves are expected. Block 43702269 - Unknown. Aborted. Smart Status Report; Statistics for /dev/sdf SAMSUNG_HD203WI_S27KJ1MSC02559 smartctl -a -d ata /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: SAMSUNG HD203WI Serial Number: S27KJ1MSC02559 Firmware Version: 1AN10002 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 6 Local Time is: Sat Oct 15 20:06:59 2011 EDT 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. 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: (25500) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 255) 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 0x002f 001 001 051 Pre-fail Always FAILING_NOW 133594 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 062 061 025 Pre-fail Always - 11725 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 3020 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 919 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 171 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 16 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 28 (Min/Max 15/33) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 98 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 2 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 1 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 6615 SMART Error Log Version: 1 ATA Error Count: 894 (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 894 occurred at disk power-on lifetime: 919 hours (38 days + 7 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 37 28 03 01 e0 Error: UNC 55 sectors at LBA = 0x00010328 = 66344 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 40 1f 03 01 e0 08 00:14:41.099 READ DMA ef 10 02 00 00 00 a0 08 00:14:41.099 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 08 00:14:41.099 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:14:41.099 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:14:41.099 SET FEATURES [set transfer mode] Error 893 occurred at disk power-on lifetime: 919 hours (38 days + 7 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 37 28 03 01 e0 Error: UNC 55 sectors at LBA = 0x00010328 = 66344 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 40 1f 03 01 e0 08 00:14:41.098 READ DMA ef 10 02 00 00 00 a0 08 00:14:41.098 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 08 00:14:41.098 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:14:41.098 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:14:41.098 SET FEATURES [set transfer mode] Error 892 occurred at disk power-on lifetime: 919 hours (38 days + 7 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 37 28 03 01 e0 Error: UNC 55 sectors at LBA = 0x00010328 = 66344 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 40 1f 03 01 e0 08 00:14:41.096 READ DMA ef 10 02 00 00 00 a0 08 00:14:41.096 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 08 00:14:41.096 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:14:41.096 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:14:41.096 SET FEATURES [set transfer mode] Error 891 occurred at disk power-on lifetime: 919 hours (38 days + 7 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 37 28 03 01 e0 Error: UNC 55 sectors at LBA = 0x00010328 = 66344 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 40 1f 03 01 e0 08 00:14:41.095 READ DMA ef 10 02 00 00 00 a0 08 00:14:41.095 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 08 00:14:41.095 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:14:41.095 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 00:14:41.095 IDENTIFY DEVICE Error 890 occurred at disk power-on lifetime: 919 hours (38 days + 7 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 37 28 03 01 e0 Error: UNC 55 sectors at LBA = 0x00010328 = 66344 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 40 1f 03 01 e0 08 00:14:41.093 READ DMA ef 10 02 00 00 00 a0 08 00:14:41.093 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 08 00:14:41.093 READ NATIVE MAX ADDRESS EXT 27 00 00 00 00 00 e0 08 00:14:41.093 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:14:41.093 IDENTIFY DEVICE SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 851 - # 2 Short offline Completed without error 00% 850 - # 3 Extended offline Aborted by host 90% 850 - # 4 Short offline Completed without error 00% 16 - # 5 Short offline Completed without error 00% 15 - # 6 Short offline Aborted by host 50% 15 - # 7 Short offline Aborted by host 80% 15 - # 8 Short offline Completed without error 00% 15 - # 9 Short offline Aborted by host 90% 15 - #10 Short offline Completed without error 00% 15 - #11 Short offline Completed: read failure 90% 8 3907028995 Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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. Syslog; http://pastebin.com/bJGf9bM1
October 16, 201114 yr Author I understand the disk is failing, I'm trying to mount it (disk5) to copy some data off of it. The following error while I try to mount... root@ensconce:~# mount /dev/md5 /mnt/disk5 REISERFS error (device md5): vs-5150 search_by_key : invalid format found in block 0. Fsck? REISERFS error (device md5): vs-13070 reiserfs_read_locked_inode: i/o failure occured trying to start data of [1 2 0x0 SD] mount: /dev/md5: can't read superblock
October 16, 201114 yr Start the array with the disk unassigned then copy from the simulated disk. Or you could just rebuild the disk on to a pre-cleared disk.
October 16, 201114 yr Author I just got a new drive. After some reading, I think I should disconnect 2 of the drives in my array so I can preclear the replacement disk, then connect all drives and start my array so it will start a data rebuild. Is this correct?
October 16, 201114 yr You don't have to remove any disks to pre-clear. The array will not start automatically with one disk missing.
October 18, 201114 yr Author I ran preclear.sh on my new disk (version 1.13) and then I assigned the precleared disk to my array and started the array to rebuild the disk. After the re-build my array is online but my new disk show up as unformatted. I don't know where I have gone wrong. Advice would be great. Thanks. preclear_reports.zip syslog.txt.zip
October 18, 201114 yr Following rebuild formatting is not necessary. I would reboot, and then if the problem persists I would PM Joe L. to request he take a look at this thread. I suspect the problem is corrupted ReiserFS or MBR alignment issues. Did you install a jumper on the drive? Did you use the -A switch when preclearing? What is the Disk>Settings>Default partition format: set to?
October 18, 201114 yr Author I tired a reboot but the problem still exists. I did not jumper this drive. I have set the partition format to 4k aligned. If I run reiserfsck --check on the new disk, terminal reports bad root block 0 (--rebuild-tree did not complete) I will PM Joe L. Thanks for your assistance. to answer your edit: I did not use -A
October 18, 201114 yr Follow the steps in this thread: http://lime-technology.com/forum/index.php?topic=15385.0 I'm particularly interested in the results of the "dd" commands as described in this post: http://lime-technology.com/forum/index.php?topic=15385.msg144723#msg144723 as it dumps of the initial part of the disk to learn where the file system actually resides.
October 18, 201114 yr Author Thanks, Joe L. The original disk 5 failed. It was added to the array when I was running 4.6. I'm running 5.0-beta12a currently. I precleared the 'new' disk 5 with 1.13 and did not specify -a or -A. I have set the partition format to 4k aligned via disk settings. root@ensconce:~# fdisk -lu /dev/sdf Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdf1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. I suspect they will indicate the partition starts on sector 64 (in error) instead of sector 63. It is easy to fix, takes a few seconds, but need you to tell me if they were originally added in a version of unRAID before 4.7. edit: whoops; forgot the dd... root@ensconce:~# dd if=/dev/sdf count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.424443 s, 235 kB/s 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 \0 \0 203 \0 \0 \0 @ \0 \0 \0 p 210 340 350 \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098304 016 021 034 035 ! \b " 035 \0 \0 \0 \0 022 \0 \0 \0 0098320 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 I 021 031 G 0098336 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 \0 020 314 003 0098352 016 \0 002 \0 R e I s E r 2 F s \0 002 372 0098368 003 \0 \0 \0 377 377 9 : 002 \0 \0 \0 031 I \0 \0 0098384 001 \0 \0 \0 315 226 206 c 355 027 C D 205 026 340 314 0098400 211 v r 242 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0098416 \0 \0 \0 \0 025 \0 036 \0 270 6 035 M \0 N 355 \0 0098432 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 001 \0 \0 \0 0098512 325 \b \0 \0 : \b \0 \0 m \b \0 \0 W \b \0 \0 0098528 ` 016 \0 \0 \ 016 \0 \0 A 016 \0 \0 @ 016 \0 \0 0098544 204 203 \0 \0 206 203 \0 \0 006 204 \0 \0 002 204 \0 \0 0098560 c 206 \0 \0 O 206 \0 \0 206 \0 \0 307 214 \0 \0 0098576 001 272 \0 \0 002 272 \0 \0 \t 272 \0 \0 215 273 \0 \0 0098592 211 273 \0 \0 344 003 \0 \0 . 003 \0 \0 002 003 \0 \0 0098608 5 002 \0 \0 021 002 \0 \0 037 002 \0 \0 o 002 \0 \0 0098624 \n 002 \0 \0 X 001 \0 \0 342 006 \0 \0 302 006 \0 \0 0098640 215 005 \0 \0 270 005 \0 \0 032 005 \0 \0 371 017 \0 \0 0098656 1 9 \0 \0 / 9 \0 \0 222 > \0 \0 a ? \0 \0 0098672 \f = \0 \0 023 = \0 \0 247 = \0 \0 ^ 7 \0 \0
October 19, 201114 yr Author root@ensconce:/boot# unraid_partition_disk.sh -A /dev/sdf BLKRRPART: Device or resource busy This disk is currently in use. ######################################################################## Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZAA658248 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdf1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. ######################################################################## ============================================================================ == == DISK /dev/sdf IS partitioned for unRAID properly == expected start = 64, actual start = 64 == expected size = 3907029104, actual size = 3907029104 == ============================================================================ I'm confused. Disk is partitioned properly?
October 19, 201114 yr Your file system is starting at sector 64. I suspect that your system thinks it starts at sector 63 but I don't know where to get that information from what you have provided (just my ignorance). You can get that from clicking on the disk5 link on the main tab of the unraid web management page. "MBR: unaligned" means sector 63. Your next step would be to correct the MBR if it is wrong. Joe L. mentions two methods to do so in this post: http://lime-technology.com/forum/index.php?topic=15385.msg144822#msg144822 I think you should wait until Joe L. confirms this, but it sounds like this is the right approach and that you will be back up and running soon.
October 19, 201114 yr Author Thanks for your comment. I clicked on disk5 link and the partition format is 4k-aligned, so sector 64? So that seems to match. I downloaded the script Joe L. posted (unraid_partition_disk.sh) and it states the disk is partitioned correctly. I'll indeed wait to see if Joe L. chimes in further.
October 19, 201114 yr Thanks for your comment. I clicked on disk5 link and the partition format is 4k-aligned, so sector 64? So that seems to match. I downloaded the script Joe L. posted (unraid_partition_disk.sh) and it states the disk is partitioned correctly. I'll indeed wait to see if Joe L. chimes in further. fdisk shows the MBR is set to start the partition on sector 64. The partition definition in the MBR looks correct (verified by the script I wrote) The actual reiserfs file system seems to start on address 0098304 which is 512 bytes greater than the 0097792 address in the example dump from my server of a partition on my server starting on sector 63. This confirms you have a reiserfs in a partition starting on sector 64. If the partition was associated with on the /dev/md5 device then you could run reiserfsck on /dev/md5 If not, and reiserfsck says it cannot open /dev/md5, you'll need to run it on /dev/sdf1 and then run a correcting parity calc to get parity into sync once more. Start by trying reiserfsck --check /dev/md5 it will instruct you how to proceed.
Archived
This topic is now archived and is closed to further replies.