Orbi

Members
  • Posts

    179
  • Joined

  • Last visited

Everything posted by Orbi

  1. A much anticipated moment! A big congratulations to Tom(s), Eric and all those involved!
  2. I've been following the various virtualization threads since christmas with interest. My use of UnRaid is fairly classic, I use it as a storage server for my media content and it is running the holy trilogy of SAB, SB and CP through the current system of plugins. While I understand the need for a package manager for those with many plugins running, my situation is pretty straightforward and easily managable manually (though I've had conflicting versions of python and openssl for the three plugins above). I'm not the primary target group for virtualizing my server, but I am very interested in one aspect and application of this technology, namely running XBMC. My server and my win7 client (running xbmc) sits 4m next to my TV. Ideally, I would be able to switch of my win7 client and have only the server on for watching movies and tv shows. When I bought my server hardware in 2009, I had no virtualization in mind. I bought it because it was compatible with unRaid, based on recommendations on the forum. I have a Phenom X2 on a 780G motherboard, not IOMMU capable. What does this mean for me? If I would be running openelec in a VM, would it be able to call onto the onboar GPU to assist in movie rendering or not? I have a RF remote I currently use and is supported by Openelec. Would I be able to use that as well?
  3. You could try to increase the voltage to your ram modules. That sometimes helps, though most of times replacing the defective module is the only solution.
  4. Don't put too much trust into BIOS detection of your hard drives. I have a malfunctioning sata port on the motherboard which gets detected by both BIOS and Unraid. Good you were able to isolate the origin of the issue.
  5. The intel ICH7 southbridge does not support AHCI. http://support.asus.com/FAQ/Detail.aspx?SLanguage=en&no=B9C0B59B-4041-0B1F-3C36-A150246D0529&p=1&m=P5LD2-VM Try different configurations, let us know how it goes.
  6. It could be the cable, or the sata channel or both. Maybe it's because of the bios settings. Be sure all the 'smart' stuff is disabled like RAID and JBOD. It's also better to have AHCI enabled.
  7. Guys, his father passed away. Is it too much to show respect, stop the nagging and give him the time he needs? He'll come around and resume work.
  8. Update: chaging the data cable had no effect, the drive kept red balling. So I used another sata port on my motherboard and the drive is still green since August 19th. Seems like I have a difficult or defect sata port.
  9. But great work has been made by user ikosa: http://lime-technology.com/forum/index.php?topic=28873.0
  10. The drive is still green, touching wood. I'll make a reiserfs check tonight just to be sure.
  11. The drive is at location md1, so no similarities here. After the reboot, the reiserfs errors were gone, but the drive redballed. It's odd.
  12. I was looking into RMA'ing the drive, but prior to that Seagate requests to run their analysis tool, Seatools. I made a full sector scan, and it found naught. After the scan, I noticed that the Runtime Bad Block value increased from 1 to 3. It was 1 before I posted this thread. To be sure I replaced the sata cable as well. Well it's been two days now since I rebuilt the array, I will see how the drive behaves. It's the second time this hard drive is red balling. Previous time it took one month for the Runtime Bad Block value to increase from 0 to 1, resulting in a write failure. Seagate's RMA policy allows to return the hard drive when Runtime Bad Block value reaches 200.
  13. Update: Oddly, reiserfsck found no corruption. It looks like my drive is good to go. I performed a SMART test as well and that didn't show anything unusual. So before reboot reiserfsck found 317 corruptions, after reboot none. I don't understand what's happening here. Is there anything else worth checking before rebuilding the drive?
  14. Thanks for all the replies. I decided to reboot the server before running reiserfsck --rebuild-tree /dev/md1. The webgui greeted me with a red ball. Under these conditions the reiserfsck utility doesn not want to even check the disk. Tower login: root Linux 3.4.26-unRAID. root@Tower:~# reiserfsck --check /dev/md1 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/md1 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 Aug 13 17:28:12 2013 ########### Partition /dev/md1 is mounted with write permissions, cannot check it root@Tower:~# In line with the wiki instructions, I wanted to start the array in maintenance mode. Before being able to do that, the array must first be stopped. After I click Stop, the array seems caught in an endless loop of unmounting (syslog attached) resulting in an unresponsive webgui. What to do? syslog.zip
  15. That all makes sense, except that the drive has been put into a read-only state. I can not modify any files or write to the disk via the disk share. I see files on my cache drive which have not been moved because the drive is not writeable. If UnRAID is trying to write to the disk to e.g. correct a read error, it will fail because of the read-only status. I'm wondering why the disk has been put into read-only status. Is it some kind of protection measure from the Reiser filesystem?
  16. Correct me if I'm wrong, but shouldn't the disk be flagged as red seeing the read-only state?
  17. Hi, I noticed my syslog is filled with errors of the like: Aug 12 18:31:32 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 16385 does not match to the expected one 2 Aug 12 18:31:32 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 304065133. Fsck? Aug 12 18:31:37 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 16385 does not match to the expected one 2 Aug 12 18:31:37 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 304065133. Fsck? Aug 12 18:31:37 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 16385 does not match to the expected one 2 Aug 12 18:31:37 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 304065133. Fsck? Aug 12 18:31:40 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 16385 does not match to the expected one 2 Aug 12 18:31:40 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 304065133. Fsck? I checked the wiki and as per the http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems instructions I ran the reiserfsck --check /dev/md1 command. This gave the following output: ... the problem in the internal node occured (575137531), whole subtree is skipped / 13 (of 162\/123 (of 170-block 575349567: The level of the node (9132) is not correct, (1) expected the problem in the internal node occured (575349567), whole subtree is skipped / 36 (of 162|/ 2 (of 170-block 127096823: The number of items (1) is incorrect, should be (0) the problem in the internal node occured (127096823), whole subtree is skipped / 16 (of 23-/119 (of 165-block 304065133: The level of the node (16385) is not correct, (2) expected the problem in the internal node occured (304065133), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 317 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Mon Aug 12 19:13:51 2013 Should I just go ahead and run reiserfsck --rebuild-tree /dev/md1 ? The drive has been put to a read-only state, but has not been red-balled by the system. Some basic info: 11 data drives Motherboard Asus M4A78LT-M AOC-SASLP-MV8 4 GB ram
  18. Poor example. My plugin is 100% compatible with SimpleFeatures. I don't even use openssl. A better example (I hope): Sabnzbd installs openssl-0.9.8r-i486-3 and simplefeatures installs openssl-1.0.1c-i486-3, resulting in SF gui instability while using sabnzbd. After removing openssl 0.9.8 from the sabnzbd.plg and package folder and restarting the server, SF gui remains responsive. http://lime-technology.com/forum/index.php?topic=12698.msg231583#msg231583
  19. I know you mentioned you disabled plugins, but some consider simpefeatures as not a plugin. If you have it enabled and opened in your browser, it will slow data rebuild and parity check. That is because is does hard drive polling in background, slowing down the process altogether. Just close it in your browser.
  20. Update: The power cycle did not yield a smart report. I went ahead and replaced the drive anyway. The old drive makes noise when I shake it gently. Sounds like a loose piece inside. Anyway, the data reconstruct completed successfully. The reason why I bought unRaid 4 years ago happened, survive a failing drive without data loss. The replacement went smoothly. Thanks unRaid!