May 18, 201016 yr I ran into a problem that's got me stumped. I had a drive that reported some bad stuff on the SMART report (even though the report says "Passed", it had self recovered from a bunch of serious errors). I replaced it with a new, identical drive, and Unraid rebuilt from parity. The array boots up fine, and everything seems to have been rebuilt correctly on the drive. However, the drive acts as read-only. I took a look at the log, and I see that the system detected some issues & purposely made it that way. Can anybody please give me some guidance to get things back to normal? I've attached the syslog and the SMART report of the failed disk. Thanks so much for any help. BB syslog-2010-05-18.txt Disk4_SMART_Report_05-17-10.txt
May 18, 201016 yr I ran into a problem that's got me stumped. I had a drive that reported some bad stuff on the SMART report (even though the report says "Passed", it had self recovered from a bunch of serious errors). I replaced it with a new, identical drive, and Unraid rebuilt from parity. The array boots up fine, and everything seems to have been rebuilt correctly on the drive. However, the drive acts as read-only. I took a look at the log, and I see that the system detected some issues & purposely made it that way. Can anybody please give me some guidance to get things back to normal? I've attached the syslog and the SMART report of the failed disk. Thanks so much for any help. BB There is probably nothing wrong with the old disk drive itself, but the file-system on it has some corruption. When you re-built it onto a new drive from parity and the other data disks, it was re-built with exactly the same corruption. To fix is easy. You need to follow the steps in the wiki that describe how to run reiserfsck on your disk. This is the equivalent of checkdsk or scandisk in MS-DOS. The steps are listed here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems When you initially run reiserfsck, it will suggest the correct option to add the second time you run it. (The first time just checks for damage but does not fix anything. When the suggested option is added, it will perform the correction) When you run reiserfsck, it will prompt you to answer "Yes" to continue. Be sure you answer with a capital "Y" and lower case "es". The disk is being currently made read-only because to write to it could cause more corruption. The Linux OS is protecting you from doing damage. Running reiserfsck in the way described in the wiki will keep parity in sync with the fix it makes, so you'll be ok after that. Joe L.
May 18, 201016 yr Author Thanks a ton, Joe. You're definitely the king! I ran reiserfsck, then needed to run --rebuilt-tree per its directions. That took pretty much all day, but now after a restart, things seem OK in terms of being able to read/write. I now have another issue -- not sure if it's related, or what. File transfers between 2 Unraid boxes (this one and another one that has no problems) usually go at about 25-30MB/s consistently for me. I'm now running one, and it seems to cycle faster/slower between about 25MB/s / 5Mb/s. Cycles last maybe 15-20 sec between running fast vs running slower. I get the following red/orange error messages in my log (attached). May 18 14:59:40 BBMedia kernel: ata8: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata8: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata8: hard resetting link May 18 14:59:40 BBMedia kernel: ata5.00: configured for UDMA/133 May 18 14:59:40 BBMedia kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata5: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata5: hard resetting link May 18 14:59:40 BBMedia kernel: ata3.00: configured for UDMA/133 May 18 14:59:40 BBMedia kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata3: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata3: hard resetting link May 18 14:59:40 BBMedia kernel: ata6.00: configured for UDMA/133 May 18 14:59:40 BBMedia kernel: ata6: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata6: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata6: hard resetting link May 18 14:59:40 BBMedia kernel: ata4.00: configured for UDMA/133 May 18 14:59:40 BBMedia kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata4: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata4: hard resetting link Is there something wrong with my controller, or how I have my bios set up? I don't think that anything has changed, but maybe with all of the rebooting, a bios setting got messed up. Any ideas? syslog-2010-05-18-1.txt
May 18, 201016 yr Thanks a ton, Joe. You're definitely the king! I ran reiserfsck, then needed to run --rebuilt-tree per its directions. That took pretty much all day, but now after a restart, things seem OK in terms of being able to read/write. I now have another issue -- not sure if it's related, or what. File transfers between 2 Unraid boxes (this one and another one that has no problems) usually go at about 25-30MB/s consistently for me. I'm now running one, and it seems to cycle faster/slower between about 25MB/s / 5Mb/s. Cycles last maybe 15-20 sec between running fast vs running slower. I get the following red/orange error messages in my log (attached). May 18 14:59:40 BBMedia kernel: ata8: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata8: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata8: hard resetting link May 18 14:59:40 BBMedia kernel: ata5.00: configured for UDMA/133 May 18 14:59:40 BBMedia kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata5: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata5: hard resetting link May 18 14:59:40 BBMedia kernel: ata3.00: configured for UDMA/133 May 18 14:59:40 BBMedia kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata3: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata3: hard resetting link May 18 14:59:40 BBMedia kernel: ata6.00: configured for UDMA/133 May 18 14:59:40 BBMedia kernel: ata6: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata6: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata6: hard resetting link May 18 14:59:40 BBMedia kernel: ata4.00: configured for UDMA/133 May 18 14:59:40 BBMedia kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xf t4 May 18 14:59:40 BBMedia kernel: ata4: irq_stat 0x00400040, connection status changed May 18 14:59:40 BBMedia kernel: ata4: hard resetting link Is there something wrong with my controller, or how I have my bios set up? I don't think that anything has changed, but maybe with all of the rebooting, a bios setting got messed up. Any ideas? Upgrade to 4.5.4, the inconsistent network throughput is fixed with the newer Linux kernel, and performance improve for most people by 20 to 30%. The errors in the syslog only seem to exist as the server is being booted and equipment initialized. I would not worry about them too much. Do you get errors are you copy files to the server?
May 18, 201016 yr Author Thanks, Joe. I'll upgrade, as you suggest. So far, everything is running well - no further errors. Best regards BB
Archived
This topic is now archived and is closed to further replies.