born2ride Posted April 22, 2014 Share Posted April 22, 2014 I am having trouble on first boot. I am not sure where I went off but i could use ALOT of guidance. This is all very new to me especially not having any computer background, I have been following this http://www.mediasmartserver.net/2011/05/19/guide-unraid-server-part-2-installing-unraid/ and this http://lime-technology.com/unraid-server-installation/Guide Does not recognize the command? http://lookpic.com/O/i2/229/gO2CtEJo.jpeg sata link showing smaller number? how come? http://lookpic.com/O/i2/67/a2VsArAV.jpeg Then I read about putty? Did i miss a step with flash drive? Quote Link to comment
trurl Posted April 23, 2014 Share Posted April 23, 2014 Your images are not working for me. They are 403 - Forbidden Quote Link to comment
born2ride Posted April 23, 2014 Author Share Posted April 23, 2014 I see that for some reason! I am trying to size them to fit as attachment Are we not allowed to post pictures? trying to post pic . i am using lookpic. Quote Link to comment
eroz Posted April 23, 2014 Share Posted April 23, 2014 try imgur or photobucket... Quote Link to comment
born2ride Posted April 26, 2014 Author Share Posted April 26, 2014 Following guides .. http://lime-technology.com/unraid-server-installation/Guide , http://www.mediasmartserver.net/2011/05/19/guide-unraid-server-part-2-installing-unraid/ Here is the place i am stumped on. Here is the one i was asking about : sata link showing smaller number? how come? Any one close to central NJ to bail me out? Quote Link to comment
bkastner Posted April 26, 2014 Share Posted April 26, 2014 Looking at your image it may be a syntax issue. the command is LS -L (in lower case) and each drive will be sda, or sdb, etc. so your command should look like this: ls -l /dev/sda The different SATA links is just connection speed, it shouldn't pose any issues at the moment - it just means one of the drives is on a lower bandwidth channel. Is your issue just in trying to view the drives? What other issues are you having? Quote Link to comment
born2ride Posted April 26, 2014 Author Share Posted April 26, 2014 I was following the guide on media , i guess they are just having me check the drives? "To see all of your device mappings, at the prompt type 1 ls -l /dev/sd[a-z] Note all of your “sdX” mappings (these should be sda & sdb & sdc for just three drives). Later, you will use these /dev/sdX names to reference the disks." I dont know why i Am checking. My problem is just trying to get up and running having hard time i guess understanding what I am doing and why. With preclear, and putty .. Was putty install on flash drive or is it something else? Quote Link to comment
bkastner Posted April 26, 2014 Share Posted April 26, 2014 Yes, so /dev/sda or /dev/sdb, etc is just checking each drive to make sure it's accessible. Putty is not part of the media, it's something you need to download separately. You can then use it to manage UnRAID via the console. If you know what your server IP address is you should be able to just open a web browser on a pc with http://192.168.1.X (or whatever the address is). That will bring up the main GUI and you should see a pulldown that shows the drives as well (to make sure they are all visible). Preclear is a separate script that the install page should link you too (along with screen which you should install). The point of preclearing a drive is it attempts to write to each byte on the disk to make sure it's error free and the whole disk is running fine prior to you adding it to UnRAID. The better, single source of info to use is the following: http://lime-technology.com/wiki/index.php/Configuration_Tutorial I would suggest you ignore the two articles you've been using and just focus on this. It will take you from the USB drive through to UnRAID up and running in clear easy steps. Quote Link to comment
Joe L. Posted April 26, 2014 Share Posted April 26, 2014 also note that the /dev/sdX device names are assigned to the drives every time you reboot in the order in which the drives spin-up and initialize. DO NOT ASSUME THE DEVICE NAMES WILL ALWAYS BE THE SAME. On reboot, they frequently will be different with similar drives (initializing in nearly identical time) Make note not of the device names, but of their model/serial numbers as you make your disk assignments. ( The unRAID software uses the mode/serial numbers of the drives when assigning them to slots in the array on current versions of unRAID and used disk-controller port IDs in older versions of unRAID... until it was discovered on some motherboards the disk-controller-IDs too were assigned differently on reboot. ) Joe L. Quote Link to comment
born2ride Posted April 26, 2014 Author Share Posted April 26, 2014 using the quide provided I am up to : Setting a static IP address...I am looking in router DHCP is set to on. Do i skip the manual setting ip? I have the ip if so i am done in the that sever. just go to the tower main page and continue with Configuration With the Server Management Utility. another question. Install UnMENU for Screen and eMail Notifications ?? WHAT IS THE FOR ,WHAT DOES IT dO FOR ME? It is not required to install UnMENU and Screen or eMail notifications, you may skip all or part(s) of this step if you are in a hurry and do not mind running the preclear_disk.sh from the console of the UnRAID server or leaving a telnet session open for an extended period. Once you installed unMENU it is highly recommended to install the clean powerdown script. Sometimes the GUI will go unresponsive which renders you without a possibility to cleanly powerdown the server! This script will bypass the GUI and facilitate a clean shutdown. Install the powerdown upgrade in the same way as screen is installed. [edit] Install UnMENU UnMENU is an enhanced Web management page for unRAID that provides a number of user-requested features, and is relatively easy to extend. Installing it now gives you access to screen and email notifications, both of which are useful for preclearing hard drives. Note: This step assumes have the unmenu_install script on your flash drive. See the Pre Boot section for details if you do not. Note: For this step your server must have access to the internet to download some files. It is NOT recommended that you connect your UnRAID server directly to the internet as it is not secure. You should connect your unRAID server to a router that in turn is connected to the internet. To be able to download files you must have both a DNS server and a Gateway defined on the unRAID web-management settings page. Typically both will be set to the IP address of your router. Step 1 Log into your UnRAID server as root via a telnet connection or at the console. (( ROOT MEANS THE BLACK SCREENS I BEEN POSTING ABOUT IN PICS?)) Step 2 At the prompt type I got to this page. Now is this where unmenu goes? Quote Link to comment
bkastner Posted April 26, 2014 Share Posted April 26, 2014 using the quide provided I am up to : Setting a static IP address...I am looking in router DHCP is set to on. Do i skip the manual setting ip? I have the ip if so i am done in the that sever. just go to the tower main page and continue with Configuration With the Server Management Utility. You can either manually set a static ip or use DHCP. The benefit of using a static address is that it will always be the same moving forward. Using DHCP the address may change as DHCP only leases an address. If you map this computer from other clients DHCP may cause issues down the road, so static is preferred. This is something you can change later in the GUI though. another question. Install UnMENU for Screen and eMail Notifications ?? WHAT IS THE FOR ,WHAT DOES IT dO FOR ME? UnMENU is a GUI enhancement that sits over the UnRAID GUI. It's reachable on port 8080 (i.e. http://192.168.1.XX:8080) but needs to be installed separately using the instructions in the config guide. It makes adding new packages MUCH easier as you can do it via the GUI rather than the telnet prompt which is advisable, especially for non-Linux types. Screen is a utility you run that allows sessions to continue even if you lose your telnet session. A pre_clear process can take 24-48 hours depending on the drive size and system speed. If you telnet into UnRAID and don't use screen and you lose your connection to UnRAID for some reason you lose the pre_clear process and have to start over. If you have screen running you can re-connect to UnRAID and then re-connect to your screen session and the process you are running will continue to run in the background so you don't have to redo anything. Both are highly recommended options. Step 1 Log into your UnRAID server as root via a telnet connection or at the console. (( ROOT MEANS THE BLACK SCREENS I BEEN POSTING ABOUT IN PICS?)) Yes, this is the command console. Once you install Putty (found by Googling it) you can start Putty, select Telnet as your option and the ip address of your UnRAID server. You can then run console commands (such as pre_clear) from another machine in your house. Using Putty allows you to run UnRAID without a monitor, keyboard or mouse and just manage it from another machine on the network. I got to this page. Now is this where unmenu goes? The screenshot you provide is the standard GUI. As mentioned, UnMENU is reachable using the same HTTP address, but adding :8080 to the end of it. Quote Link to comment
born2ride Posted November 9, 2014 Author Share Posted November 9, 2014 I finally got in to the unmenu , I am having trouble with starting preclear. I tried it through tower then here I need some help . SMART status Info for /dev/sdd smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.9 Device Model: ST3250824AS Serial Number: 9ND0DMZ1 Firmware Version: 3.ADH User Capacity: 250,000,000,000 bytes [250 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA/ATAPI-7 (minor revision not indicated) Local Time is: Sun Nov 9 03:58:13 2014 EST 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: (0x82) Offline data collection activity was completed without error. 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: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 100) minutes. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 109 084 006 Pre-fail Always - 197740771 3 Spin_Up_Time 0x0003 099 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 407 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 087 060 030 Pre-fail Always - 555157513 9 Power_On_Hours 0x0032 048 048 000 Old_age Always - 45917 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 495 187 Reported_Uncorrect 0x0032 090 090 000 Old_age Always - 10 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 056 049 045 Old_age Always - 44 (Min/Max 39/45) 194 Temperature_Celsius 0x0022 044 051 000 Old_age Always - 44 (0 10 0 0 0) 195 Hardware_ECC_Recovered 0x001a 056 050 000 Old_age Always - 104143077 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 10 (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 10 occurred at disk power-on lifetime: 45132 hours (1880 days + 12 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 -- -- -- -- -- -- -- 40 51 01 e3 7a 86 e0 Error: UNC at LBA = 0x00867ae3 = 8813283 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 42 00 01 e3 7a 86 e0 00 00:13:27.314 READ VERIFY SECTOR(S) EXT 25 00 01 00 00 00 e0 00 00:13:27.304 READ DMA EXT 42 00 02 e5 7a 86 e0 00 00:13:27.288 READ VERIFY SECTOR(S) EXT 25 00 01 00 00 00 e0 00 00:13:27.272 READ DMA EXT 42 00 02 e3 7a 86 e0 00 00:13:25.719 READ VERIFY SECTOR(S) EXT Error 9 occurred at disk power-on lifetime: 45132 hours (1880 days + 12 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 -- -- -- -- -- -- -- 40 51 02 e3 7a 86 e0 Error: UNC at LBA = 0x00867ae3 = 8813283 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 42 00 02 e3 7a 86 e0 00 00:13:27.314 READ VERIFY SECTOR(S) EXT 42 00 04 e3 7a 86 e0 00 00:13:27.304 READ VERIFY SECTOR(S) EXT 42 00 04 df 7a 86 e0 00 00:13:27.288 READ VERIFY SECTOR(S) EXT 25 00 01 00 00 00 e0 00 00:13:27.272 READ DMA EXT 42 00 08 e7 7a 86 e0 00 00:13:25.719 READ VERIFY SECTOR(S) EXT Error 8 occurred at disk power-on lifetime: 45132 hours (1880 days + 12 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 -- -- -- -- -- -- -- 40 51 04 e3 7a 86 e0 Error: UNC at LBA = 0x00867ae3 = 8813283 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 42 00 04 e3 7a 86 e0 00 00:13:27.314 READ VERIFY SECTOR(S) EXT 42 00 04 df 7a 86 e0 00 00:13:27.304 READ VERIFY SECTOR(S) EXT 25 00 01 00 00 00 e0 00 00:13:27.288 READ DMA EXT 42 00 08 e7 7a 86 e0 00 00:13:27.272 READ VERIFY SECTOR(S) EXT 42 00 08 df 7a 86 e0 00 00:13:25.719 READ VERIFY SECTOR(S) EXT Error 7 occurred at disk power-on lifetime: 45132 hours (1880 days + 12 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 -- -- -- -- -- -- -- 40 51 04 e3 7a 86 e0 Error: UNC at LBA = 0x00867ae3 = 8813283 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 42 00 08 df 7a 86 e0 00 00:13:20.942 READ VERIFY SECTOR(S) EXT 25 00 01 00 00 00 e0 00 00:13:19.390 READ DMA EXT 42 00 10 ef 7a 86 e0 00 00:13:19.374 READ VERIFY SECTOR(S) EXT 25 00 01 00 00 00 e0 00 00:13:19.364 READ DMA EXT 42 00 10 df 7a 86 e0 00 00:13:25.719 READ VERIFY SECTOR(S) EXT Error 6 occurred at disk power-on lifetime: 45132 hours (1880 days + 12 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 -- -- -- -- -- -- -- 40 51 0c e3 7a 86 e0 Error: UNC at LBA = 0x00867ae3 = 8813283 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 42 00 10 df 7a 86 e0 00 00:13:20.942 READ VERIFY SECTOR(S) EXT 42 00 20 df 7a 86 e0 00 00:13:19.390 READ VERIFY SECTOR(S) EXT 25 00 01 00 00 00 e0 00 00:13:19.374 READ DMA EXT 42 00 20 bf 7a 86 e0 00 00:13:19.364 READ VERIFY SECTOR(S) EXT 25 00 01 00 00 00 e0 00 00:13:19.351 READ DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 45910 - # 2 Short captive Completed without error 00% 45131 - # 3 Short captive Completed without error 00% 23782 - # 4 Short captive Completed without error 00% 22503 - # 5 Short offline Completed without error 00% 0 - 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. Quote Link to comment
tdallen Posted November 10, 2014 Share Posted November 10, 2014 Have you gone to the Packages tab in unMenu and installed Screen? It does not appear so. I'm not a Smart expert, but I don't see anything wrong with the smart report you posted. What kind of problem do you think you having with sdd? Quote Link to comment
born2ride Posted November 10, 2014 Author Share Posted November 10, 2014 That's the issue is it says install screen not in but I thought I did that step.. Step 5 Of wiki http://lime-technology.com/wiki/index.php/Configuration_Tutorial.. I dont have a solid state drive installed.. I am just trying to set up and get thought preclear. Quote Link to comment
tdallen Posted November 10, 2014 Share Posted November 10, 2014 Go into unMenu, http://tower:8080 Click on the tab for Pkg Manager Scroll down to the button that says Select screen-4.0.3-i486-1.tgz - mine is near the bottom. Beside it should be: screen (screen manager with VT100/ANSI terminal emulation) Currently Installed. Will be automatically Re-Installed upon Re-Boot. Is that what yours says? I can only see pictures in your last post, unfortunately - none of the earlier ones are working for me. Quote Link to comment
born2ride Posted November 10, 2014 Author Share Posted November 10, 2014 It says not currently installed. I will install.. How do I make system do a clean reboot? Quote Link to comment
tdallen Posted November 11, 2014 Share Posted November 11, 2014 Your shut down and restart unRAID from the main web page (http://tower). unMenu can install a "better" powerdown script if you want - it tries to provide a cleaner shutdown and supports ctl-alt-del. The primary way to shutdown is still from the main web page, though. Quote Link to comment
born2ride Posted November 11, 2014 Author Share Posted November 11, 2014 Dam it was staring me right in the face!! What is a better powerdown script and how to load? I am going to try do pre clear next.. Another quick question. I am using a 250gb drive for parity , 3t and 2t Should I use a larger drive for parity ALso This will not install after boot? Ps i dont know y snag it is making shitty pic now! Quote Link to comment
tdallen Posted November 11, 2014 Share Posted November 11, 2014 Installing unMenu packages is always a two step process - first "Select" to download, then enable to be automatically installed on re-boot. I use screen a lot, so I think it is worth enabling to be installed on re-boot. The clean powerdown script can be installed from the same package page as the Screen package in unMenu. It is a requirement that your parity drive be as large as the largest drive in your array so you'll have to use one of your 3TB drives for parity. Quote Link to comment
born2ride Posted November 11, 2014 Author Share Posted November 11, 2014 I was thinking the menu did not install correctly. It works.. I pulled out the 250gb and put in another 1tb how do I get the tower to stop seeing it as the 250? How does preclear do all three drives? I am reading it but getting lost with -a,-A ,dex,sdx, etc?? Quote Link to comment
itimpi Posted November 12, 2014 Share Posted November 12, 2014 How does preclear do all three drives? I am reading it but getting lost with -a,-A ,dex,sdx, etc?? You have to run Pre-clear against each drive individually (although they can be done in parallel). As a safety mesuer pre-clear will only run against drives that have not yet been allocated to the array. Most of the command line options are likely not to be needed - the one of most use being the -l option to show which drives are available for pre-clear to use and their /dev/sdX identifiers. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.