May 15, 201214 yr Hello Was copying some movies up to the server today and got errors. Before this, all was working ok. I am 5.0-beta14. Disk 5 was blinking red and showed errors in the error counts. I stopped the array. Then after the array was stopped, Disk 4 says "WRONG" - see screen shot. I was copying via robocopy and forgot about it for a while so the errors are repeated in the log, which is also attached, as robocopy kept retrying. I am afraid to do anything at this point without some help. Thanks!! syslog.zip
May 15, 201214 yr Author I just unzipped it on my work PC and it worked fine? rezipped with pkzip this time syslog2.zip
May 15, 201214 yr Run a smart test on disk4 May 14 14:55:41 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen May 14 14:55:41 Tower kernel: ata4.00: failed command: READ DMA . . . . May 14 15:06:41 Tower kernel: md: disk4 read error May 14 15:06:41 Tower kernel: handle_stripe read error: 7576/4, count: 1 and here is disk5 errors: May 14 15:06:54 Tower shfs/user: shfs_create: open: /mnt/disk5/Media/Movies/the confession (2011)/VIDEO_TS/VTS_01_2.VOB (5) Input/output error May 14 15:06:54 Tower kernel: md: disk4 read error May 14 15:06:54 Tower kernel: handle_stripe read error: 935067648/4, count: 1 May 14 15:06:54 Tower kernel: REISERFS error (device md5): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 116883456 is corrupted: first bit must be 1 May 14 15:06:54 Tower kernel: REISERFS (device md5): Remounting filesystem read-only
May 15, 201214 yr Author Ok. A quick (and maybe dumb) is there a smart test option from within the new UI or do I still need to go to the unix command line? Thanks
May 15, 201214 yr Still running 4.7 here..but I believe there is. Also here is some background on the disk5 error..that will have to be fixed first, if disk4 is dying/dead. http://lime-technology.com/forum/index.php?topic=5951.msg56606#msg56606
May 16, 201214 yr Author Do I run with the rebuild as instructed? Getting worried - here is the command line log: root@Tower:~# reiserfsck --fix-fixable /dev/sde 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 check consistency of the filesystem on /dev/sde and will fix what can be fixed without --rebuild-tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes reiserfs_open: the reiserfs superblock cannot be found on /dev/sde. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. root@Tower:~#
May 16, 201214 yr Do I run with the rebuild as instructed? Getting worried - here is the command line log: root@Tower:~# reiserfsck --fix-fixable /dev/sde 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 check consistency of the filesystem on /dev/sde and will fix what can be fixed without --rebuild-tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes reiserfs_open: the reiserfs superblock cannot be found on /dev/sde. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. root@Tower:~# no, because the partition is /dev/sde1 not /dev/sde You will never find a partition if you just use the base name of the drive. start again with reiserfsck --check /dev/sde1 followed by reiserfsck --fix-fixabble /dev/sde1 etc... HOWERVER... if you expect to keep parity in sync, you really need to do this on /dev/md5 reiserfsck --fix-fixable /dev/md5 (for disk5) If you do not use the "md" device, parity will not be kept in sync and you'll have parity errors the next time you check. If you did use the raw device, don't worry, just run a correcting parity sync and it should fix the corruption you caused.
May 16, 201214 yr Author Tried running the smart report on disk 4 which failed so I ran the below: root@Tower:~# smartctl -a -d auto /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 Short INQUIRY response, skip product id A mandatory SMART command failed: exiting. To continue, add one or more '-T perm issive' options. Does this mean the drive is very very toast? Ran the short test on disk5 and it showed read failures. 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% 3135 2916616800 So, both disks are bad? Can I replace two out of 5 disks without loosing data? How should I proceed? Disk 4 first since it is really gone then do disk 5? Thanks
May 16, 201214 yr read my prior post. Then stop the array, power down, re-seat the cables o the drive that is not responding... It could be as simple as a loose/bad cable.
May 16, 201214 yr Author Thanks Joe. I ran the reiserfsck --check /dev/sde1 and here is what it said: . . . Replaying journal: Done. Reiserfs journal '/dev/sde1' in blocks [18..8211]: 107 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 76233 Internal nodes 469 Directories 195 Other files 592 Data block pointers 77058510 (538820 of them are zero) Safe links 0 ########### reiserfsck finished at Tue May 15 19:55:36 2012 ########### root@Tower:~# Runing the reiserfsck --fix-fixable /dev/md5 shows the following: root@Tower:~# reiserfsck --fix-fixable /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 check consistency of the filesystem on /dev/md5 and will fix what can be fixed without --rebuild-tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Failed to open the device '/dev/md5': No such file or directory Going shut down and reseat the cables. Hopefully thats it.
May 16, 201214 yr The "md" device will not exist unless the array is started, but in any case, it looks like the drive is fine (assuming /dev/sde1 is assigned as disk5 ... and becomes /dev/md5)
May 16, 201214 yr Author Joe, I reseated the cables and restarted. The array started. Disk 4 no longer has a red button, but Disk 5 does on the UI page (scrrenshot attached). I ran smartctl and it now finds disk 4. (whew). No errors on the smartctl, report attached. I ran smartctl on disk 5 again. Same error as last time. Report attached. I ran the reiserfsck --fix-fixable /dev/md5 again. It said Partition /dev/md5 is mounted with write permissions, cannot check it. Disk 5 (with the red ball) settings say: --Partition 1 size: 1953514552 KB (K=1024) --Partition format: MBR: unaligned --File sytem type: reiserfs Current syslog is also attached. disk5_smartctl_report.txt disk4_smartctl_report.txt syslog.txt
May 16, 201214 yr Author I found in the wiki how to run it. It found 1 issue and was fixed. Below is the process. I rebooted again. Disk 5 is still red -- what is causing this - the error on the smartctl report? Syslog from the latest boot is attached. root@Tower:~# samba stop root@Tower:~# umount /dev/md5 root@Tower:~# reiserfsck --check /dev/md5 reiserfsck 3.6.21 (2009 www.namesys.com) 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 Tue May 15 21:14:40 2012 ########### Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Checking Semantic tree: finished 1 found corruptions can be fixed when running with --fix-fixable ########### reiserfsck finished at Tue May 15 21:18:53 2012 ########### root@Tower:~# reiserfsck --fix-fixable /dev/md5 reiserfsck 3.6.21 (2009 www.namesys.com) Will check consistency of the filesystem on /dev/md5 and will fix what can be fixed without --rebuild-tree 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 --fix-fixable started at Tue May 15 21:19:06 2012 ########### Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10630: The on-disk and the correct bitmaps differs. Will be fixed later. Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 146225 Internal nodes 891 Directories 374 Other files 1121 Data block pointers 147812974 (343136 of them are zero) Safe links 0 ########### reiserfsck finished at Tue May 15 21:28:41 2012 syslog.txt
May 16, 201214 yr See here: http://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F
Archived
This topic is now archived and is closed to further replies.