Fork

Thank you, this fixed my problem

I didn't change isp My unraid. server is actually directly connected to my htpc, theres no router. Does this not work?

Hi, I recently moved and my unraid server was ignored for a long time. now i made a new HTPC and connected it to my unraid server however, I cannot access it through the web. I ran ifconfig on the actual unraid tower and I do not see an ip under eth0 can anybody help me get my unraid server back up i attached a photo of my unraid screen and my syslog: http://www.imagebam.com/image/a0ae14306851085 thank you so much in advance, im desperate EDIT': i bought 2 unraid usbs a few years ago, so I tried my second usb key. this has the same problem, no ip detected in eth0 syslog-20140209-142224.txt

The Fork's EVGA 141-BL-E757-TR has an onboard JMB362 controller. oh, i guess that explains why it doesn't post, thanks!

My EVGA 141-BL-E757-TR LGA 1366 doesn't post with this either

thanks for the input guys

I just precleared a samsung f3 hdd with the supermicro AOC-SASLP-MV8 card. however, i was not able to get a smart report and im seeing a lot of errors in the syslog. i enabled smart with the -s on command, but do i need to be concerned with these drive status errors? thanks Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower preclear_disk-finish[1681]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Nov 23 11:55:53 Tower preclear_disk-finish[1681]: Home page is http://smartmontools.sourceforge.net/ Nov 23 11:55:53 Tower preclear_disk-finish[1681]: Nov 23 11:55:53 Tower preclear_disk-finish[1681]: Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) Nov 23 11:55:53 Tower preclear_disk-finish[1681]: Nov 23 11:55:53 Tower preclear_disk-finish[1681]: A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Nov 23 11:55:53 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 11:55:53 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 11:55:53 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 11:55:53 Tower preclear_disk-diff[1694]: ============================================================================ Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Disk /dev/sdb has been successfully precleared Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Ran 1 preclear-disk cycle Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Using :Read block size = 8225280 Bytes Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Last Cycle's Pre Read Time : 2:41:14 (103 MB/s) Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Last Cycle's Zeroing time : 2:29:59 (111 MB/s) Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Last Cycle's Post Read Time : 5:36:16 (49 MB/s) Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Last Cycle's Total Time : 10:48:33 Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Total Elapsed Time 10:48:33 Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Nov 23 11:55:53 Tower preclear_disk-diff[1694]: == Nov 23 11:55:53 Tower preclear_disk-diff[1694]: ============================================================================ Nov 23 11:55:53 Tower preclear_disk-diff[1694]: S.M.A.R.T. error count differences detected after pre-clear Nov 23 11:55:53 Tower preclear_disk-diff[1694]: note, some 'raw' values may change, but not be an indication of a problem Nov 23 11:55:53 Tower preclear_disk-diff[1694]: 4,11c4 Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < === START OF INFORMATION SECTION === Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < Device Model: SAMSUNG HD103SJ Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < Serial Number: S246J9EZ919460 Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < Firmware Version: 1AJ10001 Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < User Capacity: 1,000,204,886,016 bytes Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < Device is: In smartctl database [for details use: -P show] Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < ATA Version is: 8 Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < ATA Standard is: Not recognized. Minor revision code: 0x28 Nov 23 11:55:53 Tower preclear_disk-diff[1694]: --- Nov 23 11:55:53 Tower preclear_disk-diff[1694]: > Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) Nov 23 11:55:53 Tower preclear_disk-diff[1694]: 13,18c6 Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < SMART support is: Available - device has SMART capability. Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < SMART support is: Disabled Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < Nov 23 11:55:53 Tower preclear_disk-diff[1694]: < SMART Disabled. Use option -s with argument 'on' to enable it. Nov 23 11:55:53 Tower preclear_disk-diff[1694]: --- Nov 23 11:55:53 Tower preclear_disk-diff[1694]: > A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Nov 23 11:55:53 Tower preclear_disk-diff[1694]: ============================================================================ Nov 23 11:55:53 Tower preclear_disk-diff[1694]: Nov 23 13:03:03 Tower dhcpcd[1483]: sending DHCP_REQUEST for 192.168.1.15 to 192.168.1.1 Nov 23 13:03:03 Tower dhcpcd[1483]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Nov 23 13:03:03 Tower dhcpcd[1483]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Nov 23 13:03:03 Tower dhcpcd[1483]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Nov 23 13:03:03 Tower dhcpcd[1483]: DHCP_ACK received from (192.168.1.1) Nov 23 16:23:29 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 16:23:29 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 16:23:29 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 16:23:29 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 16:23:29 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 16:23:29 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 16:23:29 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 16:23:29 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 16:23:29 Tower kernel: ata1: error=0x04 { DriveStatusError } Nov 23 16:23:29 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 23 16:23:29 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } Nov 23 16:23:29 Tower kernel: ata1: error=0x04 { DriveStatusError }

Hi, i've been using unraid for awhile now and im very happy with it. today, however, the web-interface stopped responding after i stopped the array. I tried to access my server via telnet but it wasn't responding either. I then tried to connect my keyboard my monitor to it, but my usb keyboard wouldnt connect to it. Since i couldnt obtain a syslog or do anything, I decided to shut it down manually by holding down the power button. After restarting the server, i expected a parity check automatically, but my unraid array went online no problem, without doing a parity check. I am sooo confused by this cause I thought that whenever unraid gets shut down like that, it performs a parity check automatically. I am doing a parity check anyhow, but does anybody know why it didn't start a parity check automatically? i'm using ver 4.5.4

ok, thank you

My motherboard (ASUS M4A79XTD EVO) has 2 PCIe x16 slots. After adding a second Supermicro AOC-SASLP-MV8 card, my syslog is displaying these following errors: Sep 15 00:19:23 Tower kernel: [780]: scst: __scst_register_target_template:253:***ERROR***: Target driver mvst_scst already registered Sep 15 00:19:23 Tower kernel: [780]: scst: __scst_register_target_template:293:***ERROR***: Failed to register target template mvst_scst Does anybody know what is causing this and how to fix it? I also attached a full syslog. thank you syslog.txt

Hi, I have a WD 750gb drive that I used to use as a cache drive on my unraid server. I want to use this drive as storage for my PC instead. However, when I attach this drive to my PC, it doesn't even show up in the bios. But when I plug this drive back into my unraid server, it works just fine. To test if it was the sata port/cable, I tried another drive on my PC with the same sata port/cable, and it was fine. So does anybody know what could be causing this? Thanks

Hi, my unraid server is connected to a UPS but my pc is not. In an event of a power outage, my pc is not protected so I will lose my telnet session which tracks my preclear progress. Is it possible to somehow restore the old session to get my preclear progress back? Thank you

you would think that they would give you some sort of deal for buying a 20 pack...

for the same price, you could get M4A79XTD EVO instead http://www.newegg.com/Product/Product.aspx?Item=N82E16813131402 with 7 onboard sata and more pci express slots i dont think it's a big deal if a motherboard doesnt have onboard video. just get the cheapest PCI video card you can find, shouldnt be more than 30 dollars

im guessing that some people probably perfer a tower setup as opposed to rackmount

im the biggest unraid noob but luckily this setup has been pretty good so far CASE: COOLER MASTER Centurion 590 + 2x Icy Dock 4-in-3 SATA cages CPU: AMD Athlon II X2 250 Regor 3.0GHz Mobo: ASUS M4A79XTD EVO, with 7 onboard sata RAM: G.SKILL Ripjaws 2x2gb DDR3 HDD: 4xHitachi 7200rpm 2Tb + 1xSamsung F3 7200rpm 1Tb PSU: SeaSonic X650 Cooling: ARCTIC COOLING Freezer 64 Pro for CPU It stores all my 1080p movies and tv shows

I suggest Seasonic 650W GOLD http://www.newegg.com/Product/Product.aspx?Item=N82E16817151088 if you want some more power, you can get the 750W http://www.newegg.com/Product/Product.aspx?Item=N82E16817151087&cm_re=seasonic_gold-_-17-151-087-_-Product

i recently pre-cleared a new samsung drive and got the final smart report Jul 8 12:45:21 Tower preclear_disk-diff[881]: ============================================================================ Jul 8 12:45:21 Tower preclear_disk-diff[881]: S.M.A.R.T. error count differences detected after pre-clear Jul 8 12:45:21 Tower preclear_disk-diff[881]: note, some 'raw' values may change, but not be an indication of a problem Jul 8 12:45:21 Tower preclear_disk-diff[881]: 55c55 Jul 8 12:45:21 Tower preclear_disk-diff[881]: < 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 Jul 8 12:45:21 Tower preclear_disk-diff[881]: --- Jul 8 12:45:21 Tower preclear_disk-diff[881]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0 Jul 8 12:45:21 Tower preclear_disk-diff[881]: 67c67 Jul 8 12:45:21 Tower preclear_disk-diff[881]: < 195 Hardware_ECC_Recovered 0x003a 252 252 000 Old_age Always Jul 8 12:45:21 Tower preclear_disk-diff[881]: --- Jul 8 12:45:21 Tower preclear_disk-diff[881]: > 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always Jul 8 12:45:21 Tower preclear_disk-diff[881]: 72c72 Jul 8 12:45:21 Tower preclear_disk-diff[881]: < 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 Jul 8 12:45:21 Tower preclear_disk-diff[881]: --- Jul 8 12:45:21 Tower preclear_disk-diff[881]: > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 1 can someone tell me what these numbers mean and if it indicate any problems for the hdd? thanks

great, thanks guys

is it true that bundling sata cables together will cause interference and data loss? also, is it safe to use caviar black drives for unraid? i heard that they are not meant to be used in raid systems thank you

So far no, though I've only been using this motherboard for less than 24 hours. thanks for your help Joe

thanks guys, i took the courage and updated the bios to the latest version but the acpi errors are still showing...is there anything else i could try to resolve these errors? or would i have to boot with acpi=off from now on?

Thanks, so there isnt a way to automatically shut off the system completely?

Another question, is there a way to cleanly and completely shut off the system when i boot with acpi=off? These acpi problems are really frustrating me and I really dont want to flash the bios if i dont have to. I have never flashed a motherboard before, and since the unraid machine doesnt have a floppy/optic drive, I would probably have to do it via usb and I have no idea how... thanks in advance

yeah...power down isnt working properly. i clicked power down in unmenu and I think unraid shut down, but the fans are still running and the HDD lights are still turned on. I cannot re-access unraid now and i dont really know what to do. should i just hold the power button on the case until it shuts down? if i do that, will unraid perform a parity check on the next boot? thanks after connecting to the monitor, the last 2 lines are mount: can't find /in /etc/fstab or /etc/mtab system halted.