talmania
-
Posts
205 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by talmania
-
-
Wow...that was it!! replaced the network.cfg and brought back the other two and immediately it came up with correct shares and everything else!! My huge thanks to everyone--I sincerely appreciate the help!
It'd be nice to have my plugins back but the only one that I used was the port 8080 web ui (name escapes me) and the email notification package. I can and probably need to reinstall with the latest versions---off to read about plugins!
Thanks again everyone!
-
To add I didn't get any errors when doing a checkdisk on the usb drive.
-
Ugh..same result with the reformatted key and only copying over the .cfg files with the license key. Is it the USB key then? Can I copy these files to the previous usb key that worked?
-
OK a new usb worked and I was able to access the gui. Now how do I go about replacing it with my original config? I do know which drives were my parity and cache but that's about it.
-
Ok I've checked the startarray and it was set to "no". Changed it to yes and still no difference--I can now see the shares but all of them are "offline". I can ping the gateway and other machines but still no web ui.
I'll try the usb right now--thanks for that tip!
-
Yes I've definitely tried the IP only...I'll look at the startarray piece of the disk.cfg Thanks for that.
-
Thank you itimpi for the response--I sincerely appreciate it!
I'm accessing it via KVM over IP. I can ping the IP address. Interestingly enough I happened to check an infrequently used email this morning and noticed the following unraid notification:
WARNING - unRAID Array NOT STARTED
Server Name: Deed
Server IP: 172.23.1.31
Date: Wed Jun 25 22:47:13 PDT 2014
WARNING - unRAID Array NOT STARTED
Server Name: Deed
Server IP: 172.23.1.31
Date: Wed Jun 25 22:47:13 PDT 2014
Output of /proc/mdcmd:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
sbName=/boot/config/super.dat
sbVersion=2.2.0
sbCreated=1315969296
sbUpdated=1402893513
sbEvents=81
sbState=1
sbNumDisks=20
sbSynced=1401800612
sbSyncErrs=2198
mdVersion=2.2.0
mdState=STOPPED
mdNumProtected=20
mdNumDisabled=0
mdDisabledDisk=0
mdNumInvalid=0
mdInvalidDisk=0
mdNumMissing=0
mdMissingDisk=0
mdNumNew=0
mdResync=0
mdResyncCorr=0
mdResyncPos=0
mdResyncDt=0
mdResyncDb=0
diskNumber.0=0
diskName.0=
diskSize.0=3907018532
diskState.0=7
diskId.0=HGST_HDN724040ALE640_PK2334PBHBZ60R
rdevNumber.0=0
rdevStatus.0=DISK_OK
rdevName.0=sdb
rdevSize.0=3907018532
rdevId.0=HGST_HDN724040ALE640_PK2334PBHBZ60R
rdevNumErrors.0=0
rdevLastIO.0=1403759786
rdevSpinupGroup.0=0
diskNumber.1=1
diskName.1=md1
diskSize.1=1465138552
diskState.1=7
diskId.1=ST31500341AS_9VS09K8D
rdevNumber.1=1
rdevStatus.1=DISK_OK
rdevName.1=sdc
rdevSize.1=1465138552
rdevId.1=ST31500341AS_9VS09K8D
rdevNumErrors.1=0
rdevLastIO.1=1403759786
rdevSpinupGroup.1=0
diskNumber.2=2
diskName.2=md2
diskSize.2=1465138552
diskState.2=7
diskId.2=ST31500341AS_9VS1ELPJ
rdevNumber.2=2
rdevStatus.2=DISK_OK
rdevName.2=sdd
rdevSize.2=1465138552
rdevId.2=ST31500341AS_9VS1ELPJ
rdevNumErrors.2=0
rdevLastIO.2=1403759786
rdevSpinupGroup.2=0
diskNumber.3=3
diskName.3=md3
diskSize.3=1465138552
diskState.3=7
diskId.3=ST31500341AS_9VS1Z549
rdevNumber.3=3
rdevStatus.3=DISK_OK
rdevName.3=sde
rdevSize.3=1465138552
rdevId.3=ST31500341AS_9VS1Z549
rdevNumErrors.3=0
rdevLastIO.3=1403759786
rdevSpinupGroup.3=0
diskNumber.4=4
diskName.4=md4
diskSize.4=1953514552
diskState.4=7
diskId.4=WDC_WD20EARX-00PASB0_WD-WCAZA8379534
rdevNumber.4=4
rdevStatus.4=DISK_OK
rdevName.4=sdr
rdevSize.4=1953514552
rdevId.4=WDC_WD20EARX-00PASB0_WD-WCAZA8379534
rdevNumErrors.4=0
rdevLastIO.4=1403759786
rdevSpinupGroup.4=0
diskNumber.5=5
diskName.5=md5
diskSize.5=1953514552
diskState.5=7
diskId.5=Hitachi_HDS5C3020ALA632_ML0220F30ETWRD
rdevNumber.5=5
rdevStatus.5=DISK_OK
rdevName.5=sdo
rdevSize.5=1953514552
rdevId.5=Hitachi_HDS5C3020ALA632_ML0220F30ETWRD
rdevNumErrors.5=0
rdevLastIO.5=1403759786
rdevSpinupGroup.5=0
diskNumber.6=6
diskName.6=md6
diskSize.6=1953514552
diskState.6=7
diskId.6=Hitachi_HDS5C3020ALA632_ML0220F30LDVHD
rdevNumber.6=6
rdevStatus.6=DISK_OK
rdevName.6=sdp
rdevSize.6=1953514552
rdevId.6=Hitachi_HDS5C3020ALA632_ML0220F30LDVHD
rdevNumErrors.6=0
rdevLastIO.6=1403759786
rdevSpinupGroup.6=0
diskNumber.7=7
diskName.7=md7
diskSize.7=1953514552
diskState.7=7
diskId.7=WDC_WD20EARX-00PASB0_WD-WCAZA7876014
rdevNumber.7=7
rdevStatus.7=DISK_OK
rdevName.7=sds
rdevSize.7=1953514552
rdevId.7=WDC_WD20EARX-00PASB0_WD-WCAZA7876014
rdevNumErrors.7=0
rdevLastIO.7=1403759786
rdevSpinupGroup.7=0
diskNumber.8=8
diskName.8=md8
diskSize.8=1953514552
diskState.8=7
diskId.8=ST32000542AS_5XW2K2X7
rdevNumber.8=8
rdevStatus.8=DISK_OK
rdevName.8=sdq
rdevSize.8=1953514552
rdevId.8=ST32000542AS_5XW2K2X7
rdevNumErrors.8=0
rdevLastIO.8=1403759786
rdevSpinupGroup.8=0
diskNumber.9=9
diskName.9=md9
diskSize.9=1953514552
diskState.9=7
diskId.9=WDC_WD20EARS-00MVWB0_WD-WMAZA1059076
rdevNumber.9=9
rdevStatus.9=DISK_OK
rdevName.9=sdu
rdevSize.9=1953514552
rdevId.9=WDC_WD20EARS-00MVWB0_WD-WMAZA1059076
rdevNumErrors.9=0
rdevLastIO.9=1403759786
rdevSpinupGroup.9=0
diskNumber.10=10
diskName.10=md10
diskSize.10=1953514552
diskState.10=7
diskId.10=WDC_WD20EARS-00MVWB0_WD-WMAZA1010557
rdevNumber.10=10
rdevStatus.10=DISK_OK
rdevName.10=sdv
rdevSize.10=1953514552
rdevId.10=WDC_WD20EARS-00MVWB0_WD-WMAZA1010557
rdevNumErrors.10=0
rdevLastIO.10=1403759786
rdevSpinupGroup.10=0
diskNumber.11=11
diskName.11=md11
diskSize.11=1953514552
diskState.11=7
diskId.11=WDC_WD20EARS-00MVWB0_WD-WMAZA0987578
rdevNumber.11=11
rdevStatus.11=DISK_OK
rdevName.11=sdj
rdevSize.11=1953514552
rdevId.11=WDC_WD20EARS-00MVWB0_WD-WMAZA0987578
rdevNumErrors.11=0
rdevLastIO.11=1403759786
rdevSpinupGroup.11=0
diskNumber.12=12
diskName.12=md12
diskSize.12=1465138552
diskState.12=7
diskId.12=ST31500541AS_6XW0PY4L
rdevNumber.12=12
rdevStatus.12=DISK_OK
rdevName.12=sdg
rdevSize.12=1465138552
rdevId.12=ST31500541AS_6XW0PY4L
rdevNumErrors.12=0
rdevLastIO.12=1403759786
rdevSpinupGroup.12=0
diskNumber.13=13
diskName.13=md13
diskSize.13=1465138552
diskState.13=7
diskId.13=ST31500541AS_6XW0JM2Q
rdevNumber.13=13
rdevStatus.13=DISK_OK
rdevName.13=sdh
rdevSize.13=1465138552
rdevId.13=ST31500541AS_6XW0JM2Q
rdevNumErrors.13=0
rdevLastIO.13=1403759786
rdevSpinupGroup.13=0
diskNumber.14=14
diskName.14=md14
diskSize.14=1953514552
diskState.14=7
diskId.14=WDC_WD20EARX-00PASB0_WD-WCAZAC944241
rdevNumber.14=14
rdevStatus.14=DISK_OK
rdevName.14=sdn
rdevSize.14=1953514552
rdevId.14=WDC_WD20EARX-00PASB0_WD-WCAZAC944241
rdevNumErrors.14=0
rdevLastIO.14=1403759786
rdevSpinupGroup.14=0
diskNumber.15=15
diskName.15=md15
diskSize.15=1953514552
diskState.15=7
diskId.15=WDC_WD20EARS-00MVWB0_WD-WCAZA1239135
rdevNumber.15=15
rdevStatus.15=DISK_OK
rdevName.15=sdk
rdevSize.15=1953514552
rdevId.15=WDC_WD20EARS-00MVWB0_WD-WCAZA1239135
rdevNumErrors.15=0
rdevLastIO.15=1403759786
rdevSpinupGroup.15=0
diskNumber.16=16
diskName.16=md16
diskSize.16=1953514552
diskState.16=7
diskId.16=WDC_WD20EARS-00MVWB0_WD-WCAZA1241990
rdevNumber.16=16
rdevStatus.16=DISK_OK
rdevName.16=sdl
rdevSize.16=1953514552
rdevId.16=WDC_WD20EARS-00MVWB0_WD-WCAZA1241990
rdevNumErrors.16=0
rdevLastIO.16=1403759786
rdevSpinupGroup.16=0
diskNumber.17=17
diskName.17=md17
diskSize.17=1953514552
diskState.17=7
diskId.17=Hitachi_HDS5C3020ALA632_ML0220F30KUV9D
rdevNumber.17=17
rdevStatus.17=DISK_OK
rdevName.17=sdi
rdevSize.17=1953514552
rdevId.17=Hitachi_HDS5C3020ALA632_ML0220F30KUV9D
rdevNumErrors.17=0
rdevLastIO.17=1403759786
rdevSpinupGroup.17=0
diskNumber.18=18
diskName.18=md18
diskSize.18=1953514552
diskState.18=7
diskId.18=Hitachi_HDS5C3020ALA632_ML0221F3057MED
rdevNumber.18=18
rdevStatus.18=DISK_OK
rdevName.18=sdm
rdevSize.18=1953514552
rdevId.18=Hitachi_HDS5C3020ALA632_ML0221F3057MED
rdevNumErrors.18=0
rdevLastIO.18=1403759786
rdevSpinupGroup.18=0
diskNumber.19=19
diskName.19=md19
diskSize.19=1953514552
diskState.19=7
diskId.19=Hitachi_HDS5C3020ALA632_ML0220F30LBM0D
rdevNumber.19=19
rdevStatus.19=DISK_OK
rdevName.19=sdt
rdevSize.19=1953514552
rdevId.19=Hitachi_HDS5C3020ALA632_ML0220F30LBM0D
rdevNumErrors.19=0
rdevLastIO.19=1403759786
rdevSpinupGroup.19=0
diskNumber.20=20
diskName.20=
diskSize.20=0
diskState.20=0
diskId.20=_
rdevNumber.20=20
rdevStatus.20=DISK_NP
rdevName.20=
rdevSize.20=0
rdevId.20=
rdevNumErrors.20=0
rdevLastIO.20=0
rdevSpinupGroup.20=0
diskNumber.21=21
diskName.21=
diskSize.21=0
diskState.21=0
diskId.21=_
rdevNumber.21=21
rdevStatus.21=DISK_NP
rdevName.21=
rdevSize.21=0
rdevId.21=
rdevNumErrors.21=0
rdevLastIO.21=0
rdevSpinupGroup.21=0
diskNumber.22=22
diskName.22=
diskSize.22=0
diskState.22=0
diskId.22=_
rdevNumber.22=22
rdevStatus.22=DISK_NP
rdevName.22=
rdevSize.22=0
rdevId.22=
rdevNumErrors.22=0
rdevLastIO.22=0
rdevSpinupGroup.22=0
diskNumber.23=23
diskName.23=
diskSize.23=0
diskState.23=0
diskId.23=_
rdevNumber.23=23
rdevStatus.23=DISK_NP
rdevName.23=
rdevSize.23=0
rdevId.23=
rdevNumErrors.23=0
rdevLastIO.23=0
rdevSpinupGroup.23=0
-
So in an attempt to take the next step and possibly solve this for myself I looked at my go script and it looks like this:
#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp #
/boot/unmenu/uu
cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c
cp --preserve=timestamps /boot/custom/etc/ssh/ssh*key* /etc/ssh
chmod 600 /etc/ssh/ssh*key*
/etc/rc.d/rc.sshd start
# install crashplan
#tar -C / -xvf /boot/packages/crashplan.tar
#/usr/local/crashplan/bin/CrashPlanEngine start
I noticed the last thing it's reporting on in the syslog is the emhttp is the unmenu or something else after potentially causing it to hang? should I try commenting those out?
-
Hey all--
I just moved and my unraid server will boot up without problems but it will not start unraid or the unraid menu. I've reseated all the drives and ensured the array was offline before powering down previously.
I've followed the instructions to post my syslog here--can someone please help? Thanks!
jason
-
Good grief...I would like to apologize for wasting this board space and consuming internet bandwidth. I completely and absolutely blew it---this is a classic case of why stepping away for a few hours and then coming back to look at something with a fresh pair of eyes can make all the difference.
In my haste, I had commented out too many lines in my go script and the most critical one was removed. I swear I should be forced to surrender my computer. Many thanks to anyone that took even a second of their time to review my boneheadedness.
-
Hey all--
Hoping there's some brilliant minds out there that can help with this one. I was alerted via email that my disk6 was disabled and needed to be replaced. OK--I check web console, confirmed what it reported and followed SOP and took array offline, shutdown and replaced. Once back online it noticed the replaced disk and started the rebuild. After an all night rebuild it came back and said it was complete but there was 4200 some-odd parity errors and parity ok. I also noticed that it was stating that disk6 and disk18 were unformatted and it gave me the checkbox to rebuild. At this point the array was online and I confirmed my documents and shares were there and there was no share present for disk6 or disk18. I panicked a bit thinking 2 bad disks at once but seeing my shares and all my documents there put me at ease.
I let unraid proceed with the format which it did successfully and I confirmed that I could now see shares for disk6 and disk18. At this point I wanted to stop, reboot and restart the array just to confirm. I tried to stop the array but one of the disks never unmounted (other than disk6 or 18). Had to poweroff and upon reboot I can no longer access webgui or see shares.
I've attached my syslog--thanks in advance for the help!
-
I'm sitting here working a night shift and thought I'd weigh in with my opinion.
I've owned/currently own the following:
AppleTV 2 (need to try XBMC with it)
WDTV Live (several versions)
XBMC on net top-like PC build
Popcorn Hour A100, A200 and C200
Dune HD Smart D1
Quick summary: By far my best experience has been with the Dune HD D1
The Long Version:
I started out down this road years ago with a WDTV media player and after running into the limitations of that system decided to build. I checked out XBMC and ended up building a nice mini-itx intel based PC with BD drive etc. After finding out the numerous workarounds to get xyz codec to work or BD ISO to mount I gave up on a homebrew device.
I then started looking at appliances again. In my wait for the Dune and the positive press it was getting I bought a PCH-A200 and a special case to mod it to be silent. I was getting closer to my own entertainment nirvana---having something that could handle whatever I threw at it and "just work". The PCH was pretty close with a few bugs here and there but an ugly interface and I hated the 3rd party apps available at the time. I wanted the beauty of XBMC without the headaches and I wanted something that would play everything regardless of where I got it or what format it was in.
I finally found a perfect combo in the Dune and running the jukebox app Zappiti. It plays absolutely EVERYTHING I throw at it and then some. I don't have to worry about whether or not it will accept some weird format mkv or can it handle BD-ISO menus, subs etc. or having to configure XBMC to use some external program to mount my ISO etc. I wanted a device that my 5 year old daughter could use and my wife wouldn't kill me for installing.
The interface for Zappiti is absolutely everything I could want in a frontend. Simple, elegant, functional and beautiful. I would HIGHLY recommend anyone that is considering a media player solution to ask themselves what their goal is and how much involvement they want with their product. I work in IT for a living, love tinkering and have my own server rack and multiple pc's but when it came to my entertainment I just want it to work and the Dune delivers that absolutely perfectly. I have yet to come across something it can't play (I use mine strictly for video--never music). I've ripped all my kids favorite DVD's and BD's to ISO's and they work perfectly---much faster than my old Panasonic and Sony BD players. I've recently pulled my BD players out of my entertainment rack and will be buying another D1 for my bedroom/bonus room when funds permit.
Just one guys journey through finding digital media entertainment bliss.
-
Thanks so much mbryanr--please check your PM's when you get a chance.
My user shares are already present and while I haven't looked through everything (20 something terabytes!!) I have looked in several locations and things appear completely normal.
I don't have MBR 4k-aligned enabled. I'm using jumpers on all my EARS.
Brings up a good question about moving to the next version of Unraid--do I need to make a change to 4k aligned? Can that switch be made to an existing array?
-
Parity sync complete and Unraid reports parity is valid! What a relief!
Looking over the syslog it looks like mover initialized and some directories were recreated that must have been on 18. I've trimmed that part out in order to get the syslog down below 192k (along with a bit of the beginning). Regardless from a quick glance it looks like things are back to normal!!
-
After looking it over I'm almost certain there was no data on drive 18 yet (thankfully) just reassigned the parity drive and it's doing a parity sync now.
-
OMG...I swear the fear of losing data makes me completely incompetent. I now see that disk 18 is reporting as unformatted--I'm positive it wasn't that way before. Not sure what's going on but investigating....
-
Woohoo!! I think I'm almost there!
The disk 5 took a bit longer than the others to mount and you can see the reads/writes. Not sure what to make of that....
The data shares are now present and the only issue I'm seeing that I don't think I should see is an unformatted drive message below. I'm not moving forward with assigning the parity---I'm concerned I shouldn't be seeing that option:
-
You're an expert compared to me!!
Regardless I really appreciate the help. I've lost at least 6 months off my life worrying about my data.
Here's the output of the smart report:
smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD20EADS-00S2B0 Serial Number: WD-WCAVY5770676 Firmware Version: 01.00A01 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Sep 13 17:56:56 2011 PDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x85) Offline data collection activity was aborted by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (41700) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. 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 147 145 021 Pre-fail Always - 9633 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1843 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 091 091 000 Old_age Always - 7269 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 - 22 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 6 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35731 194 Temperature_Celsius 0x0022 123 107 000 Old_age Always - 29 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 Warning: ATA error count 6427 inconsistent with error log pointer 1 ATA Error Count: 6427 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 6427 occurred at disk power-on lifetime: 6546 hours (272 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 00 00 00 00 00 08 48d+21:57:33.705 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE Error 6426 occurred at disk power-on lifetime: 6546 hours (272 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE Error 6425 occurred at disk power-on lifetime: 6546 hours (272 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e5 00 00 00 00 00 00 08 48d+21:57:33.703 CHECK POWER MODE Error 6424 occurred at disk power-on lifetime: 6546 hours (272 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e0 00 00 00 00 00 00 08 48d+21:57:33.704 STANDBY IMMEDIATE e5 00 00 00 00 00 00 08 48d+21:57:33.703 CHECK POWER MODE e0 00 00 00 00 00 00 08 48d+21:57:19.071 STANDBY IMMEDIATE SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 7269 - # 2 Short offline Completed without error 00% 7218 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
I know enough to look at reallocated sectors and pending writes and it looks like they are zero. This is the original disk 5 that was reported DISK_DSBL
-
Thanks again for the help--I truly appreciate it.
My concern is that I'm almost positive of what my parity drive is but Unraid isn't (at least from the message given). In summary:
Logged into unraid menu one night with array running as expected and noticed disk 5 in Disk_DSBL state. Stopped array and replaced disk but when trying to bring the array back online Unraid stated it detected a new parity drive.
By proceeding in the steps below am essentially chancing it that my data is there? If drive 5 is truly bad and my array has no idea what my parity drive is aren't I screwed?
Should I attempt to bring the original disk 5 (the one that started this whole mess) back into the array in the steps listed below or leave it out and proceed as listed, adding in parity at the very end?
I will absolutely keep prinouts and notes going forward. I'm embarrased I haven't and I should know better.
Thanks!
-
I'm still confused. My guess is that the /sdX assignments are done by Linux and the drive assignments are done by Unraid right?
If so, I don't have all the pieces since I don't know what the disk device assignments looked like before (see the above Unraid screen shot).
Am I screwed?
Joe do you check your PM's?
Thanks anyone in advance for any help--I sincerely appreciate it.
-
Maybe were onto something here...
From the old syslog:
Mar 22 07:52:15 Deed emhttp: Device inventory: Mar 22 07:52:15 Deed emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host3 (sdr) WDC_WD20EARS-00MVWB0_WD-WCAZA0399136 Mar 22 07:52:15 Deed emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 host4 (sds) ST31500341AS_9VS09K8D Mar 22 07:52:15 Deed emhttp: pci-0000:00:1f.2-scsi-2:0:0:0 host5 (sdt) ST31500341AS_9VS1ELPJ Mar 22 07:52:15 Deed emhttp: pci-0000:00:1f.2-scsi-3:0:0:0 host6 (sdu) ST31500341AS_9VS1Z549 Mar 22 07:52:15 Deed emhttp: pci-0000:00:1f.2-scsi-4:0:0:0 host7 (sdv) WDC_WD3000GLFS-01F8U0_WD-WXL508054114 Mar 22 07:52:15 Deed emhttp: pci-0000:01:00.0-sas-phy0:1-0x0000000000000000:0-lun0 host0 (sdb) ST31500541AS_6XW0PY4L Mar 22 07:52:15 Deed emhttp: pci-0000:01:00.0-sas-phy1:1-0x0100000000000000:1-lun0 host0 (sdc) ST31500541AS_6XW0JM2Q Mar 22 07:52:15 Deed emhttp: pci-0000:01:00.0-sas-phy2:1-0x0200000000000000:2-lun0 host0 (sdd) Hitachi_HDS5C30_ML0220F30KUV9D Mar 22 07:52:15 Deed emhttp: pci-0000:01:00.0-sas-phy3:1-0x0300000000000000:3-lun0 host0 (sde) WDC_WD20EARS-00_WD-WMAZA0987578 Mar 22 07:52:15 Deed emhttp: pci-0000:01:00.0-sas-phy4:1-0x0400000000000000:4-lun0 host0 (sdf) WDC_WD20EARS-00_WD-WCAZA1239135 Mar 22 07:52:15 Deed emhttp: pci-0000:01:00.0-sas-phy5:1-0x0500000000000000:5-lun0 host0 (sdg) WDC_WD20EARS-00_WD-WCAZA1241990 Mar 22 07:52:15 Deed emhttp: pci-0000:01:00.0-sas-phy6:1-0x0600000000000000:6-lun0 host0 (sdh) WDC_WD20EARS-00_WD-WCAZA1263685 Mar 22 07:52:15 Deed emhttp: pci-0000:01:00.0-sas-phy7:1-0x0700000000000000:7-lun0 host0 (sdi) ST32000542AS_5XW1NRNQ Mar 22 07:52:15 Deed emhttp: pci-0000:02:00.0-sas-phy0:1-0x0000000000000000:0-lun0 host2 (sdj) WDC_WD20EADS-00S2B0_WD-WCAVY5770676 Mar 22 07:52:15 Deed emhttp: pci-0000:02:00.0-sas-phy1:1-0x0100000000000000:1-lun0 host2 (sdk) WDC_WD20EADS-00_WD-WCAVY5771098 Mar 22 07:52:15 Deed emhttp: pci-0000:02:00.0-sas-phy2:1-0x0200000000000000:2-lun0 host2 (sdl) ST32000542AS_5XW2K2X7 Mar 22 07:52:15 Deed emhttp: pci-0000:02:00.0-sas-phy3:1-0x0300000000000000:3-lun0 host2 (sdm) ST31500341AS_9VS01DQK Mar 22 07:52:15 Deed emhttp: pci-0000:02:00.0-sas-phy4:1-0x0400000000000000:4-lun0 host2 (sdn) WDC_WD20EARS-00_WD-WCAZA2829716 Mar 22 07:52:15 Deed emhttp: pci-0000:02:00.0-sas-phy5:1-0x0500000000000000:5-lun0 host2 (sdo) Hitachi_HDS5C30_ML0220F30LBM0D Mar 22 07:52:15 Deed emhttp: pci-0000:02:00.0-sas-phy6:1-0x0600000000000000:6-lun0 host2 (sdp) WDC_WD20EARS-00_WD-WMAZA1059076 Mar 22 07:52:15 Deed emhttp: pci-0000:02:00.0-sas-phy7:1-0x0700000000000000:7-lun0 host2 (sdq) WDC_WD20EARS-00_WD-WMAZA1010557
And the latest....now to compare. If they are off should I modify to correct or
?Sep 10 20:08:27 Deed emhttp: Device inventory: Sep 10 20:08:27 Deed emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host3 (sdr) WDC_WD20EARS-00MVWB0_WD-WCAZA0399136 Sep 10 20:08:27 Deed emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 host4 (sds) ST31500341AS_9VS09K8D Sep 10 20:08:27 Deed emhttp: pci-0000:00:1f.2-scsi-2:0:0:0 host5 (sdt) ST31500341AS_9VS1ELPJ Sep 10 20:08:27 Deed emhttp: pci-0000:00:1f.2-scsi-3:0:0:0 host6 (sdu) ST31500341AS_9VS1Z549 Sep 10 20:08:27 Deed emhttp: pci-0000:00:1f.2-scsi-4:0:0:0 host7 (sdv) WDC_WD3000GLFS-01F8U0_WD-WXL508054114 Sep 10 20:08:27 Deed emhttp: pci-0000:01:00.0-sas-phy0:1-0x0000000000000000:0-lun0 host0 (sdb) ST31500541AS_6XW0PY4L Sep 10 20:08:27 Deed emhttp: pci-0000:01:00.0-sas-phy1:1-0x0100000000000000:1-lun0 host0 (sdc) ST31500541AS_6XW0JM2Q Sep 10 20:08:27 Deed emhttp: pci-0000:01:00.0-sas-phy2:1-0x0200000000000000:2-lun0 host0 (sdd) Hitachi_HDS5C30_ML0220F30KUV9D Sep 10 20:08:27 Deed emhttp: pci-0000:01:00.0-sas-phy3:1-0x0300000000000000:3-lun0 host0 (sde) WDC_WD20EARS-00_WD-WMAZA0987578 Sep 10 20:08:27 Deed emhttp: pci-0000:01:00.0-sas-phy4:1-0x0400000000000000:4-lun0 host0 (sdf) WDC_WD20EARS-00_WD-WCAZA1239135 Sep 10 20:08:27 Deed emhttp: pci-0000:01:00.0-sas-phy5:1-0x0500000000000000:5-lun0 host0 (sdg) WDC_WD20EARS-00_WD-WCAZA1241990 Sep 10 20:08:27 Deed emhttp: pci-0000:01:00.0-sas-phy6:1-0x0600000000000000:6-lun0 host0 (sdh) WDC_WD20EARS-00_WD-WCAZA1263685 Sep 10 20:08:27 Deed emhttp: pci-0000:01:00.0-sas-phy7:1-0x0700000000000000:7-lun0 host0 (sdi) ST32000542AS_5XW1NRNQ Sep 10 20:08:27 Deed emhttp: pci-0000:02:00.0-sas-phy0:1-0x0000000000000000:0-lun0 host2 (sdj) WDC_WD20EARS-00MVWB0_WD-WCAZA8408520 Sep 10 20:08:27 Deed emhttp: pci-0000:02:00.0-sas-phy1:1-0x0100000000000000:1-lun0 host2 (sdk) WDC_WD20EADS-00_WD-WCAVY5771098 Sep 10 20:08:27 Deed emhttp: pci-0000:02:00.0-sas-phy2:1-0x0200000000000000:2-lun0 host2 (sdl) ST32000542AS_5XW2K2X7 Sep 10 20:08:27 Deed emhttp: pci-0000:02:00.0-sas-phy3:1-0x0300000000000000:3-lun0 host2 (sdm) ST31500341AS_9VS01DQK Sep 10 20:08:27 Deed emhttp: pci-0000:02:00.0-sas-phy4:1-0x0400000000000000:4-lun0 host2 (sdn) WDC_WD20EARS-00_WD-WCAZA2829716 Sep 10 20:08:27 Deed emhttp: pci-0000:02:00.0-sas-phy5:1-0x0500000000000000:5-lun0 host2 (sdo) Hitachi_HDS5C30_ML0220F30LBM0D Sep 10 20:08:27 Deed emhttp: pci-0000:02:00.0-sas-phy6:1-0x0600000000000000:6-lun0 host2 (sdp) WDC_WD20EARS-00_WD-WMAZA1059076 Sep 10 20:08:27 Deed emhttp: pci-0000:02:00.0-sas-phy7:1-0x0700000000000000:7-lun0 host2 (sdq) WDC_WD20EARS-00_WD-WMAZA1010557 Sep 10 20:08:27 Deed emhttp: get_fstype: open /dev/sdj1: No such file or directory Sep 10 20:08:27 Deed emhttp: get_fstype: open /dev/sdh1: No such file or directory
-
Thanks for the reply---by original config do you mean original as in first ever config? I've grown from 3-4 disks to now almost 20. Or do you mean the config right before removing the disabled disk?
I'm not sure it matters since I don't have any disk config other than the previous syslog linked above.
-
Have WD to cross-ship your drive. Guarenteed to get a different one that way.
This...avoid the retailer all together. And then don't give them anymore of your business!
-
A couple of screen shots...
after more research tonight I found a couple of posts referencing that I should be able to start up the array with one drive missing so I unassigned it, rebooted and still can't start the array. Here's what I see...
?
Looking for new media players
in Lounge
Posted
Great read!! It's interesting to see how far htpc's have come. I settled on the Dune players back a long time ago because as others have said I wanted it to work and didn't want to fuss. I have rarely used bluray iso but having that capability is important--there's nothing more annoying to me than being limited by a technology.
Interesting stuff about the Roku3 and plex--I have a roku3 connected to every TV for Netflix/amazon/hulu. I'll have to try plex and see how it does!