April 14, 200818 yr Hi- I had built an unRaid and was using the latest 4.2.x software version for quite a while trouble-free. It's a Gigabyte mobo w/ gig-E NIC on-board (on the suggested/tested list here.) Then suddenly without any other changes to the system, it was unrelaible network performance. I don't mean slowdowns either- the network shares would be not accessible a minute or two after they were fine. For example, running a large (4GB) download in the background on a relaible XP machine, saving to one of the unRaid drives mounted as a network disk. It would be working fine, then return an error: the operation could not be completed as the network share is inaccessible (something about a domain controller error.) Same thing happens when I mount the unRaid disk(s) from my Mac or another PC. They mount and seem to playback file fine, but then when writing to the unRaid the disk(s) are not accessible and the operation stops. I also tried copying a huge file (35GB) of videos I've made from the unRaid where it is safely tucked away, onto a portable hard drive (USB 2.0.) The copy failed, both using a Mac or a PC- so it's not justr writing to the unRaid that is causing probelms. Copying from it is problematic as well. I tried upgrading to the 4.3 beta 6 to see if that would fix it. Didn't. I also ordered the higher-end Intel gig NIC card suggested here to try instead of my mobo NIC. I got it working on the external NIC but that didn't solve the problem either. Note when I upgraded to 4.3 I just copied over the few new files the instructions said I needed to overwrite on my flash card, so if something else was corrupt I didn't start fresh. I don't want to lose the configuration info or any data, of course. I also tried for kicks formatting the card, which I did using the HP tool, copied my config & unRaid software back onto it,restarted and let parity check finish. All is running but I'm still getting the errors/ dropping of the network/ domain controller errors on tasks like downloading that take more than a few minutes. Any suggestions on what to try next are much appreciated. Thanks
April 14, 200818 yr When you say DC error (domain controller), I'm curious whether this is on a business network/domain or whether this is just a home setup. Can you access the web page for your unraid box when you get this problem? Can you telnet into the machine when you get this problem? Do you have the same problem connecting via the IP address? Instead of going to (in explorer) \\tower\disk1, or \\tower\sharename, try \\192.168.2.100\disk1 or \\192.168.2.100\sharename (of course you need to put in the correct IP address, it probably won't be 192.168.2.100). The reason I ask is to see if somehow you're having a problem with resolving the IP address (your computers translating "tower" into "192.168.2.100"). Also, do you have a fixed IP address for the unraid system, or is it pulling an IP address via DHCP? I can't say for sure what the problem is, but my first steps would be to figure out whether it is a DHCP or DNS issue, and if not... you probably have a problem with the unraid tower/OS itself.
April 14, 200818 yr It sounds like everything works fine for awhile, then the network is lost? If so, if all is OK even once, then everything is configured correctly, on both ends of the networking, and your flash is fine, and your unRAID system is probably fine, although it would be best to see your syslog to confirm that, see my signature. A prime suspect would be the cabling and router between unRAID and your desktop computers. Have there been any network issues between any desktop computer and the router? Is the router getting too hot? Is it possible that a pet or mouse has chewed a cable? Is there a loose cable connection? Is it possible that a source of major electrical interference has been moved to a place where it might cause network disruption, too near a cable or the router? You might try different cables to the unRAID server, and confirm the router is working properly, check its logs immediately after lost network connection. Your syslog captured immediately after a lost network connection may help, to see what unRAID detected.
April 14, 200818 yr Everything you are describing indicates an issue with the LAN, and not necessarily the unRaid software. The fact that you have used more than one network interface card, and more than one version of unRaid seems to me to eliminate them as the possible cause. I would suspect cabling first and the router second. I would like to see a syslog, just in case it is an interrupt issue from the motherboard. Might not be a bad idea to run memtest overnight to make sure it is not a memory related issue. It could also be a conflict on your LAN. Do you use dynamically set IP addresses? or hard-code them? (Two assigned to the same IP address would be bad) Joe L.
April 14, 200818 yr Author "When you say DC error (domain controller), I'm curious whether this is on a business network/domain or whether this is just a home setup." -it's a home setup. I have the unRaid set for workgroup Mshome, as are my two PCs and two Macs. Seems like it might be related though, since my new Leopard MacBook Pro auto-browses available shares on the network when connected, (just one example), and it sometimes shows the unraid tower there and then sometimes it just disappears. Even when I mount a disk from the unraid- it'll stay there for a few, then drop off. Fixed IP address. BTW, I initially changed the name from "tower" to "unraid" in the config page on the web interface as my own preference. When I go to \\unraid\disk1 as a path when mounting network share, or for a UNC file path in programs to locate stored items (such as my movie browser), it works fine. However I've never gotten it to work that way in the web browser. It thinks I'm searching and goes to the lime-technology.com when I type \\unraid\.... (So I have always used \\192.168.100.201\disk1, etc... to get to the web interface.) Anyway, when it seems to lock up I also can't get to the web interface. As far as RobJ's reply, I was thinking something along those lines too, so I moved the tower to a different location on the other side of my basement, connected it to a different ethernet switch with a different cable, and I'm getting the same issue. I will try moving it upstairs where my main router/WAP is and connect it there to see if it helps. When I experience a drop in access to the unRaid like this, what is the best way to capture the info in the log if the unraid is down to the rest of the network? It seems to be intermittent (if I wait a while and try to remount the share or restart a download that's saving to the share, it will run again for a little bit then be inaccessible again. Like, you click on the shortcut to say, \\unraid\disk4\movies, which was working 5 minutes ago, and it shows it's inaccessible ("do you want to delete this shortcut?" No, I want the unraid to keep alive!) Anyway, when it's out I can't get to \\unraid\flash, and though it usually comes back on it's own, sometimes I need to restart it or even power cycle it. Is the log flushed by then or would it preserve info from when the dropout happened? Can I reverse back to 4.2xxxx versions of the software? What files would I overwrite? Can I preserve my config if I do this? Or does that just seem totally unnecessary, especially since (I believe) I was experiencing this problem even before the upgrade to 4.3 beta 6.
April 14, 200818 yr Author PS- my network setup (physical) is rather convoluted as there are a lot of devices in different locations (seems more and more items need an IP address lately, no!?) So brief overview: Upstairs office: Comcast cable modem/phone ATA for WAN service. Connected to a Belkin pre-N WAP/router (flashed with Linksys firmware which seems much more flexible and stable, as suggested by DSLReports.com forums.) The WAP/router has only four 10/100 wired Ethernet ports (rest of system is gig-E capable), so only one is connected, and outputs the WAN/internet to: wired gig-E 8 port switch, that connects son's PC and a couple of other upstairs devices, with several free wired gig ports available. This is where I'm thinking of moving the unraid tower to check if it makes a difference. This upstairs switch has one run down to the basement to connect to: Basement: Another 10/100/1000 LAN switch connects several wired devices (PS3, 360, HTPC, etc...) This is where the unraid was connected for most of its life. I ran out of ports and needed some items on the other side of the basement, so there is a new run of Cat5E pulled over there and a final 8-port 10/100/1000 switch there, which the unraid is connected to now.
April 14, 200818 yr When I experience a drop in access to the unRaid like this, what is the best way to capture the info in the log if the unraid is down to the rest of the network? The only way to capture the syslog at that point is from the system console. You would log in as "root" and copy the syslog file to the flash drive. Then, you could power down, remove the flash drive and put it in a different PC to read it. It seems to be intermittent (if I wait a while and try to remount the share or restart a download that's saving to the share, it will run again for a little bit then be inaccessible again. Like, you click on the shortcut to say, \\unraid\disk4\movies, which was working 5 minutes ago, and it shows it's inaccessible ("do you want to delete this shortcut?" No, I want the unraid to keep alive!) Anyway, when it's out I can't get to \\unraid\flash, and though it usually comes back on it's own, sometimes I need to restart it or even power cycle it. Is the log flushed by then or would it preserve info from when the dropout happened? The log is written to a file system that exists only in memory. When you reboot, previous contents are gone. Can I reverse back to 4.2xxxx versions of the software? What files would I overwrite? Can I preserve my config if I do this? Or does that just seem totally unnecessary, especially since (I believe) I was experiencing this problem even before the upgrade to 4.3 beta 6. The issues could be release related, but not likely. We will know more whan we can see your syslog. To check for sure, you can revert to the older release... all you need do is replace 2 files on your flash drive. Replace bzroot and bzimage from those from the older 4.2 release of your choice. The rest of your config should stay exactly the same. If you like, you can easily add three lines to the end of the syslinux.cfg file on your flash drive to allow you to boot into either the old or newer versions of unraid. Here is how I have mine set up. I can actually go back two versions (I added two sets of three lines) to do this, all you need do is name the bzroot and bzimage files after the release they represent and have matching names on the menu choices in syslinux.cfg [pre] default menu.c32 menu title Lime Technology LLC prompt 0 timeout 50 label unRAID OS menu default kernel bzimage append initrd=bzroot rootdelay=10 label Memtest86+ kernel memtest label unRaid version4.3b5 kernel bzimage43b5 append initrd=bzroot43b5 rootdelay=10 label unRaid version4.2.3 kernel bzimage423 append initrd=bzroot423 rootdelay=10 [/pre] By default, unRaid will use bzroot and bzimage. My menu will pause a few seconds to allow me to choose either of the prior two releases. If you do this, just unzip Tom's older release and copy the files using names other than bzroot and bzimage. Then reference them using the same two names in the syslinux.cfg. (The actual names you use can be anything, I just name them after the release. They could have just as easily been nameed bzroot_old and bzimage_old ) Joe L.
April 14, 200818 yr "When you say DC error (domain controller), I'm curious whether this is on a business network/domain or whether this is just a home setup." -it's a home setup. I have the unRaid set for workgroup Mshome, as are my two PCs and two Macs. Seems like it might be related though, since my new Leopard MacBook Pro auto-browses available shares on the network when connected, (just one example), and it sometimes shows the unraid tower there and then sometimes it just disappears. Even when I mount a disk from the unraid- it'll stay there for a few, then drop off. Fixed IP address. BTW, I initially changed the name from "tower" to "unraid" in the config page on the web interface as my own preference. When I go to \\unraid\disk1 as a path when mounting network share, or for a UNC file path in programs to locate stored items (such as my movie browser), it works fine. However I've never gotten it to work that way in the web browser. It thinks I'm searching and goes to the lime-technology.com when I type \\unraid\.... (So I have always used \\192.168.100.201\disk1, etc... to get to the web interface.) Anyway, when it seems to lock up I also can't get to the web interface. As far as RobJ's reply, I was thinking something along those lines too, so I moved the tower to a different location on the other side of my basement, connected it to a different ethernet switch with a different cable, and I'm getting the same issue. I will try moving it upstairs where my main router/WAP is and connect it there to see if it helps. When I experience a drop in access to the unRaid like this, what is the best way to capture the info in the log if the unraid is down to the rest of the network? It seems to be intermittent (if I wait a while and try to remount the share or restart a download that's saving to the share, it will run again for a little bit then be inaccessible again. Like, you click on the shortcut to say, \\unraid\disk4\movies, which was working 5 minutes ago, and it shows it's inaccessible ("do you want to delete this shortcut?" No, I want the unraid to keep alive!) Anyway, when it's out I can't get to \\unraid\flash, and though it usually comes back on it's own, sometimes I need to restart it or even power cycle it. Is the log flushed by then or would it preserve info from when the dropout happened? Can I reverse back to 4.2xxxx versions of the software? What files would I overwrite? Can I preserve my config if I do this? Or does that just seem totally unnecessary, especially since (I believe) I was experiencing this problem even before the upgrade to 4.3 beta 6. Well, if you can't get to the actual IP address when it is locked up, I'd second what others are saying and figure there is a network problem or some sort of problem with unraid machine. The only exception I can think of would be if you are attempting to acquire an IP address thru your router's DHCP (I'd suggest trying to manually assign an IP address), or you have conflicting IP addresses on the network (if manually assigned). I've had issues like this before, but since it's on a doman, most of the time it is my server not properly resolving the name, or the tower not pulling a valid IP address. Hopefully you'll find it's something that "easy" and get it worked out without a hassle.
April 14, 200818 yr Author Just recalled that my gigabyte mobo has a feature in the BIOS to test the network. I've never tried it. Not sure if it will work with the new external NIC (I'd highly doubt that) but at least it should work with the mobo NIC for testing. It is supposed to indicate approx. distance of cable run, pairs used, any cabling faults, etc... I wonder if I should check that as well before I let the unraid OS boot up next time? Any other network testing methods you all suggest short of just replacing cables? I think just moving it right next to the main router & connected gig switch and using a short pre-made cable would be the logical next thing to try, and I'll do that tonight. Also, when you all use the unraid disk shares on an XP PC, how do you mount/auto-mount them? Meaning, I use the method map network drive in XP, to map say Z to \\unraid\disk1, Y to \\unraid\disk2, etc... These mapped drive letters become inaccessible when the problems reoccur. Is there another way I should use instead?
April 16, 200818 yr I had similar problems. Everything would boot up fine, shares would mount, and then in the middle of a large transfer I would lose connection. Once I realized that my Promise Ultra 100 ATA card was not the same as the TX2 Promise card and after I subsequently replaced the offending card my problems went away.
April 16, 200818 yr Author Thanks, I'll check that. I do have Promise cards; can't recall which so I'll take a look. I also think I may have a bad network run from one floor to another. I relocated the unRaid directly to the router and was able to transfer a large 40GB file from it to my MacBook Pro without fail. However, the PC that is still connected downstairs (next to where the unRaid used to be) is still having trouble downloading files it's writing to the unRaid ("the specificed network resource is no longer available"; then I remount it, it works for a while again, then drops off again.) So I'm guessing my network run down to the basement might be suspect.
April 17, 200818 yr Physical networkproblems are a pain. If you made the cables yourself, cut off the connectors, and attache new ones, but make a effort to keep the twisting of the cables intact as close as humanly possible to the connector. It is the twisting that minimise noise and crosstalk on the physical cables. If you run the cables close of older electrical applications, consider using Shilded Twisted pair cables. If you know any with a Fluke (or similar), network tester, give them a call. The ones with small clients you attach around the house are brilliant. I had network problems few years ago, but no access to proper testing tools. I got a throughput test program, Qcheck. And tested from from one workstation to a laptop I moved from room to room, it tested over and over again. It was hard work, but I identified som crappy cables and two connectors I had not made well enough. /Rene
April 17, 200818 yr Physical networkproblems are a pain. If you made the cables yourself, cut off the connectors, and attache new ones, but make a effort to keep the twisting of the cables intact as close as humanly possible to the connector. It is the twisting that minimise noise and crosstalk on the physical cables. If you run the cables close of older electrical applications, consider using Shilded Twisted pair cables. Even if the cables pre-made, make sure they are cat-5 cables and not cat-3. At 1000 Mb speeds the older cables are not sufficient for reliable connections. (the wire pairs in the cat-3 cable are not twisted as tightly as those in cat-5, and noise from adjacent conductors causes intermittent errors) If you made the cables yourself, it is critical that the pairs be wired to the correct pins in the connectors. It is possible to accidentally swap two conductors between two of the pairs and end up with good electrical continuity, but horrible performance at 1000 Mb. A simple "cable tester" will not detect this type of poorly constructed cable. It takes one of the very expensive testers to check for that type of problem. Joe L.
April 22, 200818 yr Author Okay, sad to report I still can't solve this. I've moved the computer(s) having trouble staying connected to the unraid during a file transfer, I've remade cables and replaced with pre-made, and I've reconfigured network access on my main PC. Still having the drop outs. I've isolated it down to the unraid now: when I put the unraid connected directly to my router, right next to my PC connected directly to the router, both with new premade cables, I still have the issue. For example, just trying to transfer some files off the unraid to a local disk, I got this error: Cannot copy xxxxxxx.r47: Configuration information could not be read from the domain controller, either becuase the machine is unavailable, or access has been denied. I also get other similar errors and the share disappears for a bit. I tried connecting to the unraid via network places and via mapped network drive- happens either way. Also happens when I try to transfer a file from the unraid to my MacBook Pro, mid transfer the mounted drive disappears and I get a copy error. I've tried the Intel gig NIC instead of the mobo nic. I've not changed any settings in my router, but am game to check it. I have tried connecting to the unraid when mapping the network drive as both my normal logged in PC user name (or guest) OR tried it with "use different name to login" with root, and still get the trouble either way (never knew if I needed to specify login as root from a remote machine when accessing the unraid. Is that the preferred way?) Any suggestions are appreciated. I'll pull the log if the unraid web interface is still running. That doesn't seem to be dropping off lately- just the shared drives themselves when in the middle of a transfer. Interestingly, I use this server to store videos mostly, and playback seems to not have been affected. Not sure why- maybe it's a write only problem, but then again I did have trouble moving files off of the unraid to another disk shared on the network.
April 22, 200818 yr Author Here is a clipping from the end of the syslog. Seems to be some errors to ID and help trace this down here: Apr 19 14:46:08 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:46:08 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:46:08 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:47:38 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:47:38 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:47:38 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:47:50 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:47:50 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:47:50 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:47:50 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:47:50 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:47:50 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:47:56 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:47:56 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:47:56 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:51:22 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:51:22 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:51:22 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:51:22 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:51:22 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 14:51:22 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 14:51:22 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 23:23:15 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 23:23:15 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 23:23:15 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 19 23:35:45 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 19 23:35:45 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 19 23:35:45 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:11:54 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:11:54 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:11:54 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:16 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:16 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:16 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:18 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:18 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:18 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:18 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:18 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:18 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:32 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:32 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:32 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:33 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:33 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:33 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:33 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:33 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:33 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:34 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:34 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:34 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:34 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:34 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:34 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 14:12:34 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 14:12:34 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 14:12:34 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 21:28:08 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 21:28:08 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 21:28:08 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 21:29:59 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 21:29:59 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 21:29:59 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 21:29:59 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 21:29:59 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 20 21:29:59 unraid kernel: ReiserFS: warning: is_leaf: free space seems wrong: level=1, nr_items=16, free_space=65472 rdkey Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-5150: search_by_key: invalid format found in block 62254577. Fsck? Apr 20 21:29:59 unraid kernel: ReiserFS: md2: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 104 0x0 SD] Apr 22 09:23:26 unraid in.telnetd[4003]: connect from 192.168.100.203 (192.168.100.203) By the way, the other error I just got was "The specified network name is no longer available" when it failed trying to copy some files off the unraid
April 22, 200818 yr See this page, and run the test on md2: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems. However, this ReiserFS problem is a new issue, completely unrelated to the network problems.
April 22, 200818 yr Author See this page, and run the test on md2: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems. However, this ReiserFS problem is a new issue, completely unrelated to the network problems. Okay, tried it. Ran the resierfsck and for quite a while, it stayed there, then output some info: Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Apr 22 14:24:11 2008 ########### Replaying journal.. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed Checking internal tree../ 1 (of 5)/ 1 (of 153)/ 8 (of 120)block 62254577: The number of items (16) is incorrect, should be (13) the problem in the internal node occuredfinished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Tue Apr 22 14:34:12 2008 ########### root@unraid:~# Then, it just hung. I couldn't get it to respond. I was going to try --rebuild-tree if you suggested it as the instructions showed, but I didn't get that far. Copied and pasted the telnet data, then I had to reboot. The unraid is gone of course, since I never got back to remounting the drive or samba start. Now there is no prompt at telnet. I power cycled the unraid and still no telnet prompt. I get a putty fatal error: network error-connection timed out. Help- what to do now?
April 22, 200818 yr Author Okay, waited a bit more and got prompt and login on putty. Should I run resierfsck --rebuild-tree /dev/md2
April 22, 200818 yr Author Here is the rest of the syslog prior to all those resierFS errors: Apr 14 20:01:30 unraid syslogd 1.4.1: restart. Apr 14 20:01:30 unraid kernel: klogd 1.4.1, log source = /proc/kmsg started. Apr 14 20:01:30 unraid kernel: Linux version 2.6.24.4-unRAID (root@Develop) (gcc version 4.1.2) #4 Thu Apr 3 01:28:58 MDT 2008 Apr 14 20:01:30 unraid kernel: BIOS-provided physical RAM map: Apr 14 20:01:30 unraid kernel: BIOS-e820: 0000000000000000 - 000000000009e800 (usable) Apr 14 20:01:30 unraid kernel: BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) Apr 14 20:01:30 unraid kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) Apr 14 20:01:30 unraid kernel: BIOS-e820: 0000000000100000 - 000000003f7f0000 (usable) Apr 14 20:01:30 unraid kernel: BIOS-e820: 000000003f7f0000 - 000000003f7f3000 (ACPI NVS) Apr 14 20:01:30 unraid kernel: BIOS-e820: 000000003f7f3000 - 000000003f800000 (ACPI data) Apr 14 20:01:30 unraid kernel: BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved) Apr 14 20:01:30 unraid kernel: BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) Apr 14 20:01:30 unraid kernel: 119MB HIGHMEM available. Apr 14 20:01:30 unraid kernel: 896MB LOWMEM available. Apr 14 20:01:30 unraid kernel: found SMP MP-table at 000f4cd0 Apr 14 20:01:30 unraid kernel: Entering add_active_range(0, 0, 260080) 0 entries of 256 used Apr 14 20:01:30 unraid kernel: Zone PFN ranges: Apr 14 20:01:30 unraid kernel: DMA 0 -> 4096 Apr 14 20:01:30 unraid kernel: Normal 4096 -> 229376 Apr 14 20:01:30 unraid kernel: HighMem 229376 -> 260080 Apr 14 20:01:30 unraid kernel: Movable zone start PFN for each node Apr 14 20:01:30 unraid kernel: early_node_map[1] active PFN ranges Apr 14 20:01:30 unraid kernel: 0: 0 -> 260080 Apr 14 20:01:30 unraid kernel: On node 0 totalpages: 260080 Apr 14 20:01:30 unraid kernel: DMA zone: 32 pages used for memmap Apr 14 20:01:30 unraid kernel: DMA zone: 0 pages reserved Apr 14 20:01:30 unraid kernel: DMA zone: 4064 pages, LIFO batch:0 Apr 14 20:01:30 unraid kernel: Normal zone: 1760 pages used for memmap Apr 14 20:01:30 unraid kernel: Normal zone: 223520 pages, LIFO batch:31 Apr 14 20:01:30 unraid kernel: HighMem zone: 239 pages used for memmap Apr 14 20:01:30 unraid kernel: HighMem zone: 30465 pages, LIFO batch:7 Apr 14 20:01:30 unraid kernel: Movable zone: 0 pages used for memmap Apr 14 20:01:30 unraid kernel: DMI 2.4 present. Apr 14 20:01:30 unraid kernel: ACPI: RSDP 000F6650, 0014 (r0 GBT ) Apr 14 20:01:30 unraid kernel: ACPI: RSDT 3F7F3040, 0034 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) Apr 14 20:01:30 unraid kernel: ACPI: FACP 3F7F30C0, 0074 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) Apr 14 20:01:30 unraid kernel: ACPI: DSDT 3F7F3180, 3AAF (r1 GBT GBTUACPI 1000 MSFT 100000C) Apr 14 20:01:30 unraid kernel: ACPI: FACS 3F7F0000, 0040 Apr 14 20:01:30 unraid kernel: ACPI: HPET 3F7F6D40, 0038 (r1 GBT GBTUACPI 42302E31 GBTU 98) Apr 14 20:01:30 unraid kernel: ACPI: MCFG 3F7F6DC0, 003C (r1 GBT GBTUACPI 42302E31 GBTU 1010101) Apr 14 20:01:30 unraid kernel: ACPI: APIC 3F7F6C80, 0068 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) Apr 14 20:01:30 unraid kernel: ACPI: PM-Timer IO Port: 0x408 Apr 14 20:01:30 unraid kernel: ACPI: Local APIC address 0xfee00000 Apr 14 20:01:30 unraid kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Apr 14 20:01:30 unraid kernel: Processor #0 15:4 APIC version 20 Apr 14 20:01:30 unraid kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled) Apr 14 20:01:30 unraid kernel: ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) Apr 14 20:01:30 unraid kernel: ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) Apr 14 20:01:30 unraid kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) Apr 14 20:01:30 unraid kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 Apr 14 20:01:30 unraid kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Apr 14 20:01:30 unraid kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Apr 14 20:01:30 unraid kernel: ACPI: IRQ0 used by override. Apr 14 20:01:30 unraid kernel: ACPI: IRQ2 used by override. Apr 14 20:01:30 unraid kernel: ACPI: IRQ9 used by override. Apr 14 20:01:30 unraid kernel: Enabling APIC mode: Flat. Using 1 I/O APICs Apr 14 20:01:30 unraid kernel: Using ACPI (MADT) for SMP configuration information Apr 14 20:01:30 unraid kernel: Allocating PCI resources starting at 40000000 (gap: 3f800000:b0800000) Apr 14 20:01:30 unraid kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 258049 Apr 14 20:01:30 unraid kernel: Kernel command line: initrd=bzroot rootdelay=10 BOOT_IMAGE=bzimage Apr 14 20:01:30 unraid kernel: mapped APIC to ffffb000 (fee00000) Apr 14 20:01:30 unraid kernel: mapped IOAPIC to ffffa000 (fec00000) Apr 14 20:01:30 unraid kernel: Enabling fast FPU save and restore... done. Apr 14 20:01:30 unraid kernel: Enabling unmasked SIMD FPU exception support... done. Apr 14 20:01:30 unraid kernel: Initializing CPU#0 Apr 14 20:01:30 unraid kernel: PID hash table entries: 4096 (order: 12, 16384 bytes) Apr 14 20:01:30 unraid kernel: Detected 2813.248 MHz processor. Apr 14 20:01:30 unraid kernel: Console: colour VGA+ 80x25 Apr 14 20:01:30 unraid kernel: console [tty0] enabled Apr 14 20:01:30 unraid kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Apr 14 20:01:30 unraid kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Apr 14 20:01:30 unraid kernel: Memory: 999420k/1040320k available (1973k kernel code, 40228k reserved, 834k data, 176k init, 122816k highmem) Apr 14 20:01:30 unraid kernel: virtual kernel memory layout: Apr 14 20:01:30 unraid kernel: fixmap : 0xfffa8000 - 0xfffff000 ( 348 kB) Apr 14 20:01:30 unraid kernel: pkmap : 0xff800000 - 0xffc00000 (4096 kB) Apr 14 20:01:30 unraid kernel: vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB) Apr 14 20:01:30 unraid kernel: lowmem : 0xc0000000 - 0xf8000000 ( 896 MB) Apr 14 20:01:30 unraid kernel: .init : 0xc03c0000 - 0xc03ec000 ( 176 kB) Apr 14 20:01:30 unraid kernel: .data : 0xc02ed616 - 0xc03bdf5c ( 834 kB) Apr 14 20:01:30 unraid kernel: .text : 0xc0100000 - 0xc02ed616 (1973 kB) Apr 14 20:01:30 unraid kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok. Apr 14 20:01:30 unraid kernel: SLUB: Genslabs=11, HWalign=64, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Apr 14 20:01:30 unraid kernel: Calibrating delay using timer specific routine.. 5639.02 BogoMIPS (lpj=28195112) Apr 14 20:01:30 unraid kernel: Mount-cache hash table entries: 512 Apr 14 20:01:30 unraid kernel: CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000651d 00000000 00000001 00000000 Apr 14 20:01:30 unraid kernel: monitor/mwait feature present. Apr 14 20:01:30 unraid kernel: using mwait in idle threads. Apr 14 20:01:30 unraid kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K Apr 14 20:01:30 unraid kernel: CPU: L2 cache: 256K Apr 14 20:01:30 unraid kernel: CPU: After all inits, caps: bfebfbff 20100000 00000000 0000b180 0000651d 00000000 00000001 00000000 Apr 14 20:01:30 unraid kernel: Intel machine check architecture supported. Apr 14 20:01:30 unraid kernel: Intel machine check reporting enabled on CPU#0. Apr 14 20:01:30 unraid kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (24) available Apr 14 20:01:30 unraid kernel: Compat vDSO mapped to ffffe000. Apr 14 20:01:30 unraid kernel: CPU: Intel(R) Celeron(R) CPU 2.80GHz stepping 09 Apr 14 20:01:30 unraid kernel: Checking 'hlt' instruction... OK. Apr 14 20:01:30 unraid kernel: Freeing SMP alternatives: 0k freed Apr 14 20:01:30 unraid kernel: ACPI: Core revision 20070126 Apr 14 20:01:30 unraid kernel: Parsing all Control Methods: Apr 14 20:01:30 unraid kernel: Table [DSDT](id 0001) - 458 Objects with 58 Devices 151 Methods 21 Regions Apr 14 20:01:30 unraid kernel: tbxface-0598 [00] tb_load_namespace : ACPI Tables successfully acquired Apr 14 20:01:30 unraid kernel: evxfevnt-0091 [00] enable : Transition to ACPI mode successful Apr 14 20:01:30 unraid kernel: ENABLING IO-APIC IRQs Apr 14 20:01:30 unraid kernel: ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 Apr 14 20:01:30 unraid kernel: net_namespace: 64 bytes Apr 14 20:01:30 unraid kernel: NET: Registered protocol family 16 Apr 14 20:01:30 unraid kernel: ACPI: bus type pci registered Apr 14 20:01:30 unraid kernel: PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory Controller Hub without MMCONFIG support. Apr 14 20:01:30 unraid kernel: PCI: PCI BIOS revision 3.00 entry at 0xfab00, last bus=2 Apr 14 20:01:30 unraid kernel: PCI: Using configuration type 1 Apr 14 20:01:30 unraid kernel: Setting up standard PCI resources Apr 14 20:01:30 unraid kernel: evgpeblk-0956 [00] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on int 0x9 Apr 14 20:01:30 unraid kernel: evgpeblk-1052 [00] ev_initialize_gpe_bloc: Found 9 Wake, Enabled 0 Runtime GPEs in this block Apr 14 20:01:30 unraid kernel: ACPI: EC: Look up EC in DSDT Apr 14 20:01:30 unraid kernel: Completing Region/Field/Buffer/Package initialization:....................................................... Apr 14 20:01:30 unraid kernel: Initialized 16/21 Regions 1/1 Fields 16/16 Buffers 22/27 Packages (467 nodes) Apr 14 20:01:30 unraid kernel: Initializing Device/Processor/Thermal objects by executing _INI methods:. Apr 14 20:01:30 unraid kernel: Executed 1 _INI methods requiring 1 _STA executions (examined 62 objects) Apr 14 20:01:30 unraid kernel: ACPI: Interpreter enabled Apr 14 20:01:30 unraid kernel: ACPI: (supports S0 S1 S5) Apr 14 20:01:30 unraid kernel: ACPI: Using IOAPIC for interrupt routing Apr 14 20:01:30 unraid kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Apr 14 20:01:30 unraid kernel: PCI quirk: region 0400-047f claimed by ICH6 ACPI/GPIO/TCO Apr 14 20:01:30 unraid kernel: PCI quirk: region 0480-04bf claimed by ICH6 GPIO Apr 14 20:01:30 unraid kernel: PCI: Transparent bridge - 0000:00:1e.0 Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT] Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT] Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 *12 14 15) Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 9 10 11 12 14 15) Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) Apr 14 20:01:30 unraid kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Apr 14 20:01:30 unraid kernel: pnp: PnP ACPI init Apr 14 20:01:30 unraid kernel: ACPI: bus type pnp registered Apr 14 20:01:30 unraid kernel: pnpacpi: exceeded the max number of mem resources: 12 Apr 14 20:01:30 unraid kernel: pnp: PnP ACPI: found 10 devices Apr 14 20:01:30 unraid kernel: ACPI: ACPI bus type pnp unregistered Apr 14 20:01:30 unraid kernel: SCSI subsystem initialized Apr 14 20:01:30 unraid kernel: usbcore: registered new interface driver usbfs Apr 14 20:01:30 unraid kernel: usbcore: registered new interface driver hub Apr 14 20:01:30 unraid kernel: usbcore: registered new device driver usb Apr 14 20:01:30 unraid kernel: PCI: Using ACPI for IRQ routing Apr 14 20:01:30 unraid kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Apr 14 20:01:30 unraid kernel: Time: tsc clocksource has been installed. Apr 14 20:01:30 unraid kernel: system 00:01: ioport range 0x4d0-0x4d1 has been reserved Apr 14 20:01:30 unraid kernel: system 00:01: ioport range 0x290-0x29f has been reserved Apr 14 20:01:30 unraid kernel: system 00:01: ioport range 0x800-0x87f has been reserved Apr 14 20:01:30 unraid kernel: system 00:01: ioport range 0x290-0x294 has been reserved Apr 14 20:01:30 unraid kernel: system 00:01: ioport range 0x880-0x88f has been reserved Apr 14 20:01:30 unraid kernel: system 00:06: ioport range 0x400-0x4bf could not be reserved Apr 14 20:01:30 unraid kernel: system 00:07: iomem range 0xf0000000-0xf3ffffff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0xd7800-0xd7fff has been reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0xf0000-0xf7fff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0xf8000-0xfbfff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0xfc000-0xfffff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0x3f7f0000-0x3f7fffff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0x0-0x9ffff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0x100000-0x3f7effff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0xfec00000-0xfec00fff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0xfed13000-0xfed1dfff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0xfed20000-0xfed8ffff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0xfee00000-0xfee00fff could not be reserved Apr 14 20:01:30 unraid kernel: system 00:08: iomem range 0xffb00000-0xffb7ffff could not be reserved Apr 14 20:01:30 unraid kernel: PCI: Bridge: 0000:00:1c.0 Apr 14 20:01:30 unraid kernel: IO window: 7000-7fff Apr 14 20:01:30 unraid kernel: MEM window: e0000000-e1ffffff Apr 14 20:01:30 unraid kernel: PREFETCH window: 40000000-400fffff Apr 14 20:01:30 unraid kernel: PCI: Bridge: 0000:00:1e.0 Apr 14 20:01:30 unraid kernel: IO window: 8000-afff Apr 14 20:01:30 unraid kernel: MEM window: e2000000-e3ffffff Apr 14 20:01:30 unraid kernel: PREFETCH window: disabled. Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16 Apr 14 20:01:30 unraid kernel: PCI: Setting latency timer of device 0000:00:1c.0 to 64 Apr 14 20:01:30 unraid kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64 Apr 14 20:01:30 unraid kernel: NET: Registered protocol family 2 Apr 14 20:01:30 unraid kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes) Apr 14 20:01:30 unraid kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes) Apr 14 20:01:30 unraid kernel: TCP bind hash table entries: 65536 (order: 6, 262144 bytes) Apr 14 20:01:30 unraid kernel: TCP: Hash tables configured (established 131072 bind 65536) Apr 14 20:01:30 unraid kernel: TCP reno registered Apr 14 20:01:30 unraid kernel: Unpacking initramfs... done Apr 14 20:01:30 unraid kernel: Freeing initrd memory: 27925k freed Apr 14 20:01:30 unraid kernel: Machine check exception polling timer started. Apr 14 20:01:30 unraid kernel: highmem bounce pool size: 64 pages Apr 14 20:01:30 unraid kernel: Installing knfsd (copyright (C) 1996 [email protected]). Apr 14 20:01:30 unraid kernel: io scheduler noop registered (default) Apr 14 20:01:30 unraid kernel: io scheduler anticipatory registered Apr 14 20:01:30 unraid kernel: io scheduler deadline registered Apr 14 20:01:30 unraid kernel: io scheduler cfq registered Apr 14 20:01:30 unraid kernel: Boot video device is 0000:00:02.0 Apr 14 20:01:30 unraid kernel: PCI: Setting latency timer of device 0000:00:1c.0 to 64 Apr 14 20:01:30 unraid kernel: assign_interrupt_mode Found MSI capability Apr 14 20:01:30 unraid kernel: Allocate Port Service[0000:00:1c.0:pcie00] Apr 14 20:01:30 unraid kernel: Allocate Port Service[0000:00:1c.0:pcie02] Apr 14 20:01:30 unraid kernel: input: Power Button (FF) as /devices/virtual/input/input0 Apr 14 20:01:30 unraid kernel: ACPI: Power Button (FF) [PWRF] Apr 14 20:01:30 unraid kernel: input: Power Button (CM) as /devices/virtual/input/input1 Apr 14 20:01:30 unraid kernel: ACPI: Power Button (CM) [PWRB] Apr 14 20:01:30 unraid kernel: ACPI: Processor [CPU0] (supports 2 throttling states) Apr 14 20:01:30 unraid kernel: Real Time Clock Driver v1.12ac Apr 14 20:01:30 unraid kernel: intel_rng: FWH not detected Apr 14 20:01:30 unraid kernel: Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds). Apr 14 20:01:30 unraid kernel: Hangcheck: Using get_cycles(). Apr 14 20:01:30 unraid kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled Apr 14 20:01:30 unraid kernel: floppy0: no floppy controllers found Apr 14 20:01:30 unraid kernel: loop: module loaded Apr 14 20:01:30 unraid kernel: Driver 'sd' needs updating - please use bus_type methods Apr 14 20:01:30 unraid kernel: ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver Apr 14 20:01:30 unraid kernel: USB Universal Host Controller Interface driver v3.0 Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 17 [\CODE] to be continued...
April 22, 200818 yr Author continued: Apr 14 20:01:30 unraid kernel: PCI: Setting latency timer of device 0000:00:1d.1 to 64 Apr 14 20:01:30 unraid kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller Apr 14 20:01:30 unraid kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 Apr 14 20:01:30 unraid kernel: uhci_hcd 0000:00:1d.1: irq 18, io base 0x0000b400 Apr 14 20:01:30 unraid kernel: usb usb2: configuration #1 chosen from 1 choice Apr 14 20:01:30 unraid kernel: hub 2-0:1.0: USB hub found Apr 14 20:01:30 unraid kernel: hub 2-0:1.0: 2 ports detected Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 19 Apr 14 20:01:30 unraid kernel: PCI: Setting latency timer of device 0000:00:1d.2 to 64 Apr 14 20:01:30 unraid kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller Apr 14 20:01:30 unraid kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 Apr 14 20:01:30 unraid kernel: uhci_hcd 0000:00:1d.2: irq 19, io base 0x0000b800 Apr 14 20:01:30 unraid kernel: usb usb3: configuration #1 chosen from 1 choice Apr 14 20:01:30 unraid kernel: hub 3-0:1.0: USB hub found Apr 14 20:01:30 unraid kernel: hub 3-0:1.0: 2 ports detected Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16 Apr 14 20:01:30 unraid kernel: PCI: Setting latency timer of device 0000:00:1d.3 to 64 Apr 14 20:01:30 unraid kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller Apr 14 20:01:30 unraid kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4 Apr 14 20:01:30 unraid kernel: uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000bc00 Apr 14 20:01:30 unraid kernel: usb usb4: configuration #1 chosen from 1 choice Apr 14 20:01:30 unraid kernel: hub 4-0:1.0: USB hub found Apr 14 20:01:30 unraid kernel: hub 4-0:1.0: 2 ports detected Apr 14 20:01:30 unraid kernel: Initializing USB Mass Storage driver... Apr 14 20:01:30 unraid kernel: usb 4-1: new full speed USB device using uhci_hcd and address 2 Apr 14 20:01:30 unraid kernel: usb 4-1: configuration #1 chosen from 1 choice Apr 14 20:01:30 unraid kernel: scsi0 : SCSI emulation for USB Mass Storage devices Apr 14 20:01:30 unraid kernel: usbcore: registered new interface driver usb-storage Apr 14 20:01:30 unraid kernel: USB Mass Storage support registered. Apr 14 20:01:30 unraid kernel: usb-storage: device found at 2 Apr 14 20:01:30 unraid kernel: usb-storage: waiting for device to settle before scanning Apr 14 20:01:30 unraid kernel: PNP: No PS/2 controller found. Probing ports directly. Apr 14 20:01:30 unraid kernel: Failed to disable AUX port, but continuing anyway... Is this a SiS? Apr 14 20:01:30 unraid kernel: If AUX port is really absent please use the 'i8042.noaux' option. Apr 14 20:01:30 unraid kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Apr 14 20:01:30 unraid kernel: mice: PS/2 mouse device common for all mice Apr 14 20:01:30 unraid kernel: usbcore: registered new interface driver usbhid Apr 14 20:01:30 unraid kernel: drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Apr 14 20:01:30 unraid kernel: TCP cubic registered Apr 14 20:01:30 unraid kernel: NET: Registered protocol family 1 Apr 14 20:01:30 unraid kernel: NET: Registered protocol family 17 Apr 14 20:01:30 unraid kernel: RPC: Registered udp transport module. Apr 14 20:01:30 unraid kernel: RPC: Registered tcp transport module. Apr 14 20:01:30 unraid kernel: Using IPI Shortcut mode Apr 14 20:01:30 unraid kernel: Freeing unused kernel memory: 176k freed Apr 14 20:01:30 unraid kernel: Intel(R) PRO/1000 Network Driver - version 7.6.15.4-NAPI Apr 14 20:01:30 unraid kernel: Copyright (c) 1999-2008 Intel Corporation. Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Apr 14 20:01:30 unraid kernel: PCI: Setting latency timer of device 0000:01:00.0 to 64 Apr 14 20:01:30 unraid kernel: e1000: 0000:01:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 00:15:17:51:7d:fa Apr 14 20:01:30 unraid kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Apr 14 20:01:30 unraid kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Apr 14 20:01:30 unraid kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection Apr 14 20:01:30 unraid kernel: PDC20269: IDE controller (0x105a:0x4d69 rev 0x02) at PCI slot 0000:02:00.0 Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 20 (level, low) -> IRQ 20 Apr 14 20:01:30 unraid kernel: PDC20269: PLL input clock is 16705 kHz Apr 14 20:01:30 unraid kernel: PDC20269: 100%% native mode on irq 20 Apr 14 20:01:30 unraid kernel: ide2: BM-DMA at 0x9000-0x9007, BIOS settings: hde:pio, hdf:pio Apr 14 20:01:30 unraid kernel: ide3: BM-DMA at 0x9008-0x900f, BIOS settings: hdg:pio, hdh:pio Apr 14 20:01:30 unraid kernel: Probing IDE interface ide2... Apr 14 20:01:30 unraid kernel: libata version 3.00 loaded. Apr 14 20:01:30 unraid kernel: hdf: Maxtor 6Y250P0, ATA DISK drive Apr 14 20:01:30 unraid kernel: hdf: host max PIO4 wanted PIO255(auto-tune) selected PIO4 Apr 14 20:01:30 unraid kernel: hdf: UDMA/133 mode selected Apr 14 20:01:30 unraid kernel: ide2 at 0x8000-0x8007,0x8402 on irq 20 Apr 14 20:01:30 unraid kernel: Probing IDE interface ide3... Apr 14 20:01:30 unraid kernel: hdh: Maxtor 6B300R0, ATA DISK drive Apr 14 20:01:30 unraid kernel: hdh: host max PIO4 wanted PIO255(auto-tune) selected PIO4 Apr 14 20:01:30 unraid kernel: hdh: UDMA/133 mode selected Apr 14 20:01:30 unraid kernel: ide3 at 0x8800-0x8807,0x8c02 on irq 20 Apr 14 20:01:30 unraid kernel: PDC20269: IDE controller (0x105a:0x4d69 rev 0x02) at PCI slot 0000:02:01.0 Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 19 (level, low) -> IRQ 18 Apr 14 20:01:30 unraid kernel: PDC20269: PLL input clock is 16716 kHz Apr 14 20:01:30 unraid kernel: PDC20269: 100%% native mode on irq 18 Apr 14 20:01:30 unraid kernel: ide4: BM-DMA at 0xa400-0xa407, BIOS settings: hdi:pio, hdj:pio Apr 14 20:01:30 unraid kernel: ide5: BM-DMA at 0xa408-0xa40f, BIOS settings: hdk:pio, hdl:pio Apr 14 20:01:30 unraid kernel: Probing IDE interface ide4... Apr 14 20:01:30 unraid kernel: Probing IDE interface ide5... Apr 14 20:01:30 unraid kernel: hdk: Maxtor 7Y250P0, ATA DISK drive Apr 14 20:01:30 unraid kernel: hdk: host max PIO4 wanted PIO255(auto-tune) selected PIO4 Apr 14 20:01:30 unraid kernel: hdk: UDMA/133 mode selected Apr 14 20:01:30 unraid kernel: ide5 at 0x9c00-0x9c07,0xa002 on irq 18 Apr 14 20:01:30 unraid kernel: ICH7: IDE controller (0x8086:0x27df rev 0x01) at PCI slot 0000:00:1f.1 Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 19 Apr 14 20:01:30 unraid kernel: ICH7: not 100%% native mode: will probe irqs later Apr 14 20:01:30 unraid kernel: ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio Apr 14 20:01:30 unraid kernel: ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio Apr 14 20:01:30 unraid kernel: Probing IDE interface ide0... Apr 14 20:01:30 unraid kernel: hdf: max request size: 512KiB Apr 14 20:01:30 unraid kernel: hdf: 490234752 sectors (251000 MB) w/7936KiB Cache, CHS=30515/255/63 Apr 14 20:01:30 unraid kernel: hdf: cache flushes supported Apr 14 20:01:30 unraid kernel: hdf: hdf1 Apr 14 20:01:30 unraid kernel: hdh: max request size: 512KiB Apr 14 20:01:30 unraid kernel: hdh: 586114704 sectors (300090 MB) w/16384KiB Cache, CHS=36483/255/63 Apr 14 20:01:30 unraid kernel: hdh: cache flushes supported Apr 14 20:01:30 unraid kernel: hdh: hdh1 Apr 14 20:01:30 unraid kernel: hdk: max request size: 512KiB Apr 14 20:01:30 unraid kernel: hdk: 490234752 sectors (251000 MB) w/7936KiB Cache, CHS=30515/255/63 Apr 14 20:01:30 unraid kernel: hdk: cache flushes supported Apr 14 20:01:30 unraid kernel: hdk: hdk1 Apr 14 20:01:30 unraid kernel: scsi 0:0:0:0: Direct-Access Sony Storage Media 0100 PQ: 0 ANSI: 0 CCS Apr 14 20:01:30 unraid kernel: sd 0:0:0:0: [sda] 1014784 512-byte hardware sectors (520 MB) Apr 14 20:01:30 unraid kernel: sd 0:0:0:0: [sda] Write Protect is off Apr 14 20:01:30 unraid kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 Apr 14 20:01:30 unraid kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Apr 14 20:01:30 unraid kernel: sd 0:0:0:0: [sda] 1014784 512-byte hardware sectors (520 MB) Apr 14 20:01:30 unraid kernel: sd 0:0:0:0: [sda] Write Protect is off Apr 14 20:01:30 unraid kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 Apr 14 20:01:30 unraid kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Apr 14 20:01:30 unraid kernel: sda: sda1 Apr 14 20:01:30 unraid kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Apr 14 20:01:30 unraid kernel: usb-storage: device scan complete Apr 14 20:01:30 unraid kernel: hda: MAXTOR STM3500630A, ATA DISK drive Apr 14 20:01:30 unraid kernel: hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 Apr 14 20:01:30 unraid kernel: hda: UDMA/100 mode selected Apr 14 20:01:30 unraid kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Apr 14 20:01:30 unraid kernel: hda: max request size: 512KiB Apr 14 20:01:30 unraid kernel: hda: Host Protected Area detected. Apr 14 20:01:30 unraid kernel: ^Icurrent capacity is 976771055 sectors (500106 MB) Apr 14 20:01:30 unraid kernel: ^Inative capacity is 976773168 sectors (500107 MB) Apr 14 20:01:30 unraid kernel: hda: Host Protected Area disabled. Apr 14 20:01:30 unraid kernel: hda: 976773168 sectors (500107 MB) w/16384KiB Cache, CHS=60801/255/63 Apr 14 20:01:30 unraid kernel: hda: cache flushes supported Apr 14 20:01:30 unraid kernel: hda: hda1 Apr 14 20:01:30 unraid kernel: Probing IDE interface ide1... Apr 14 20:01:30 unraid kernel: ata_piix 0000:00:1f.2: version 2.12 Apr 14 20:01:30 unraid kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] Apr 14 20:01:30 unraid kernel: ACPI: PCI Interrupt 0000:00:1f.2[b] -> GSI 19 (level, low) -> IRQ 18 Apr 14 20:01:30 unraid kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64 Apr 14 20:01:30 unraid kernel: scsi1 : ata_piix Apr 14 20:01:30 unraid kernel: scsi2 : ata_piix Apr 14 20:01:30 unraid kernel: ata1: SATA max UDMA/133 cmd 0xd400 ctl 0xd800 bmdma 0xe400 irq 18 Apr 14 20:01:30 unraid kernel: ata2: SATA max UDMA/133 cmd 0xdc00 ctl 0xe000 bmdma 0xe408 irq 18 Apr 14 20:01:30 unraid kernel: ata1.00: HPA detected: current 976771055, native 976773168 Apr 14 20:01:30 unraid kernel: ata1.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7 Apr 14 20:01:30 unraid kernel: ata1.00: 976771055 sectors, multi 16: LBA48 NCQ (depth 0/32) Apr 14 20:01:30 unraid kernel: ata1.01: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7 Apr 14 20:01:30 unraid kernel: ata1.01: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) Apr 14 20:01:30 unraid kernel: ata1.00: configured for UDMA/133 Apr 14 20:01:30 unraid kernel: ata1.01: configured for UDMA/133 Apr 14 20:01:30 unraid kernel: ata2.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 Apr 14 20:01:30 unraid kernel: ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) Apr 14 20:01:30 unraid kernel: ata2.00: configured for UDMA/133 Apr 14 20:01:30 unraid kernel: scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5 Apr 14 20:01:30 unraid kernel: sd 1:0:0:0: [sdb] 976771055 512-byte hardware sectors (500107 MB) Apr 14 20:01:30 unraid kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 14 20:01:30 unraid kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 14 20:01:30 unraid kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 14 20:01:30 unraid kernel: sd 1:0:0:0: [sdb] 976771055 512-byte hardware sectors (500107 MB) Apr 14 20:01:30 unraid kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 14 20:01:30 unraid kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 14 20:01:30 unraid kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 14 20:01:30 unraid kernel: sdb: sdb1 Apr 14 20:01:30 unraid kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Apr 14 20:01:30 unraid kernel: scsi 1:0:1:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5 Apr 14 20:01:30 unraid kernel: sd 1:0:1:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) Apr 14 20:01:30 unraid kernel: sd 1:0:1:0: [sdc] Write Protect is off Apr 14 20:01:30 unraid kernel: sd 1:0:1:0: [sdc] Mode Sense: 00 3a 00 00 Apr 14 20:01:30 unraid kernel: sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 14 20:01:30 unraid kernel: sd 1:0:1:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) Apr 14 20:01:30 unraid kernel: sd 1:0:1:0: [sdc] Write Protect is off Apr 14 20:01:30 unraid kernel: sd 1:0:1:0: [sdc] Mode Sense: 00 3a 00 00 Apr 14 20:01:30 unraid kernel: sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 14 20:01:30 unraid kernel: sdc: sdc1 Apr 14 20:01:30 unraid kernel: sd 1:0:1:0: [sdc] Attached SCSI disk Apr 14 20:01:30 unraid kernel: scsi 2:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 Apr 14 20:01:30 unraid kernel: sd 2:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) Apr 14 20:01:30 unraid kernel: sd 2:0:0:0: [sdd] Write Protect is off Apr 14 20:01:30 unraid kernel: sd 2:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Apr 14 20:01:30 unraid kernel: sd 2:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 14 20:01:30 unraid kernel: sd 2:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) Apr 14 20:01:30 unraid kernel: sd 2:0:0:0: [sdd] Write Protect is off Apr 14 20:01:30 unraid kernel: sd 2:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Apr 14 20:01:30 unraid kernel: sd 2:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 14 20:01:30 unraid kernel: sdd: sdd1 Apr 14 20:01:30 unraid kernel: sd 2:0:0:0: [sdd] Attached SCSI disk Apr 14 20:01:31 unraid logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Apr 14 20:01:32 unraid logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Apr 14 20:01:32 unraid logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.100.201 broadcast 192.168.100.255 netmask 255.255.255.0 Apr 14 20:01:32 unraid logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.100.1 metric 1 Apr 14 20:01:32 unraid ifplugd(eth0)[1452]: ifplugd 0.28 initializing. Apr 14 20:01:32 unraid ifplugd(eth0)[1452]: Using interface eth0/00:15:17:51:7D:FA with driver <e1000> (version: 7.6.15.4-NAPI) Apr 14 20:01:32 unraid ifplugd(eth0)[1452]: Using detection mode: SIOCETHTOOL Apr 14 20:01:32 unraid ifplugd(eth0)[1452]: Initialization complete, link beat not detected. Apr 14 20:01:32 unraid kernel: fuse init (API version 7.9) Apr 14 20:01:33 unraid emhttp: unRAID System Management Utility version 4.3-beta6 Apr 14 20:01:33 unraid emhttp: Copyright (C) 2005-2008, Lime Technology, LLC Apr 14 20:01:33 unraid emhttp: Pro key detected, registered to: Mike Morbeto Apr 14 20:01:33 unraid emhttp: Device inventory: Apr 14 20:01:33 unraid emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 (sdc) ata-SAMSUNG_HD501LJ_S0MUJ1DP301846 Apr 14 20:01:33 unraid emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 (sdd) ata-ST3500630AS_9QG41ZM2 Apr 14 20:01:33 unraid emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 (sdb) ata-SAMSUNG_HD501LJ_S0MUJ1DP301847 Apr 14 20:01:33 unraid emhttp: pci-0000:00:1f.1-ide-0:0 (hda) ata-MAXTOR_STM3500630A_5QG06KKG Apr 14 20:01:33 unraid emhttp: pci-0000:02:01.0-ide-0:0 (hdk) ata-Maxtor_7Y250P0_Y62B2DJE Apr 14 20:01:33 unraid emhttp: pci-0000:02:00.0-ide-1:1 (hdh) ata-Maxtor_6B300R0_B60EQK0H Apr 14 20:01:33 unraid emhttp: pci-0000:02:00.0-ide-0:1 (hdf) ata-Maxtor_6Y250P0_Y62HYJZE Apr 14 20:01:33 unraid emhttp: shcmd (1): rmmod md-mod >>/var/log/go 2>&1 Apr 14 20:01:33 unraid emhttp: shcmd: shcmd (1): exit status: 1 Apr 14 20:01:33 unraid emhttp: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=8,32,3,0,8,16,33,64,34,64,8,48,57,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1 Apr 14 20:01:33 unraid kernel: md: unRAID driver 0.94.0 installed Apr 14 20:01:33 unraid kernel: md: xor using function: pIII_sse (1214.400 MB/sec) Apr 14 20:01:33 unraid emhttp: shcmd (3): /usr/sbin/hdparm -S242 /dev/sdc >/dev/null Apr 14 20:01:33 unraid emhttp: shcmd (4): /usr/sbin/hdparm -S242 /dev/hda >/dev/null Apr 14 20:01:33 unraid emhttp: shcmd (5): /usr/sbin/hdparm -S242 /dev/sdb >/dev/null Apr 14 20:01:33 unraid kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX Apr 14 20:01:33 unraid kernel: e1000: eth0: e1000_watchdog_task: 10/100 speed: disabling TSO Apr 14 20:01:33 unraid emhttp: shcmd (6): /usr/sbin/hdparm -S242 /dev/hdf >/dev/null Apr 14 20:01:33 unraid ifplugd(eth0)[1452]: Link beat detected. Apr 14 20:01:33 unraid emhttp: shcmd (7): /usr/sbin/hdparm -S242 /dev/hdh >/dev/null Apr 14 20:01:34 unraid emhttp: shcmd (: /usr/sbin/hdparm -S242 /dev/sdd >/dev/null Apr 14 20:01:34 unraid emhttp: shcmd (9): /usr/sbin/hdparm -S242 /dev/hdk >/dev/null Apr 14 20:01:34 unraid emhttp: shcmd (10): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Apr 14 20:01:34 unraid emhttp: shcmd (11): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Apr 14 20:01:34 unraid emhttp: shcmd (12): echo '40 3 * * * /usr/local/sbin/mover | logger 2>&1' >>/var/spool/cron/crontabs/root Apr 14 20:01:34 unraid emhttp: shcmd (13): crontab /var/spool/cron/crontabs/root Apr 14 20:01:34 unraid emhttp: shcmd (14): killall -w smbd nmbd Apr 14 20:01:35 unraid ifplugd(eth0)[1452]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Apr 14 20:01:35 unraid ifplugd(eth0)[1452]: Program executed successfully. Apr 14 20:01:35 unraid emhttp: shcmd (15): /usr/sbin/nmbd -D Apr 14 20:01:35 unraid emhttp: shcmd (16): /usr/sbin/smbd -D Apr 14 20:01:35 unraid kernel: mdcmd (3): start Apr 14 20:01:35 unraid kernel: unraid: allocated 15222kB Apr 14 20:01:35 unraid kernel: md1: running, size: 488386552 blocks Apr 14 20:01:35 unraid kernel: md2: running, size: 488385496 blocks Apr 14 20:01:35 unraid kernel: md3: running, size: 245117344 blocks Apr 14 20:01:35 unraid kernel: md4: running, size: 293057320 blocks Apr 14 20:01:35 unraid kernel: md5: running, size: 488386552 blocks Apr 14 20:01:35 unraid kernel: md6: running, size: 245117344 blocks Apr 14 20:01:35 unraid kernel: mdcmd (5): check Apr 14 20:01:35 unraid kernel: md: recovery thread got woken up ... Apr 14 20:01:35 unraid emhttp: shcmd (17): udevsettle Apr 14 20:01:35 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk1 Apr 14 20:01:35 unraid kernel: md: recovery thread has nothing to resync Apr 14 20:01:35 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk2 Apr 14 20:01:35 unraid emhttp: shcmd (19): mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 >/dev/null 2>&1 Apr 14 20:01:36 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk3 Apr 14 20:01:36 unraid emhttp: shcmd (19): mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 >/dev/null 2>&1 Apr 14 20:01:36 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk4 Apr 14 20:01:36 unraid emhttp: shcmd (19): mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3 >/dev/null 2>&1 Apr 14 20:01:36 unraid emhttp: shcmd (18): mkdir -m 700 /mnt/disk5
April 22, 200818 yr Yes, re-run reiserfsck on that drive with the --rebuild-tree parameter: reiserfsck -y --rebuild-tree /dev/md2. The -y skips the Yes confirmation. The network appears to be an Intel Pro1000 PCI Express gigabit card. It did not connect immediately, but did a little later at 100Mbps speed, not gigabit. No errors appeared, just slow connecting and at a slow speed. This is weird, saw my very first HPA message this morning, and now here is another, actually 2 in your case. These don't seem particularly important, but should be noted. Disk 1 (hda) apparently has an HPA (Host Protected Area), but it was disabled, so no loss of disk space. Disk 2 (sdb) has an HPA, costing you the use of a little over a megabyte of disk space, not much but interesting. I did some searching of syslogs, and found only the 2 HPA's found today on SATA drives, but 5 or 6 users have them on IDE drives. The IDE setup driver calls it Host Protected Area, whereas the SATA driver calls it HPA, but it is the same thing. They have all been exactly 2113 sectors, which is 1056 unRAID blocks. I have no idea what the significance of these are, or why they are there, or what process has put them there. Supposedly, an HPA is for securing or hiding information.
April 23, 200818 yr Usually they contain restore info partitions as used on Compaq, HP, and other OEM computers...
April 23, 200818 yr Author Yes, re-run reiserfsck on that drive with the --rebuild-tree parameter: reiserfsck -y --rebuild-tree /dev/md2. The -y skips the Yes confirmation. The network appears to be an Intel Pro1000 PCI Express gigabit card. It did not connect immediately, but did a little later at 100Mbps speed, not gigabit. No errors appeared, just slow connecting and at a slow speed. This is weird, saw my very first HPA message this morning, and now here is another, actually 2 in your case. These don't seem particularly important, but should be noted. Disk 1 (hda) apparently has an HPA (Host Protected Area), but it was disabled, so no loss of disk space. Disk 2 (sdb) has an HPA, costing you the use of a little over a megabyte of disk space, not much but interesting. I did some searching of syslogs, and found only the 2 HPA's found today on SATA drives, but 5 or 6 users have them on IDE drives. The IDE setup driver calls it Host Protected Area, whereas the SATA driver calls it HPA, but it is the same thing. They have all been exactly 2113 sectors, which is 1056 unRAID blocks. I have no idea what the significance of these are, or why they are there, or what process has put them there. Supposedly, an HPA is for securing or hiding information. Okay, ran the reiserfsck --rebuild-tree last night. Took quite a while to run but I let it rip while I was sleeping. Here is the info: Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal.. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Tue Apr 22 19:17:48 2008 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 114931476 blocks marked used Skipping 11937 blocks (super block, journal, bitmaps) 114919539 blocks will be read 0%...block 16011091: The number of items (29712) is incorrect, should be (1) - corrected block 16011091: The free space (63246) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 16011091, item (0): Unknown item type found [26221698 242491392 0xc3f7 (15)] - deleted .block 23138524: The number of items (29712) is incorrect, should be (1) - corrected block 23138524: The free space (63246) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 23138524, item (0): Unknown item type found [26221698 242491392 0xc3f7 (15)] - deleted 20%....block 62254577: The number of items (16) is incorrect, should be (13) - corrected block 62254577: The free space (65472) is incorrect, should be (116) - corrected left 0, 6208 /seccseccccc 27025 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 114919539 Leaves among those 117935 - leaves all contents of which could not be saved and deleted 2 Objectids found 27027 Pass 1 (will try to insert 117933 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 225 /sec Flushing..finished 117933 leaves read 117845 inserted 88 not inserted ####### Pass 2 ####### ####### Pass 2 ####### Pass 2: 0%....20%....40%....60%....80%....100% left 0, 176 /sec Flushing..finished Leaves inserted item by item 88 Pass 3 (semantic): ####### Pass 3 ######### /Movies, Shows and DVDs/Cars??[DVD]_??_i_United??States_??2006__i_/VIDEO_TSrebuild_semantic_pass: The entry [2 110] ("VTS_01_0.BUP") in directory [2 105] points to nowhere - is removed /Movies, Shows and DVDs/Cars??[DVD]_??_i_United??States_??2006__i_/VIDEO_TSrebuild_semantic_pass: The entry [2 111] ("VTS_01_0.IFO") in directory [2 105] points to nowhere - is removed /Movies, Shows and DVDs/Cars??[DVD]_??_i_United??States_??2006__i_/VIDEO_TSvpf-10650: The directory [2 105] has the wrong size in the StatData (1824) - corrected to (1728) /mymoviesFlushing..finished Files found: 24510 Directories found: 2515 Names pointing to nowhere (removed): 2 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Flushing..finished1, 218 /sec Pass 4 - finisheddone 116801, 269 /sec Deleted unreachable items 1 Flushing..finished Syncing..finished ########### reiserfsck finished at Wed Apr 23 00:46:14 2008 ########### root@unraid:~# As far as the network problems, I suspect as you pointed out these are two unrelated issues so I'm still looking for help tracking down the network drops. As far as connecting the Intel gig card at 100MB, that's 'cause I moved the unraid at one point to directly connect to my router/WAP, which has built-in 100B-T ports. I usually keep it connected to a switch that's Gig-E, but I was trying to eliminate cables and components in the chain to help troubleshoot any physical network issues, but this seems unrelated to cabling since it persisted even when the PC and the unraid were both directly connected to the router with new cables.... Now I've got it back connected as before (when it used to work) at gig-E but of course the network dropouts continue on the unraid. The PC seems stable (except when trying to write to the unraid or move files from it.) My other machines are also having trouble accessing only the unraid. I'll dump a new log in a few minutes and repost, but for example, just this morning checking the telnet session to get the samba back started after reiserfsck finished, I'm getting puTTY fatal error: Network Error: Software caused connection abort
April 23, 200818 yr Author Still getting these dropouts every 10 minutes or so making it impossible to use the unraid to write larger files. Here is the current syslog (I did a reboot after the reiserfsck finished, and unfortunaltly the problem is still there.) Part 1: Apr 23 08:40:02 unraid syslogd 1.4.1: restart. Apr 23 08:40:02 unraid kernel: klogd 1.4.1, log source = /proc/kmsg started. Apr 23 08:40:02 unraid kernel: Linux version 2.6.24.4-unRAID (root@Develop) (gcc version 4.1.2) #4 Thu Apr 3 01:28:58 MDT 2008 Apr 23 08:40:02 unraid kernel: BIOS-provided physical RAM map: Apr 23 08:40:02 unraid kernel: BIOS-e820: 0000000000000000 - 000000000009e800 (usable) Apr 23 08:40:02 unraid kernel: BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) Apr 23 08:40:02 unraid kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) Apr 23 08:40:02 unraid kernel: BIOS-e820: 0000000000100000 - 000000003f7f0000 (usable) Apr 23 08:40:02 unraid kernel: BIOS-e820: 000000003f7f0000 - 000000003f7f3000 (ACPI NVS) Apr 23 08:40:02 unraid kernel: BIOS-e820: 000000003f7f3000 - 000000003f800000 (ACPI data) Apr 23 08:40:02 unraid kernel: BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved) Apr 23 08:40:02 unraid kernel: BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) Apr 23 08:40:02 unraid kernel: 119MB HIGHMEM available. Apr 23 08:40:02 unraid kernel: 896MB LOWMEM available. Apr 23 08:40:02 unraid kernel: found SMP MP-table at 000f4cd0 Apr 23 08:40:02 unraid kernel: Entering add_active_range(0, 0, 260080) 0 entries of 256 used Apr 23 08:40:02 unraid kernel: Zone PFN ranges: Apr 23 08:40:02 unraid kernel: DMA 0 -> 4096 Apr 23 08:40:02 unraid kernel: Normal 4096 -> 229376 Apr 23 08:40:02 unraid kernel: HighMem 229376 -> 260080 Apr 23 08:40:02 unraid kernel: Movable zone start PFN for each node Apr 23 08:40:02 unraid kernel: early_node_map[1] active PFN ranges Apr 23 08:40:02 unraid kernel: 0: 0 -> 260080 Apr 23 08:40:02 unraid kernel: On node 0 totalpages: 260080 Apr 23 08:40:02 unraid kernel: DMA zone: 32 pages used for memmap Apr 23 08:40:02 unraid kernel: DMA zone: 0 pages reserved Apr 23 08:40:02 unraid kernel: DMA zone: 4064 pages, LIFO batch:0 Apr 23 08:40:02 unraid kernel: Normal zone: 1760 pages used for memmap Apr 23 08:40:02 unraid kernel: Normal zone: 223520 pages, LIFO batch:31 Apr 23 08:40:02 unraid kernel: HighMem zone: 239 pages used for memmap Apr 23 08:40:02 unraid kernel: HighMem zone: 30465 pages, LIFO batch:7 Apr 23 08:40:02 unraid kernel: Movable zone: 0 pages used for memmap Apr 23 08:40:02 unraid kernel: DMI 2.4 present. Apr 23 08:40:02 unraid kernel: ACPI: RSDP 000F6650, 0014 (r0 GBT ) Apr 23 08:40:02 unraid kernel: ACPI: RSDT 3F7F3040, 0034 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) Apr 23 08:40:02 unraid kernel: ACPI: FACP 3F7F30C0, 0074 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) Apr 23 08:40:02 unraid kernel: ACPI: DSDT 3F7F3180, 3AAF (r1 GBT GBTUACPI 1000 MSFT 100000C) Apr 23 08:40:02 unraid kernel: ACPI: FACS 3F7F0000, 0040 Apr 23 08:40:02 unraid kernel: ACPI: HPET 3F7F6D40, 0038 (r1 GBT GBTUACPI 42302E31 GBTU 98) Apr 23 08:40:02 unraid kernel: ACPI: MCFG 3F7F6DC0, 003C (r1 GBT GBTUACPI 42302E31 GBTU 1010101) Apr 23 08:40:02 unraid kernel: ACPI: APIC 3F7F6C80, 0068 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) Apr 23 08:40:02 unraid kernel: ACPI: PM-Timer IO Port: 0x408 Apr 23 08:40:02 unraid kernel: ACPI: Local APIC address 0xfee00000 Apr 23 08:40:02 unraid kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Apr 23 08:40:02 unraid kernel: Processor #0 15:4 APIC version 20 Apr 23 08:40:02 unraid kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled) Apr 23 08:40:02 unraid kernel: ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) Apr 23 08:40:02 unraid kernel: ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) Apr 23 08:40:02 unraid kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) Apr 23 08:40:02 unraid kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 Apr 23 08:40:02 unraid kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Apr 23 08:40:02 unraid kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Apr 23 08:40:02 unraid kernel: ACPI: IRQ0 used by override. Apr 23 08:40:02 unraid kernel: ACPI: IRQ2 used by override. Apr 23 08:40:02 unraid kernel: ACPI: IRQ9 used by override. Apr 23 08:40:02 unraid kernel: Enabling APIC mode: Flat. Using 1 I/O APICs Apr 23 08:40:02 unraid kernel: Using ACPI (MADT) for SMP configuration information Apr 23 08:40:02 unraid kernel: Allocating PCI resources starting at 40000000 (gap: 3f800000:b0800000) Apr 23 08:40:02 unraid kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 258049 Apr 23 08:40:02 unraid kernel: Kernel command line: initrd=bzroot rootdelay=10 BOOT_IMAGE=bzimage Apr 23 08:40:02 unraid kernel: mapped APIC to ffffb000 (fee00000) Apr 23 08:40:02 unraid kernel: mapped IOAPIC to ffffa000 (fec00000) Apr 23 08:40:02 unraid kernel: Enabling fast FPU save and restore... done. Apr 23 08:40:02 unraid kernel: Enabling unmasked SIMD FPU exception support... done. Apr 23 08:40:02 unraid kernel: Initializing CPU#0 Apr 23 08:40:02 unraid kernel: PID hash table entries: 4096 (order: 12, 16384 bytes) Apr 23 08:40:02 unraid kernel: Detected 2813.561 MHz processor. Apr 23 08:40:02 unraid kernel: Console: colour VGA+ 80x25 Apr 23 08:40:02 unraid kernel: console [tty0] enabled Apr 23 08:40:02 unraid kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Apr 23 08:40:02 unraid kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Apr 23 08:40:02 unraid kernel: Memory: 999420k/1040320k available (1973k kernel code, 40228k reserved, 834k data, 176k init, 122816k highmem) Apr 23 08:40:02 unraid kernel: virtual kernel memory layout: Apr 23 08:40:02 unraid kernel: fixmap : 0xfffa8000 - 0xfffff000 ( 348 kB) Apr 23 08:40:02 unraid kernel: pkmap : 0xff800000 - 0xffc00000 (4096 kB) Apr 23 08:40:02 unraid kernel: vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB) Apr 23 08:40:02 unraid kernel: lowmem : 0xc0000000 - 0xf8000000 ( 896 MB) Apr 23 08:40:02 unraid kernel: .init : 0xc03c0000 - 0xc03ec000 ( 176 kB) Apr 23 08:40:02 unraid kernel: .data : 0xc02ed616 - 0xc03bdf5c ( 834 kB) Apr 23 08:40:02 unraid kernel: .text : 0xc0100000 - 0xc02ed616 (1973 kB) Apr 23 08:40:02 unraid kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok. Apr 23 08:40:02 unraid kernel: SLUB: Genslabs=11, HWalign=64, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Apr 23 08:40:02 unraid kernel: Calibrating delay using timer specific routine.. 5639.83 BogoMIPS (lpj=28199159) Apr 23 08:40:02 unraid kernel: Mount-cache hash table entries: 512 Apr 23 08:40:02 unraid kernel: CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000651d 00000000 00000001 00000000 Apr 23 08:40:02 unraid kernel: monitor/mwait feature present. Apr 23 08:40:02 unraid kernel: using mwait in idle threads. Apr 23 08:40:02 unraid kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K Apr 23 08:40:02 unraid kernel: CPU: L2 cache: 256K Apr 23 08:40:02 unraid kernel: CPU: After all inits, caps: bfebfbff 20100000 00000000 0000b180 0000651d 00000000 00000001 00000000 Apr 23 08:40:02 unraid kernel: Intel machine check architecture supported. Apr 23 08:40:02 unraid kernel: Intel machine check reporting enabled on CPU#0. Apr 23 08:40:02 unraid kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (24) available Apr 23 08:40:02 unraid kernel: Compat vDSO mapped to ffffe000. Apr 23 08:40:02 unraid kernel: CPU: Intel(R) Celeron(R) CPU 2.80GHz stepping 09 Apr 23 08:40:02 unraid kernel: Checking 'hlt' instruction... OK. Apr 23 08:40:02 unraid kernel: Freeing SMP alternatives: 0k freed Apr 23 08:40:02 unraid kernel: ACPI: Core revision 20070126 Apr 23 08:40:02 unraid kernel: Parsing all Control Methods: Apr 23 08:40:02 unraid kernel: Table [DSDT](id 0001) - 458 Objects with 58 Devices 151 Methods 21 Regions Apr 23 08:40:02 unraid kernel: tbxface-0598 [00] tb_load_namespace : ACPI Tables successfully acquired Apr 23 08:40:02 unraid kernel: evxfevnt-0091 [00] enable : Transition to ACPI mode successful Apr 23 08:40:02 unraid kernel: ENABLING IO-APIC IRQs Apr 23 08:40:02 unraid kernel: ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 Apr 23 08:40:02 unraid kernel: net_namespace: 64 bytes Apr 23 08:40:02 unraid kernel: NET: Registered protocol family 16 Apr 23 08:40:02 unraid kernel: ACPI: bus type pci registered Apr 23 08:40:02 unraid kernel: PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory Controller Hub without MMCONFIG support. Apr 23 08:40:02 unraid kernel: PCI: PCI BIOS revision 3.00 entry at 0xfab00, last bus=2 Apr 23 08:40:02 unraid kernel: PCI: Using configuration type 1 Apr 23 08:40:02 unraid kernel: Setting up standard PCI resources Apr 23 08:40:02 unraid kernel: evgpeblk-0956 [00] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on int 0x9 Apr 23 08:40:02 unraid kernel: evgpeblk-1052 [00] ev_initialize_gpe_bloc: Found 9 Wake, Enabled 0 Runtime GPEs in this block Apr 23 08:40:02 unraid kernel: ACPI: EC: Look up EC in DSDT Apr 23 08:40:02 unraid kernel: Completing Region/Field/Buffer/Package initialization:....................................................... Apr 23 08:40:02 unraid kernel: Initialized 16/21 Regions 1/1 Fields 16/16 Buffers 22/27 Packages (467 nodes) Apr 23 08:40:02 unraid kernel: Initializing Device/Processor/Thermal objects by executing _INI methods:. Apr 23 08:40:02 unraid kernel: Executed 1 _INI methods requiring 1 _STA executions (examined 62 objects) Apr 23 08:40:02 unraid kernel: ACPI: Interpreter enabled Apr 23 08:40:02 unraid kernel: ACPI: (supports S0 S1 S5) Apr 23 08:40:02 unraid kernel: ACPI: Using IOAPIC for interrupt routing Apr 23 08:40:02 unraid kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Apr 23 08:40:02 unraid kernel: PCI quirk: region 0400-047f claimed by ICH6 ACPI/GPIO/TCO Apr 23 08:40:02 unraid kernel: PCI quirk: region 0480-04bf claimed by ICH6 GPIO Apr 23 08:40:02 unraid kernel: PCI: Transparent bridge - 0000:00:1e.0 Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT] Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT] Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 *12 14 15) Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 9 10 11 12 14 15) Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) Apr 23 08:40:02 unraid kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Apr 23 08:40:02 unraid kernel: pnp: PnP ACPI init Apr 23 08:40:02 unraid kernel: ACPI: bus type pnp registered Apr 23 08:40:02 unraid kernel: pnpacpi: exceeded the max number of mem resources: 12 Apr 23 08:40:02 unraid kernel: pnp: PnP ACPI: found 10 devices Apr 23 08:40:02 unraid kernel: ACPI: ACPI bus type pnp unregistered Apr 23 08:40:02 unraid kernel: SCSI subsystem initialized Apr 23 08:40:02 unraid kernel: usbcore: registered new interface driver usbfs Apr 23 08:40:02 unraid kernel: usbcore: registered new interface driver hub Apr 23 08:40:02 unraid kernel: usbcore: registered new device driver usb Apr 23 08:40:02 unraid kernel: PCI: Using ACPI for IRQ routing Apr 23 08:40:02 unraid kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Apr 23 08:40:02 unraid kernel: Time: tsc clocksource has been installed. Apr 23 08:40:02 unraid kernel: system 00:01: ioport range 0x4d0-0x4d1 has been reserved Apr 23 08:40:02 unraid kernel: system 00:01: ioport range 0x290-0x29f has been reserved Apr 23 08:40:02 unraid kernel: system 00:01: ioport range 0x800-0x87f has been reserved Apr 23 08:40:02 unraid kernel: system 00:01: ioport range 0x290-0x294 has been reserved Apr 23 08:40:02 unraid kernel: system 00:01: ioport range 0x880-0x88f has been reserved Apr 23 08:40:02 unraid kernel: system 00:06: ioport range 0x400-0x4bf could not be reserved Apr 23 08:40:02 unraid kernel: system 00:07: iomem range 0xf0000000-0xf3ffffff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0xd7800-0xd7fff has been reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0xf0000-0xf7fff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0xf8000-0xfbfff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0xfc000-0xfffff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0x3f7f0000-0x3f7fffff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0x0-0x9ffff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0x100000-0x3f7effff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0xfec00000-0xfec00fff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0xfed13000-0xfed1dfff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0xfed20000-0xfed8ffff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0xfee00000-0xfee00fff could not be reserved Apr 23 08:40:02 unraid kernel: system 00:08: iomem range 0xffb00000-0xffb7ffff could not be reserved Apr 23 08:40:02 unraid kernel: PCI: Bridge: 0000:00:1c.0 Apr 23 08:40:02 unraid kernel: IO window: 7000-7fff Apr 23 08:40:02 unraid kernel: MEM window: e0000000-e1ffffff Apr 23 08:40:02 unraid kernel: PREFETCH window: 40000000-400fffff Apr 23 08:40:02 unraid kernel: PCI: Bridge: 0000:00:1e.0 Apr 23 08:40:02 unraid kernel: IO window: 8000-afff Apr 23 08:40:02 unraid kernel: MEM window: e2000000-e3ffffff Apr 23 08:40:02 unraid kernel: PREFETCH window: disabled. Apr 23 08:40:02 unraid kernel: ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16 Apr 23 08:40:02 unraid kernel: PCI: Setting latency timer of device 0000:00:1c.0 to 64 Apr 23 08:40:02 unraid kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64 Apr 23 08:40:02 unraid kernel: NET: Registered protocol family 2 Apr 23 08:40:02 unraid kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes) Apr 23 08:40:02 unraid kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes) Apr 23 08:40:02 unraid kernel: TCP bind hash table entries: 65536 (order: 6, 262144 bytes) Apr 23 08:40:02 unraid kernel: TCP: Hash tables configured (established 131072 bind 65536) Apr 23 08:40:02 unraid kernel: TCP reno registered Apr 23 08:40:02 unraid kernel: Unpacking initramfs... done Apr 23 08:40:02 unraid kernel: Freeing initrd memory: 27925k freed Apr 23 08:40:02 unraid kernel: Machine check exception polling timer started. Apr 23 08:40:02 unraid kernel: highmem bounce pool size: 64 pages Apr 23 08:40:02 unraid kernel: Installing knfsd (copyright (C) 1996 [email protected]).
Archived
This topic is now archived and is closed to further replies.