William Posted July 21, 2009 Share Posted July 21, 2009 I upgraded from plus to pro today but can no longer access my Tower through my Mac Pro or Mac Air using Firefox. Did it change the address? When I type in http://tower/main.htm I get the website http://www.tower.com/main.htm. However it works on my PC using Firefox. I also use Xmarks to sync my bookmarks. Quote Link to comment
Joe L. Posted July 21, 2009 Share Posted July 21, 2009 I upgraded from plus to pro today but can no longer access my Tower through my Mac Pro or Mac Air using Firefox. Did it change the address? When I type in http://tower/main.htm I get the website http://www.tower.com/main.htm. However it works on my PC using Firefox. I also use Xmarks to sync my bookmarks. if you have a keyboard and monitor attached, you can log in as "root" and then type ifconfig eth0 The "Inet" address listed in the output should be your IP address (mine is shown below, IP address is in blue). ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:11:11:75:fb:7e inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:20072240 errors:0 dropped:0 overruns:0 frame:0 TX packets:56595640 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:477997710 (455.8 MiB) TX bytes:1011699148 (964.8 MiB) If you can get to the server via your PC, you can go to the management interface and click on the "settings" link. The network configuration, and IP address, should be displayed there. How did you "upgrade" Did you completely reformat/reload the flash drive, or just install the new "pro.key" file and reboot? Joe L. Quote Link to comment
William Posted July 21, 2009 Author Share Posted July 21, 2009 I upgraded from plus to pro today but can no longer access my Tower through my Mac Pro or Mac Air using Firefox. Did it change the address? When I type in http://tower/main.htm I get the website http://www.tower.com/main.htm. However it works on my PC using Firefox. I also use Xmarks to sync my bookmarks. if you have a keyboard and monitor attached, you can log in as "root" and then type ifconfig eth0 The "Inet" address listed in the output should be your IP address (mine is shown below, IP address is in blue). ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:11:11:75:fb:7e inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:20072240 errors:0 dropped:0 overruns:0 frame:0 TX packets:56595640 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:477997710 (455.8 MiB) TX bytes:1011699148 (964.8 MiB) If you can get to the server via your PC, you can go to the management interface and click on the "settings" link. The network configuration, and IP address, should be displayed there. How did you "upgrade" Did you completely reformat/reload the flash drive, or just install the new "pro.key" file and reboot? Joe L. Got it thanks, I don't see my 2 new drives though. Quote Link to comment
Joe L. Posted July 21, 2009 Share Posted July 21, 2009 Have you "assigned" them yet? (Click on the drop-down box on any of the un-assigned slots in the array to see if the new disks are listed there to be assigned.) It is up to you to assign them. Quote Link to comment
prostuff1 Posted July 21, 2009 Share Posted July 21, 2009 I upgraded from plus to pro today but can no longer access my Tower through my Mac Pro or Mac Air using Firefox. Did it change the address? When I type in http://tower/main.htm I get the website http://www.tower.com/main.htm. However it works on my PC using Firefox. I also use Xmarks to sync my bookmarks. Take a look at This post It should get //tower working on the Mac side. Quote Link to comment
William Posted July 21, 2009 Author Share Posted July 21, 2009 Have you "assigned" them yet? (Click on the drop-down box on any of the un-assigned slots in the array to see if the new disks are listed there to be assigned.) It is up to you to assign them. There is nothing in the drop down box to assign. I checked and cables are fin. It may be some incompatibility with my Rosewell card. I read it is just plug and play ( do I need to load drivers?) Quote Link to comment
William Posted July 22, 2009 Author Share Posted July 22, 2009 Found my my syslog (I think) but it is way too big to post. I'm scowling through it but not sure what I'm looking for. EDIT: Here is some disk stuff but I don't see the 2 new disks. Jul 21 20:15:38 Tower emhttp: Device inventory: Jul 21 20:15:38 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 (sda) ata-ST31000340AS_5QJ01G51 Jul 21 20:15:38 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 (sdb) ata-WDC_WD4000AAKS-00TMA0_WD-WCAPW1876621 Jul 21 20:15:38 Tower emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 (sdc) ata-WDC_WD4000AAKS-00TMA0_WD-WCAPW1810826 Jul 21 20:15:38 Tower emhttp: pci-0000:00:1f.2-scsi-1:0:1:0 (sdd) ata-ST31000340AS_5QJ01FD4 Jul 21 20:15:38 Tower emhttp: pci-0000:00:1f.5-scsi-0:0:0:0 (sde) ata-ST3750330AS_3QK00LPN Jul 21 20:15:38 Tower emhttp: pci-0000:00:1f.5-scsi-1:0:0:0 (sdf) ata-ST3750330AS_3QK0110E Jul 21 20:15:38 Tower emhttp: shcmd (3): rmmod md-mod >>/var/log/go 2>&1 Jul 21 20:15:38 Tower emhttp: shcmd: shcmd (3): exit status: 1 Jul 21 20:15:38 Tower emhttp: shcmd (4): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,16,8,32,8,48,8,64,8,80,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1 Jul 21 20:15:38 Tower kernel: md: unRAID driver 0.95.0 installed Jul 21 20:15:38 Tower kernel: md: xor using function: pIII_sse (7293.600 MB/sec) Jul 21 20:15:38 Tower kernel: md: import disk0: [8,0] (sda) ST31000340AS 5QJ01G51 offset: 63 size: 976762552 Jul 21 20:15:38 Tower kernel: md: import disk1: [8,16] (sdb) WDC WD4000AAKS-00TMA0 WD-WCAPW1876621 offset: 63 size: 390711352 Jul 21 20:15:38 Tower kernel: md: import disk2: [8,32] (sdc) WDC WD4000AAKS-00TMA0 WD-WCAPW1810826 offset: 63 size: 390711352 Jul 21 20:15:38 Tower kernel: md: import disk3: [8,48] (sdd) ST31000340AS 5QJ01FD4 offset: 63 size: 976762552 Jul 21 20:15:38 Tower kernel: md: import disk4: [8,64] (sde) ST3750330AS 3QK00LPN offset: 63 size: 732574552 Jul 21 20:15:38 Tower kernel: md: import disk5: [8,80] (sdf) ST3750330AS 3QK0110E offset: 63 size: 732574552 Jul 21 20:15:39 Tower emhttp: shcmd (5): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Jul 21 20:15:39 Tower emhttp: shcmd (6): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Jul 21 20:15:39 Tower emhttp: shcmd (7): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Jul 21 20:15:39 Tower emhttp: shcmd (: crontab /var/spool/cron/crontabs/root Jul 21 20:15:39 Tower kernel: md: import disk0: [8,0] (sda) ST31000340AS 5QJ01G51 offset: 63 size: 976762552 Jul 21 20:15:39 Tower kernel: md: import disk1: [8,16] (sdb) WDC WD4000AAKS-00TMA0 WD-WCAPW1876621 offset: 63 size: 390711352 Jul 21 20:15:39 Tower kernel: md: import disk2: [8,32] (sdc) WDC WD4000AAKS-00TMA0 WD-WCAPW1810826 offset: 63 size: 390711352 Jul 21 20:15:39 Tower kernel: md: import disk3: [8,48] (sdd) ST31000340AS 5QJ01FD4 offset: 63 size: 976762552 Jul 21 20:15:39 Tower kernel: md: import disk4: [8,64] (sde) ST3750330AS 3QK00LPN offset: 63 size: 732574552 Jul 21 20:15:39 Tower kernel: md: import disk5: [8,80] (sdf) ST3750330AS 3QK0110E offset: 63 size: 732574552 Jul 21 20:15:39 Tower emhttp: shcmd (9): /etc/rc.d/rc.samba stop >/dev/null Jul 21 20:15:39 Tower emhttp: shcmd (10): /etc/rc.d/rc.nfsd stop >/dev/null Jul 21 20:15:40 Tower emhttp: shcmd (11): cp /etc/exports- /etc/exports Jul 21 20:15:40 Tower emhttp: shcmd (12): /etc/rc.d/rc.samba start >/dev/null Jul 21 20:15:40 Tower emhttp: shcmd (13): /etc/rc.d/rc.nfsd start >/dev/null Jul 21 20:15:40 Tower kernel: mdcmd (3): start Jul 21 20:15:40 Tower kernel: md: import disk0: [8,0] (sda) ST31000340AS 5QJ01G51 offset: 63 size: 976762552 Jul 21 20:15:40 Tower kernel: md: import disk1: [8,16] (sdb) WDC WD4000AAKS-00TMA0 WD-WCAPW1876621 offset: 63 size: 390711352 Jul 21 20:15:40 Tower kernel: md: import disk2: [8,32] (sdc) WDC WD4000AAKS-00TMA0 WD-WCAPW1810826 offset: 63 size: 390711352 Jul 21 20:15:40 Tower kernel: md: import disk3: [8,48] (sdd) ST31000340AS 5QJ01FD4 offset: 63 size: 976762552 Jul 21 20:15:40 Tower kernel: md: import disk4: [8,64] (sde) ST3750330AS 3QK00LPN offset: 63 size: 732574552 Jul 21 20:15:40 Tower kernel: md: import disk5: [8,80] (sdf) ST3750330AS 3QK0110E offset: 63 size: 732574552 Jul 21 20:15:40 Tower kernel: unraid: allocated 13240kB Jul 21 20:15:40 Tower kernel: md1: running, size: 390711352 blocks Jul 21 20:15:40 Tower kernel: md2: running, size: 390711352 blocks Jul 21 20:15:40 Tower kernel: md3: running, size: 976762552 blocks Jul 21 20:15:40 Tower kernel: md4: running, size: 732574552 blocks Jul 21 20:15:40 Tower kernel: md5: running, size: 732574552 blocks Jul 21 20:15:40 Tower kernel: mdcmd (5): check Jul 21 20:15:40 Tower kernel: md: recovery thread woken up ... Jul 21 20:15:40 Tower emhttp: shcmd (14): mkdir -m 700 /mnt/disk1 Jul 21 20:15:40 Tower emhttp: shcmd (14): mkdir -m 700 /mnt/disk2 Jul 21 20:15:40 Tower emhttp: shcmd (14): mkdir -m 700 /mnt/disk3 Jul 21 20:15:40 Tower emhttp: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 >/dev/null 2>&1 Jul 21 20:15:40 Tower emhttp: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 >/dev/null 2>&1 Jul 21 20:15:40 Tower emhttp: shcmd (14): mkdir -m 700 /mnt/disk4 Jul 21 20:15:40 Tower emhttp: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3 >/dev/null 2>&1 Jul 21 20:15:40 Tower emhttp: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 >/dev/null 2>&1 Jul 21 20:15:40 Tower emhttp: shcmd (14): mkdir -m 700 /mnt/disk5 Jul 21 20:15:40 Tower emhttp: shcmd (15): mount -t reiserfs -o noatime,nodiratime /dev/md5 /mnt/disk5 >/dev/null 2>&1 Jul 21 20:15:40 Tower kernel: md: recovery thread has nothing to resync Jul 21 20:15:40 Tower kernel: ReiserFS: md1: found reiserfs format "3.6" with standard journal Jul 21 20:15:40 Tower kernel: ReiserFS: md1: using ordered data mode Jul 21 20:15:40 Tower kernel: ReiserFS: md1: journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jul 21 20:15:40 Tower kernel: ReiserFS: md1: checking transaction log (md1) Jul 21 20:15:40 Tower kernel: ReiserFS: md5: found reiserfs format "3.6" with standard journal Jul 21 20:15:40 Tower kernel: ReiserFS: md5: using ordered data mode Jul 21 20:15:40 Tower kernel: ReiserFS: md2: found reiserfs format "3.6" with standard journal Jul 21 20:15:40 Tower kernel: ReiserFS: md2: using ordered data mode Jul 21 20:15:40 Tower kernel: ReiserFS: md3: found reiserfs format "3.6" with standard journal Jul 21 20:15:40 Tower kernel: ReiserFS: md3: using ordered data mode Jul 21 20:15:40 Tower kernel: ReiserFS: md4: found reiserfs format "3.6" with standard journal Jul 21 20:15:40 Tower kernel: ReiserFS: md4: using ordered data mode Jul 21 20:15:40 Tower kernel: ReiserFS: md5: journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jul 21 20:15:40 Tower kernel: ReiserFS: md5: checking transaction log (md5) Jul 21 20:15:40 Tower kernel: ReiserFS: md2: journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jul 21 20:15:40 Tower kernel: ReiserFS: md2: checking transaction log (md2) Jul 21 20:15:40 Tower kernel: ReiserFS: md3: journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jul 21 20:15:40 Tower kernel: ReiserFS: md3: checking transaction log (md3) Jul 21 20:15:40 Tower kernel: ReiserFS: md4: journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jul 21 20:15:40 Tower kernel: ReiserFS: md4: checking transaction log (md4) Jul 21 20:15:40 Tower kernel: ReiserFS: md5: Using r5 hash to sort names Jul 21 20:15:40 Tower kernel: ReiserFS: md1: Using r5 hash to sort names Jul 21 20:15:40 Tower kernel: ReiserFS: md2: Using r5 hash to sort names Jul 21 20:15:40 Tower kernel: ReiserFS: md4: Using r5 hash to sort names Jul 21 20:15:40 Tower kernel: ReiserFS: md3: Using r5 hash to sort names Jul 21 20:15:40 Tower kernel: can't shrink filesystem on-line Jul 21 20:15:41 Tower last message repeated 4 times Jul 21 20:15:41 Tower emhttp: shcmd (14): cp /etc/exports- /etc/exports Jul 21 20:15:41 Tower emhttp: shcmd (15): mkdir -m 700 /mnt/user Jul 21 20:15:41 Tower emhttp: shcmd (16): /usr/local/sbin/shfs /mnt/user Jul 21 20:15:42 Tower shfs: duplicate object: /mnt/disk2/./.DS_Store Jul 21 20:15:42 Tower shfs: duplicate object: /mnt/disk5/./.DS_Store Jul 21 20:15:42 Tower emhttp: shcmd (17): killall -HUP smbd Jul 21 20:15:42 Tower emhttp: shcmd (18): /etc/rc.d/rc.nfsd restart >/dev/null Jul 21 20:15:47 Tower ntpd[1279]: synchronized to 207.182.243.123, stratum 2 Jul 21 20:15:47 Tower ntpd[1279]: time reset +0.163390 s Jul 21 20:17:07 Tower emhttp: shcmd (19): /etc/rc.d/rc.samba stop >/dev/null Jul 21 20:17:07 Tower emhttp: shcmd (20): /etc/rc.d/rc.nfsd stop >/dev/null Jul 21 20:17:08 Tower emhttp: Spinning up all drives... Jul 21 20:17:08 Tower emhttp: shcmd (21): sync Jul 21 20:17:08 Tower emhttp: shcmd (22): umount /mnt/user Jul 21 20:17:08 Tower emhttp: shcmd (23): rmdir /mnt/user Jul 21 20:17:08 Tower emhttp: shcmd (24): umount /mnt/disk1 Jul 21 20:17:08 Tower emhttp: shcmd (24): umount /mnt/disk2 Jul 21 20:17:08 Tower emhttp: shcmd (24): umount /mnt/disk3 Jul 21 20:17:08 Tower emhttp: shcmd (24): umount /mnt/disk4 Jul 21 20:17:08 Tower emhttp: shcmd (24): umount /mnt/disk5 Jul 21 20:17:09 Tower emhttp: shcmd (25): rmdir /mnt/disk2 Jul 21 20:17:09 Tower emhttp: shcmd (25): rmdir /mnt/disk3 Jul 21 20:17:09 Tower emhttp: shcmd (25): rmdir /mnt/disk1 Jul 21 20:17:09 Tower emhttp: shcmd (25): rmdir /mnt/disk4 Jul 21 20:17:09 Tower emhttp: shcmd (25): rmdir /mnt/disk5 Quote Link to comment
Joe L. Posted July 22, 2009 Share Posted July 22, 2009 Have you "assigned" them yet? (Click on the drop-down box on any of the un-assigned slots in the array to see if the new disks are listed there to be assigned.) It is up to you to assign them. There is nothing in the drop down box to assign. I checked and cables are fin. It may be some incompatibility with my Rosewell card. I read it is just plug and play ( do I need to load drivers?) Nope, no drivers to load. You might need to configure the sata card to have the disks show up as individual drives. You do not want any kind of RAID mode. Does the card show up in the syslog at all? (post your syslog if you are unsure?) What version of unRAID are you running? Joe L. Quote Link to comment
William Posted July 22, 2009 Author Share Posted July 22, 2009 Thanks for adopting me Joe L. This has to be one of the biggest coincidences ever. After extensive trouble shooting (my unRAID is probably about worn out from all the stop and starts) I found that I had 2 power cables that were bad (one new). I now have it up and running. I have assigned one of the new 1.5HD's as parity and it is doing a parity sync at 4%. So I'm using (read only) my unRAID while this is in progress. Thought you couldn't use the unRAID while installing a new HD? I have 3 more HD's to install (the other 1.5TBHD, the removed 1TB parity and a new 1TB HD that will be here today). Do I still need to use the preclear_disk.sh script because installing a new parity disc different than a data (data disk install won't let you run the unRAID)? Quote Link to comment
Joe L. Posted July 22, 2009 Share Posted July 22, 2009 Thanks for adopting me Joe L. This has to be one of the biggest coincidences ever. After extensive trouble shooting (my unRAID is probably about worn out from all the stop and starts) I found that I had 2 power cables that were bad (one new). I now have it up and running. That is good news... In the first post of the "preclear" thread you will see I battled a very similar hardware problem with a "Y" power splitter. I lost a few hairs during those trouble shooting sessions. My "Y" splitter was installed by Tom at lime-tech. It was on the lower set of drive slots I did not use until years after the server was in operation. Complicating things, it was intermittent. I have assigned one of the new 1.5HD's as parity and it is doing a parity sync at 4%. So I'm using (read only) my unRAID while this is in progress. Thought you couldn't use the unRAID while installing a new HD? The reason for clearing a drive (setting it to all zeros) is to easily add it to an array with existing parity. (since it is all zeros, it does not change parity) Since you are just now calculating parity, you can still use the array. Once it is calculated to add a new data drive it must either be pre-cleared, or cleared by unRAID during the install. I have 3 more HD's to install (the other 1.5TBHD, the removed 1TB parity and a new 1TB HD that will be here today). Do I still need to use the preclear_disk.sh script because installing a new parity disc different than a data (data disk install won't let you run the unRAID)? Yes, you should still preclear all the drives before installation. (even the parity drive you just installed could have benefited from it, at least you would have known of any early failure problems with it.) After the parity is fully calculated and its indicator is "green" you should do a parity "check" It is different in that it will "read" the parity disk to ensure it can be read. The initial sync is just writing the parity disk. Both types of operations are necessary for the SMART firmware on the parity-disk to identify bad sectors and reallocate them. (and why pre-clearing a parity drive has a benefit, it both reads and writes to a drive being pre-cleared.) Good luck with your server. Joe L. Quote Link to comment
prostuff1 Posted July 22, 2009 Share Posted July 22, 2009 I preclear ALL disks i add to my unRAID server. I run each drive through 2-3 cycles just to make sure it is not going to crap out on me at some point later on. Granted there is still a possibility of that happening but it is lower since i have run it through with the preclear script. Quote Link to comment
William Posted July 22, 2009 Author Share Posted July 22, 2009 Can I start Preclear while doing a parity sync or check? Also I nave my original parity drive and won't preclear it until after parity sync. Quote Link to comment
prostuff1 Posted July 22, 2009 Share Posted July 22, 2009 Can I start Preclear while doing a parity sync or check? The preclear will only work on disks that are not in the array. And yes, you should be able to start preclearing disks while the parity check is going on. The best thing about the preclear script is that it stress tests a disk, sets the unRAID signature, and allows it to be added to the array very quickly since the long clearing process is avoided (i.e. done by the preclear script). Quote Link to comment
William Posted July 22, 2009 Author Share Posted July 22, 2009 All I get is "-bash: preclear_disk.sh /dev/sdc: No such file or directory". I know the file is there because I can see it from my Mac but it is listed as a .txt file. Also when I try hdparm -i /dev/sdc I get the same message. I think I'm in the correct folder. It's the default and is root@tower:~#. Quote Link to comment
Joe L. Posted July 22, 2009 Share Posted July 22, 2009 All I get is "-bash: preclear_disk.sh /dev/sdc: No such file or directory". I know the file is there because I can see it from my Mac but it is listed as a .txt file. Also when I try hdparm -i /dev/sdc I get the same message. I think I'm in the correct folder. It's the default and is root@tower:~#. The command interperter (bash) is unable to run the program since it is not in the current directory and not in the search PATH. You either did not change directory to where the preclear_disk.sh disk resides, or it is named differently. type cd /boot ls -l preclear_disk.sh You should see the file listed as follows: root@Tower:~# cd /boot root@Tower:/boot# ls -l preclear_disk.sh -rwxrwxrwx 1 root root 32025 Jul 22 13:21 preclear_disk.sh* Its' name should be in all lower case. If it has a .txt suffix, then you did something wrong. The file should be named preclear_disk.sh You will probable want to set your window's explorer to show file extensions. (It is set to hide them by default) In the same way, if you used notepad or some other editor to look at the file you might have accidentally added carriage return characters to the ends of the lines. If so, it will not work either as a shell script under linux. Joe L. Quote Link to comment
William Posted July 22, 2009 Author Share Posted July 22, 2009 Thanks again Joe L. I've it it going. I was in the wrong folder (why doesn't it log on in the root folder ). Linux command logic and syntax is horrible. It make the old DOS look logical. Is there a basic list of commands and syntax for dummies? Quote Link to comment
Joe L. Posted July 22, 2009 Share Posted July 22, 2009 Thanks again Joe L. I've it it going. I was in the wrong folder (why doesn't it log on in the root folder ). Linux command logic and syntax is horrible. It make the old DOS look logical. Is there a basic list of commands and syntax for dummies? In the wiki FAQ list: http://lime-technology.com/wiki/index.php/FAQ#unRAID_Console_and_Addon_Questions 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.