slaveunit

Here were my results. There was a newly created lost+found with nothing in it. After remounting everything seems normal again. Thanks Joe L. reiserfsck --rebuild-tree started at Sun Jun 26 23:22:51 2011 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 450959478 blocks marked used Skipping 23115 blocks (super block, journal, bitmaps) 450936363 blocks will be read 0%.. left 406925961, 29242 /sec left 84571607, 24259 /secc left 0, 21907 /secc 3962 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 450936363 Leaves among those 445704 - leaves all contents of which could not be saved and deleted 1 Objectids found 3964 Pass 1 (will try to insert 445703 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 66 /sec Flushing..finished 445703 leaves read 445701 inserted 2 not inserted ####### Pass 2 ####### Pass 2: 0%....20%....40%....60%....80%....100% left 0, 0 /sec Flushing..finished Leaves inserted item by item 2 Pass 3 (semantic): ####### Pass 3 ######### ... s - The Pathologists Report Part IV Epidemic/CARCASS CHAPTER 4 MOSH 097.isovpf-10680: The file [392 393] has the wrong block count in the StatData (5031936) - corrected to (832248) Flushing..finished Files found: 3553 Directories found: 411 Broken (of files/symlinks/others): 1 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Flushing..finished13, 39 /sec Pass 4 - finished done 428543, 27 /sec Deleted unreachable items 518 Flushing..finished Syncing..finished ########### reiserfsck finished at Mon Jun 27 11:23:55 2011 ###########

I get the feeling this is going to take quite a long time on a 2tb drive moving at 30MB/sec.

Today I was using MC to move some files around and one certain ones I received and error that stated they cannot be deleted because the filesystem is read only. I looked in the syslog and it kept repeating that one of the blocks was bad on my disk and that I should run FSCK. So I stop samba and unmount the drive then proceed to run the reiserfsck --check /dev/md5 command. Here are my results. Just to be safe I would like to get some opinions if I should proceed or not. This is version 4.6 and I did not save my syslog before rebooting. I know I should have. root@Tower:~# reiserfsck --check /dev/md5 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md5 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sun Jun 26 21:09:29 2011 ########### Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. \/ 4 (of 18|/ 27 (of 153\/104 (of 114\block 20114674: The level of the node (33576) is not correct, (1) expected the problem in the internal node occured (20114674), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Sun Jun 26 22:43:25 2011 ###########

You could try reading one page back where I posted "I think the easiest way to do this is". I didn't check to see if my data was erased from the drive. Before I updated it I took it out of the array and started the array without it. That way it would rebuild after the update. I did only have one data drive that was a samsung F4.

I have a plain jane Gigabyte MB with the drive connected via sata. I didnt look to see if I had any legacy enabled but the update worked fine on it. Pras1011 did you try the page I linked for the DOS system files? Once you build that you just copy the samsung file on it and boot from the flash then run the samsung exe file.

IF you can boot into DOS from a flash drive and it will see the esata port, I dont see why it wouldnt work.

Just curious...how does a laptop have a pci express card in it?

I think the easiest way to patch if you do not want to remove your drive is to unplug either the sata or the power from all drives but the samsung one. Then boot from a seperate flash drive with the upgrade on it. Here is a simple tutorial for getting DOS boot files onto a flash drive. http://thelostbrain.com/post/2008/01/Make-your-flash-drive-bootable!-%28Boot-into-DOS-with-access-to-full-flash-drive-space%29.aspx

Nevermind.

Until a fw fix comes out wouldn't we want to disable the write cache in the middle of your process Joe? Thanks.

If you have one of these drives I'd suggest a read only parity check. You can do it from the command line. /root/mdcmd check READONLY If it shows no errors you are fine. It will look exactly like the normal check and the web-interface will still say it is correcting the errors but it is not. If it does show parity errors AND if you ONLY have one of the F4 drives in your array, you can Stop the array un-assign the F4 drive Start the array with it un-assigned (This will cause the array to forget its serial number so it can be used as its own replacement) Stop the array once more Re-Assign the F4 drive Start the array again... It will re-construct the data onto the F4 drive. It will have the correct data. This is assuming the F4 drive is a data drive and not the parity drive. If the F4 drive is the parity drive just do a normal parity "Check" and it will be corrected based on the actual data on the data disk. You'll be without parity protection for the duration of the re-construction but since you are actually only writing what is already there for most of the disk you are no worse off than with the corruption. (You could force the F4 data disk to be valid if another were to fail during the process.) Joe L. Is that the actual command? Is readonly supposed to be in all CAPS? If so I get this: root@Tower:~# /root/mdcmd check READONLY /root/mdcmd: line 11: echo: write error: Invalid argument

I really hope this gets solved from Samsung by the end of this week. It will ease some of our stress. Although other sources say not http://hardforum.com/showpost.php?p=1036531314&postcount=26

Any way in the official versions (not the uumenu) we can get totals for the drive sizes, free space and maybe errors at the bottom of the screen?

On the NIC question, yes. I was updating the fw on the router the unRAID is connected to. I am currently running the reiserfsck --rebuild-tree now and will then run another --check to see if it fixed the issue. I will report results when complete. Update: Its now completed. Here are the results. It looks like it did fix it. root@Tower:~# reiserfsck --check /dev/md15 reiserfsck 3.6.19 (2003 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md15 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Mon Jun 14 12:53:19 2010 ########### Replaying journal.. Reiserfs journal '/dev/md15' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 159504 Internal nodes 970 Directories 82 Other files 138 Data block pointers 161395625 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Mon Jun 14 13:41:11 2010 ########### root@Tower:~# Thanks very much for your time Joe!!

I didn't look previously. Im not 100% keen on how to read all he sections here. I do see some errors with the on time. root@Tower:/dev# smartctl -d ata -a /dev/sdq smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS1R38D Firmware Version: CC1H User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Jun 14 09:10:16 2010 GMT+8 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: (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: ( 609) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status 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 105 095 006 Pre-fail Always - 8067228 3 Spin_Up_Time 0x0003 096 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 56 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 061 060 030 Pre-fail Always - 1367503 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 896 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 30 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 156 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 041 041 000 Old_age Always - 59 190 Airflow_Temperature_Cel 0x0022 070 068 045 Old_age Always - 30 (Lifetime Min/Ma x 22/31) 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 20 0 0) 195 Hardware_ECC_Recovered 0x001a 040 033 000 Old_age Always - 8067228 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 38001870635228 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3759789166 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3403232947 SMART Error Log Version: 1 ATA Error Count: 156 (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 156 occurred at disk power-on lifetime: 175 hours (7 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 1d+10:45:08.277 READ DMA EXT 27 00 00 00 00 00 e0 00 1d+10:45:08.248 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+10:45:08.228 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+10:45:08.209 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 1d+10:45:08.047 READ NATIVE MAX ADDRESS EXT Error 155 occurred at disk power-on lifetime: 175 hours (7 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 1d+10:45:05.291 READ DMA EXT 27 00 00 00 00 00 e0 00 1d+10:45:05.261 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+10:45:05.241 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+10:45:05.222 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 1d+10:45:05.131 READ NATIVE MAX ADDRESS EXT Error 154 occurred at disk power-on lifetime: 175 hours (7 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 1d+10:45:02.284 READ DMA EXT 27 00 00 00 00 00 e0 00 1d+10:45:02.255 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+10:45:02.235 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+10:45:02.215 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 1d+10:45:02.054 READ NATIVE MAX ADDRESS EXT Error 153 occurred at disk power-on lifetime: 175 hours (7 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 1d+10:44:59.277 READ DMA EXT 27 00 00 00 00 00 e0 00 1d+10:44:59.248 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+10:44:59.228 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+10:44:59.209 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 1d+10:44:59.128 READ NATIVE MAX ADDRESS EXT Error 152 occurred at disk power-on lifetime: 175 hours (7 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 1d+10:44:56.281 READ DMA EXT 27 00 00 00 00 00 e0 00 1d+10:44:56.252 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 1d+10:44:56.232 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 1d+10:44:56.212 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 1d+10:44:56.052 READ NATIVE MAX ADDRESS EXT 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. root@Tower:/dev#

Thanks for the quick reply. Is there any risk of data loss by running this? Would it be safer just to RMA the drive?

Hello All, Since there is no 4.5.x thread in the support section I am posting here. I noticed on my console some errors suggesting me to run FSCK this morning. So following the wiki I ran "reiserfsck --check /dev/md1" My FSCK return was: Trans replayed: mountid 20, transid 66029, desc 428, len 9, commit 438, next trans offset 421 Trans replayed: mountid 20, transid 66030, desc 439, len 9, commit 449, next trans offset 432 Trans replayed: mountid 20, transid 66031, desc 450, len 10, commit 461, next trans offset 444 Trans replayed: mountid 20, transid 66032, desc 462, len 14, commit 477, next trans offset 460 Trans replayed: mountid 20, transid 66033, desc 478, len 1, commit 480, next trans offset 463 Trans replayed: mountid 20, transid 66034, desc 481, len 9, commit 491, next trans offset 474 Trans replayed: mountid 20, transid 66035, desc 492, len 71, commit 564, next trans offset 547 Trans replayed: mountid 20, transid 66036, desc 565, len 14, commit 580, next trans offset 563 Reiserfs journal '/dev/md15' in blocks [18..8211]: 618 transactions replayed Checking internal tree../ 1 (of 6)/ 13 (of 170)/144 (of 170)block 38887627: The level of the node (0) is not correct , (1) expected the problem in the internal node occured (38887627), whole subtree is skipped finished ) Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Mon Jun 14 08:02:01 2010 ########### root@Tower:~# So since it is asking me to run the "--rebuild-tree" switch I am asking for advice here. If it matters at all I did not reboot the box before running FSCK. syslog is too large to attach so I have posted it at pastebin: http://pastebin.com/EqUQuUF1

Drives spin up one after another for a good reason. Spinning up a drive is the time when it draws most power. Imagine the spike if all your drives were to spin up at the same time. No power supply would survive that. Purko So what happens when you power the machine on? They all spin up at once right? Your PSU handles it fine.

Thanks. Grabbed a couple of the 4x ones. This will really clean up the cabling some more in an Antec 1200 with 16 drives.

Grabbed it as well. thanks Weeb!

On the 590 case would you guys say it better to run your PSU upside down? Im just curious...Im not sure if it would be better or worse for airflow. I have mine like this for now because until I finish a room where it will be placed it is sitting on carpet. I guess I can stick a piece of thin wood under it so it doesnt suck the carpet up.

frys.com is sold out.

3 year warranty I believe?

Add a couple/few cooler master 4in3 drive bays and 12 drives total isnt bad.

Nice price. These are $99 on newegg after a $40 rebate. This one has no rebates and is $69. http://newspaperads.mercurynews.com/ROP/ads.aspx?advid=32664&adid=6252119&subid=21405550&type=