December 28, 201015 yr Does anyone else have issues trying to get to unmenu? When I put in my IP address of the unRAID box or using it's hostname :8080 it takes either like 15 minutes to hit the home screen or it'll just time out and the service will fail and I have to telnet in and start up unmenu manually again..
December 28, 201015 yr Does anyone else have issues trying to get to unmenu? When I put in my IP address of the unRAID box or using it's hostname :8080 it takes either like 15 minutes to hit the home screen or it'll just time out and the service will fail and I have to telnet in and start up unmenu manually again.. It sounds like there is an IP conflict somewhere on your network. Rajahal had a similar problem a while back and I can't remember exactly what fixed it. I would try restarting the router and/or the unRAID server.
December 28, 201015 yr Author Does anyone else have issues trying to get to unmenu? When I put in my IP address of the unRAID box or using it's hostname :8080 it takes either like 15 minutes to hit the home screen or it'll just time out and the service will fail and I have to telnet in and start up unmenu manually again.. It sounds like there is an IP conflict somewhere on your network. Rajahal had a similar problem a while back and I can't remember exactly what fixed it. I would try restarting the router and/or the unRAID server. I've tried restarting the server and nothing.. I am going to try later forwarding port 8080 to it.. nothing is mapped to 8080 right now so I don't think there's a port conflict there.. If you find out what Rajahal did.. please post it up.
December 28, 201015 yr Does anyone else have issues trying to get to unmenu? When I put in my IP address of the unRAID box or using it's hostname :8080 it takes either like 15 minutes to hit the home screen or it'll just time out and the service will fail and I have to telnet in and start up unmenu manually again.. It sounds like there is an IP conflict somewhere on your network. Rajahal had a similar problem a while back and I can't remember exactly what fixed it. I would try restarting the router and/or the unRAID server. I've tried restarting the server and nothing.. I am going to try later forwarding port 8080 to it.. nothing is mapped to 8080 right now so I don't think there's a port conflict there.. If you find out what Rajahal did.. please post it up. usually it is your router improperly set to first look on the wide-area net, and then the local lan. (or a browser where a proxy has been set/hijacked by your ISP) Joe L.
December 29, 201015 yr I don't understand why you'd port forward on your LAN . Did you check your workgroup settings?
December 29, 201015 yr Author Does anyone else have issues trying to get to unmenu? When I put in my IP address of the unRAID box or using it's hostname :8080 it takes either like 15 minutes to hit the home screen or it'll just time out and the service will fail and I have to telnet in and start up unmenu manually again.. It sounds like there is an IP conflict somewhere on your network. Rajahal had a similar problem a while back and I can't remember exactly what fixed it. I would try restarting the router and/or the unRAID server. I've tried restarting the server and nothing.. I am going to try later forwarding port 8080 to it.. nothing is mapped to 8080 right now so I don't think there's a port conflict there.. If you find out what Rajahal did.. please post it up. usually it is your router improperly set to first look on the wide-area net, and then the local lan. (or a browser where a proxy has been set/hijacked by your ISP) Joe L. I have an Airport Extreme.. I'm not sure if that's an option. Say in Firefox for example.. how would I adjust my proxy to check these things? Or if I were to point my hosts file on my local machine to the NAS.. would that make it work?
December 29, 201015 yr Author I don't understand why you'd port forward on your LAN . Did you check your workgroup settings? I haven't done it. Realize I don't want to since I don't want anyone or me.. from the outside world to be able to access it. What workgroup settings would I have to change?
December 29, 201015 yr I don't understand why you'd port forward on your LAN . Did you check your workgroup settings? I haven't done it. Realize I don't want to since I don't want anyone or me.. from the outside world to be able to access it. What workgroup settings would I have to change? Windows has workgroups. OS X does not. Which are you on?
December 29, 201015 yr Author I don't understand why you'd port forward on your LAN . Did you check your workgroup settings? I haven't done it. Realize I don't want to since I don't want anyone or me.. from the outside world to be able to access it. What workgroup settings would I have to change? Windows has workgroups. OS X does not. Which are you on? Windows. Also have an OSX machine too and it does the same thing. What I think might be happening is that on my local machine I have my DNS servers as Google's DNS.. and I have the DNS entries on the router pointing to Google as well.. Could that be it?
December 29, 201015 yr Workgroups is on the settings tab in UNraid and in the properties of your computer on your PC. They should match. Check this first. When you telnet in to start up unmenu do you just restart it or do you kill it and then restart it? It sounds like you might be running out of memory. I would restart and the capture a syslog immediately after if fails again.
December 29, 201015 yr Author Workgroups is on the settings tab in UNraid and in the properties of your computer on your PC. They should match. Check this first. When you telnet in to start up unmenu do you just restart it or do you kill it and then restart it? It sounds like you might be running out of memory. I would restart and the capture a syslog immediately after if fails again. Yeah they're definitely in the same workgroup, didn't know you were asking about that I guess for some reason.. I have 4GB of RAM installed, shouldn't be running out.. When I restart it I usually do a killall awk and then /boot/unmenu/uu after it. I'll get a syslog later after it fails and post it.
January 6, 201115 yr Author Alright. This is the syslog after unmenu fails.. it's still doing it and I've made sure it's in the same workgroup and all.. syslog.txt
January 6, 201115 yr Alright. This is the syslog after unmenu fails.. it's still doing it and I've made sure it's in the same workgroup and all.. You did not include the initial portion of the system log where it initially describes "ata5" but that disk is timing out pretty badly. The OS keeps resetting the disk in an attempt to restore communications to it. Jan 6 06:47:31 DangNas kernel: ata5.00: failed command: SMART Jan 6 06:47:31 DangNas kernel: ata5.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Jan 6 06:47:31 DangNas kernel: res 40/00:00:00:4f:c2/00:00:00:4f:c2/a0 Emask 0x4 (timeout) Jan 6 06:47:31 DangNas kernel: ata5.00: status: { DRDY } Jan 6 06:47:31 DangNas kernel: ata5: hard resetting link Jan 6 06:47:32 DangNas kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 6 06:47:32 DangNas kernel: ata5.00: configured for UDMA/33 Jan 6 06:47:32 DangNas kernel: ata5: EH complete Jan 6 06:48:02 DangNas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 6 06:48:02 DangNas kernel: ata5.00: failed command: SMART Jan 6 06:48:02 DangNas kernel: ata5.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Jan 6 06:48:02 DangNas kernel: res 40/00:00:00:4f:c2/00:00:00:4f:c2/a0 Emask 0x4 (timeout) Jan 6 06:48:02 DangNas kernel: ata5.00: status: { DRDY } Jan 6 06:48:02 DangNas kernel: ata5: hard resetting link Jan 6 06:48:03 DangNas kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 6 06:48:03 DangNas kernel: ata5.00: configured for UDMA/33 Jan 6 06:48:03 DangNas kernel: ata5: EH complete Jan 6 06:48:33 DangNas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 6 06:48:33 DangNas kernel: ata5.00: failed command: SMART Jan 6 06:48:33 DangNas kernel: ata5.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Jan 6 06:48:33 DangNas kernel: res 40/00:00:00:4f:c2/00:00:00:4f:c2/a0 Emask 0x4 (timeout) Jan 6 06:48:33 DangNas kernel: ata5.00: status: { DRDY } Jan 6 06:48:33 DangNas kernel: ata5: hard resetting link Jan 6 06:48:34 DangNas kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 6 06:48:34 DangNas kernel: ata5.00: configured for UDMA/33 Jan 6 06:48:34 DangNas kernel: ata5: EH complete Jan 6 06:49:04 DangNas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 6 06:49:04 DangNas kernel: ata5.00: failed command: SMART Jan 6 06:49:04 DangNas kernel: ata5.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Jan 6 06:49:04 DangNas kernel: res 40/00:00:00:4f:c2/00:00:00:4f:c2/a0 Emask 0x4 (timeout) Jan 6 06:49:04 DangNas kernel: ata5.00: status: { DRDY } Jan 6 06:49:04 DangNas kernel: ata5: hard resetting link Jan 6 06:49:05 DangNas kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 6 06:49:05 DangNas kernel: ata5.00: configured for UDMA/33 Jan 6 06:49:05 DangNas kernel: ata5: EH complete Jan 6 06:49:35 DangNas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 6 06:49:35 DangNas kernel: ata5.00: failed command: SMART Jan 6 06:49:35 DangNas kernel: ata5.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Jan 6 06:49:35 DangNas kernel: res 40/00:00:00:4f:c2/00:00:00:4f:c2/a0 Emask 0x4 (timeout) Jan 6 06:49:35 DangNas kernel: ata5.00: status: { DRDY } Jan 6 06:49:35 DangNas kernel: ata5: hard resetting link Jan 6 06:49:36 DangNas kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 6 06:49:36 DangNas kernel: ata5.00: configured for UDMA/33 Jan 6 06:49:36 DangNas kernel: ata5: EH complete Jan 6 06:50:06 DangNas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 6 06:50:06 DangNas kernel: ata5.00: failed command: SMART Jan 6 06:50:06 DangNas kernel: ata5.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Jan 6 06:50:06 DangNas kernel: res 40/00:00:00:4f:c2/00:00:00:4f:c2/a0 Emask 0x4 (timeout) Jan 6 06:50:06 DangNas kernel: ata5.00: status: { DRDY } Jan 6 06:50:06 DangNas kernel: ata5: hard resetting link
January 6, 201115 yr Author Alright. This is the syslog after unmenu fails.. it's still doing it and I've made sure it's in the same workgroup and all.. You did not include the initial portion of the system log where it initially describes "ata5" but that disk is timing out pretty badly. The OS keeps resetting the disk in an attempt to restore communications to it. Well I removed all of yesterday's logs but I just took a look at it and I don't see anything above it.. I just grab it from /var/log/syslog right? Do you think that disk is going bad?
January 6, 201115 yr Alright. This is the syslog after unmenu fails.. it's still doing it and I've made sure it's in the same workgroup and all.. You did not include the initial portion of the system log where it initially describes "ata5" but that disk is timing out pretty badly. The OS keeps resetting the disk in an attempt to restore communications to it. Well I removed all of yesterday's logs but I just took a look at it and I don't see anything above it.. I just grab it from /var/log/syslog right? Do you think that disk is going bad? When logs get over a certain size they are rotated out. You might find the previous content in /var/log/syslog.1 or /var/log/syslog.2 As far as the drive... can't tell from here if it is the drive, the drive cable, the power cable, the disk controller... all we know is it is timing out. Joe L.
January 6, 201115 yr Author Alright. This is the syslog after unmenu fails.. it's still doing it and I've made sure it's in the same workgroup and all.. You did not include the initial portion of the system log where it initially describes "ata5" but that disk is timing out pretty badly. The OS keeps resetting the disk in an attempt to restore communications to it. Well I removed all of yesterday's logs but I just took a look at it and I don't see anything above it.. I just grab it from /var/log/syslog right? Do you think that disk is going bad? When logs get over a certain size they are rotated out. You might find the previous content in /var/log/syslog.1 or /var/log/syslog.2 As far as the drive... can't tell from here if it is the drive, the drive cable, the power cable, the disk controller... all we know is it is timing out. Joe L. How would I find out which disk is ata5? I tried attaching syslog1 and syslog2 but they are over a meg each.. I think the reason those are split up is because it's stored for longer.. syslog1 dates back to the 31st of December. The 2nd log is the same as what I had attached for today.
January 6, 201115 yr Alright. This is the syslog after unmenu fails.. it's still doing it and I've made sure it's in the same workgroup and all.. You did not include the initial portion of the system log where it initially describes "ata5" but that disk is timing out pretty badly. The OS keeps resetting the disk in an attempt to restore communications to it. Well I removed all of yesterday's logs but I just took a look at it and I don't see anything above it.. I just grab it from /var/log/syslog right? Do you think that disk is going bad? When logs get over a certain size they are rotated out. You might find the previous content in /var/log/syslog.1 or /var/log/syslog.2 As far as the drive... can't tell from here if it is the drive, the drive cable, the power cable, the disk controller... all we know is it is timing out. Joe L. How would I find out which disk is ata5? I tried attaching syslog1 and syslog2 but they are over a meg each.. I think the reason those are split up is because it's stored for longer.. syslog1 dates back to the 31st of December. The 2nd log is the same as what I had attached for today. I wish there was an easy answer to the question of "which disk is ata5?" The only clues I am aware of are in the initial syslog entries output when you first boot the server. You could try this command and see if it prints anything you might be able use as clues: grep -i ata5 /var/log/syslog.1 | sed 25q It will print the first 25 lines in the syslog file mentioning that device.
January 6, 201115 yr Author Alright. This is the syslog after unmenu fails.. it's still doing it and I've made sure it's in the same workgroup and all.. You did not include the initial portion of the system log where it initially describes "ata5" but that disk is timing out pretty badly. The OS keeps resetting the disk in an attempt to restore communications to it. Well I removed all of yesterday's logs but I just took a look at it and I don't see anything above it.. I just grab it from /var/log/syslog right? Do you think that disk is going bad? When logs get over a certain size they are rotated out. You might find the previous content in /var/log/syslog.1 or /var/log/syslog.2 As far as the drive... can't tell from here if it is the drive, the drive cable, the power cable, the disk controller... all we know is it is timing out. Joe L. How would I find out which disk is ata5? I tried attaching syslog1 and syslog2 but they are over a meg each.. I think the reason those are split up is because it's stored for longer.. syslog1 dates back to the 31st of December. The 2nd log is the same as what I had attached for today. I wish there was an easy answer to the question of "which disk is ata5?" The only clues I am aware of are in the initial syslog entries output when you first boot the server. You could try this command and see if it prints anything you might be able use as clues: grep -i ata5 /var/log/syslog.1 | sed 25q It will print the first 25 lines in the syslog file mentioning that device. This is what I get.. Dec 31 04:47:33 DangNas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x6 frozen Dec 31 04:47:33 DangNas kernel: ata5.00: failed command: SMART Dec 31 04:47:33 DangNas kernel: ata5.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Dec 31 04:47:33 DangNas kernel: ata5.00: status: { DRDY } Dec 31 04:47:33 DangNas kernel: ata5: hard resetting link Dec 31 04:47:33 DangNas kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SContro l 310) Dec 31 04:47:33 DangNas kernel: ata5.00: configured for UDMA/33 Dec 31 04:47:33 DangNas kernel: ata5: EH complete Dec 31 04:48:04 DangNas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x6 frozen Dec 31 04:48:04 DangNas kernel: ata5.00: failed command: SMART Dec 31 04:48:04 DangNas kernel: ata5.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Dec 31 04:48:04 DangNas kernel: ata5.00: status: { DRDY } Dec 31 04:48:04 DangNas kernel: ata5: hard resetting link Dec 31 04:48:04 DangNas kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SContro l 310) Dec 31 04:48:04 DangNas kernel: ata5.00: configured for UDMA/33 Dec 31 04:48:04 DangNas kernel: ata5: EH complete Dec 31 04:48:35 DangNas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x6 frozen Dec 31 04:48:35 DangNas kernel: ata5.00: failed command: SMART Dec 31 04:48:35 DangNas kernel: ata5.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Dec 31 04:48:35 DangNas kernel: ata5.00: status: { DRDY } Dec 31 04:48:35 DangNas kernel: ata5: hard resetting link Dec 31 04:48:35 DangNas kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SContro l 310) Dec 31 04:48:35 DangNas kernel: ata5.00: configured for UDMA/33 Dec 31 04:48:35 DangNas kernel: ata5: EH complete Dec 31 04:49:06 DangNas kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x6 frozen
January 6, 201115 yr unfortunately, it does not go back far enough to when you first rebooted the server. You could try the same command on syslog.2, or stop the server when convenient, reboot, and try the command soon after the reboot. Joe L.
Archived
This topic is now archived and is closed to further replies.