September 20, 200817 yr I was playing with Joe L's awesome unmenu and was scoping out my bootlog and noticed these two things: Sep 20 18:22:39 Tower1 kernel: system 00:01: ioport range 0x4d0-0x4d1 has been reserved Sep 20 18:22:39 Tower1 kernel: system 00:01: ioport range 0x290-0x29f has been reserved Sep 20 18:22:39 Tower1 kernel: system 00:01: ioport range 0x800-0x87f has been reserved Sep 20 18:22:39 Tower1 kernel: system 00:01: ioport range 0x290-0x294 has been reserved Sep 20 18:22:39 Tower1 kernel: system 00:01: ioport range 0x880-0x88f has been reserved Sep 20 18:22:39 Tower1 kernel: system 00:08: ioport range 0x400-0x4bf could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:09: iomem range 0xf0000000-0xf3ffffff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0xdb800-0xdbfff has been reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0xf0000-0xf7fff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0xf8000-0xfbfff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0xfc000-0xfffff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0x3f7f0000-0x3f7fffff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0x0-0x9ffff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0x100000-0x3f7effff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0xfec00000-0xfec00fff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0xfed13000-0xfed1dfff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0xfed20000-0xfed8ffff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0xfee00000-0xfee00fff could not be reserved Sep 20 18:22:39 Tower1 kernel: system 00:0a: iomem range 0xffb00000-0xffb7ffff could not be reserved And also: Sep 20 18:22:44 Tower1 emhttp: get_config_idx: fopen /boot/config/shares/Movies.cfg: No such file or directory - assigning defaults I assume the later one means something is wrong with my Movies share, but it exists, is accessible, and appears to be working OK. What do they mean? Do they signal that something important is wrong? Here is the full bootlog if it helps: http://pastebin.com/m5dbaff9
September 21, 200817 yr I was playing with Joe L's awesome unmenu and was scoping out my bootlog and noticed these two things: Nice having easy access and visibility, isn't it. Sep 20 18:22:44 Tower1 emhttp: get_config_idx: fopen /boot/config/shares/Movies.cfg: No such file or directory - assigning defaults Nothing is wrong with your "Movies" share, it is just that you apparently did not configure the "Movies" share in the user-shares. Instead, the share was created because the folder had pre-existed. unRAID simply applied a "default" configuration in the absence of one you created. I've got two of the same messages in my log... for folders I created at the linux command line, before I enabled user shares. I can't help you with the memory allocation messages. You might "google" them to see if they are an issue, or just a result of memory being reserved by various pieces of hardware. Joe L.
September 21, 200817 yr Those ioport and iomem sections are fairly common, nothing to worry about. The more recent kernels report more info, but you should consider it similar to turning on a debug mode. You will see a lot more messages that are only of technical interest. The problem sometimes with exposing too much info is that less experienced users may be alarmed by things that really aren't that important.
September 22, 200817 yr Author Thanks. I'll have to check my other unraid server wehn I get home and see if I get those same memory errors since they are identical setups.
Archived
This topic is now archived and is closed to further replies.