Space_UnRaider

The smart reports for the other drives look very similar, no real errors that i can see. Sounds like the best thing to do here is to run another parity sync. Out of interest, what could have caused unraid to think my parity drive has changed? Some configuration file getting corrupted somehow?

Smart report from parity drive (/dev/sdf) smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 198 194 021 Pre-fail Always - 9066 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 461 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 10174 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 44 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1133 194 Temperature_Celsius 0x0022 119 110 000 Old_age Always - 33 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

How can I get SMART reports without starting the array and mounting the disks?

I have a 10x6TB unraid server running 5.0.5 (1 parity + 9 data) I was writing a file to disk9 and it was failing. I have been having some issues with my local network, so i tried deleting the failed file and unraid told me the file system was read only. I rebooted unraid through the web interface, and now it is telling me that a new parity disk has been installed. On the device status screen, there is a blue ball next to the parity drive. All the other drives are green. Relevant lines from syslog: Dec 31 03:37:29 Tower2 kernel: mdcmd (1): import 0 8,80 5860522532 WDC_WD60EFRX-68MYMN0_WD-WX21D1406561 Dec 31 03:37:29 Tower2 kernel: md: import disk0: [8,80] (sdf) WDC_WD60EFRX-68MYMN0_WD-WX21D1406561 size: 5860522532 Dec 31 03:37:29 Tower2 kernel: md: disk0 replaced I haven't added or removed any drives, so I am unsure what to do next. I don't want to corrupt my existing data. How do I go about resolving this? The full syslog is attached. syslog_tower2.txt

Hi Guys, Some of the media on my server suddenly stopped working. I rebooted the server and I am getting the following messages after the login prompt: Tower2 login: REISERFS error (device md2): zam-7001 reiserfs_find_entry: io error I'm running unraid 5.0.4. I have 9x6TB data drives a 1x6TB parity drive. A bunch of the content on unraid is no longer accessible. I can see the files in explorer, but trying to play them results in errors. I have attached my system log. tower2_error_log.zip

Thanks Gary, that worked.

I'm looking for the best practice to go about reusing an old server. I have old 18 drive array with 2TB drives and I have copied the contents over into my new 24 drive array with 4TB drives. I want to reuse the old server hardware with completely fresh new 6TB drives that I have bought, I'm not interested in any of the old data on the drives as it has already been copied. I don't want parity to be based on my old config in any way. Which files on the unraid flash drive should I delete to get back into a completely neutral state. Is it just the config directory? I'm runing unraid server pro 5.0.4 Thanks.

I powered down, checked all the cabling, powered up again. The server seemed to work ok, apart from the red dot on the latest drive. I replaced this drive and started a rebuild last night. Coming back to it this morning, the web interface is unresponsive - can't seem to connect, and my syslog is huge and full of errors: Apr 23 21:03:56 Tower2 kernel: mvsas 0000:01:00.0: Phy2 : No sig fis Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2024:phy2 Attached Device Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 2 ctrl sts=0x89800. Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 2 irq sts = 0x1001 Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy2 Unplug Notice Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 2 ctrl sts=0x199800. Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 2 irq sts = 0x81 Apr 23 21:03:56 Tower2 kernel: mvsas 0000:01:00.0: Phy3 : No sig fis Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2024:phy3 Attached Device Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 3 ctrl sts=0x89800. Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 3 irq sts = 0x1001001 Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy3 Unplug Notice Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 3 ctrl sts=0x199800. Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 3 irq sts = 0x81 Apr 23 21:03:56 Tower2 kernel: mvsas 0000:01:00.0: Phy7 : No sig fis Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2024:phy7 Attached Device Apr 23 21:03:56 Tower2 kernel: mvsas 0000:01:00.0: Phy5 : No sig fis Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2024:phy5 Attached Device Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 5 ctrl sts=0x89800. Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 5 irq sts = 0x1001 Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy5 Unplug Notice Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 7 ctrl sts=0x199800. Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 7 irq sts = 0x1081 Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2111:phy7 Unplug Notice Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2083:port 5 ctrl sts=0x199800. Apr 23 21:03:56 Tower2 kernel: drivers/scsi/mvsas/mv_sas.c 2085:Port 5 irq sts = 0x81 Full file here: https://www.dropbox.com/s/z7v9pvyi0n7p18d/syslog_today.zip I'm not sure what to do. I don't want to reboot as it is in the middle of data rebuild, but server seems to be unresponsive and just constantly spamming errors to the syslog.

Should I swap back in my old (seemingly failed) drive for this test? I'm not sure how much of the new drive unraid managed to rebuild. There seems to be a bunch of working files on there, but this drive doesn't appear on the stats screen of the unraid menu. I'm not sure what state my parity drive will be in after this partial rebuild, and whether its best to go back to the old drive, stick with the partially built drive or put a new drive into this slot.

Hi guys, I had a drive fail on me this morning (red dot appeared). I moved it out of the array, and started a rebuild with a new drive. When I returned from work this evening, I noticed the new drive now also has a red dot on it too, so am unsure if the rebuild finished correctly. To give some background, I have a 24 bay norco server. I have 17 active disks, a parity drive and some spares. Yesterday I installed a SIL3132 card into the server so I would be able to expand the array. After restarting, I copied a bunch of files to disk 17 (which was about 60% full) and went to bed. When I woke up I saw that not all the files had copied, and the drive had a red dot, and thus started the rebuild with the new drive. I'm not sure the best way to proceed now. Try another disk? Remove the SIL3132? As the attachment facility isn't currently working, I've put my syslog here: https://www.dropbox.com/s/s7cyywn2anzy3a4/systlog.1.zip I'm running Unraid 5.0-beta9. Any help greatly appreciated.

Thanks for the advice. I tried this "Stop the array; and un-assign that drive (disk4). Then Start the array -- it will now show a missing drive. Then Stop the array and assign the drive back to that slot; and finally Start the array again and it will rebuild the drive.", but it doesn't work. I stop the array, unassign the drive, start the array again (drive is now unassigned). I stop the array, assign the drive and start again. It is briefly blue, but it goes red and doesn't attempt to rebuild. The server is 24 bay norco build, and the other drives in the same row as this one are working ok. I tried sliding it out and back in again. It's been a while since I ran a full parity check, but I now this failure must be relatively recent as I installed a new drive about a month ago and didn't have any of these issues. I have attached the system log if that sheds any further light. tower2_log.zip

I am getting a red ball next to disk 4 of my 16 drive array. I have checked the smart reports, but i can't see any obvious errors. I have attached the smart report here. I have not written to that drive for a long time, and I suspect something happened when I just installed a new drive in the array. I thought the obvious thing to do was to follow the http://lime-technology.com/wiki/index.php/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily procedure, but that doesn't seem to work on this version of unraid. Any suggestions? smart_sdn.txt

Update: I've fixed the issue. I removed the memory from the server, ensured it was dust+debris free, and reinstalled it firmly. Unraid now boots again and is working like normal

Thanks. I've got a console up via IPMI, and it looks like unraid is hanging at the "Unpacking initramfs.." section. What could be the cause of this?

Hi Guys, I'm having problems with one of my unraid servers following a house move. The unraid server appears to not be booting. "Tower" no longer appears on the network. I'm running with a supermicro ST-MBD-X8SIL-F-O motherboard in a 20 drive norco box. I can access the supermicro board itself via IMPMI, but unraid itself never appears (I have it's IP address set to 192.168.1.128 via network.cfg, but this never appears on the network and i can't ping it). This had been working perfectly for two years up until I moved house (and my second unraid server box still works great). I not sure how to go about fixing this. I've taken out the USB flashdrive, and it looks like all the contents is still on there. The last syslog was written out on the day of the move, but there have been no logs written out since. Any help will be greatly appreciated.