June 15, 201115 yr I've had that happen o a Win7 client with my test array when I upgraded from 4.7 to 5.0b3 then to b4, b5, b6 and b6a. A reboot of the client has always fixed it though. Yep, that did it. Weird. Thanks! Shawn
June 15, 201115 yr Need help as I have an issue with this release. I upgraded from 5.0Beta6d to this release by just updating the bzroot and bzimage files as stated and rebooted My array is set to not auto start. All looked well, I started the array. Waited to see if it would spin down the drives (set to 15mins for QA Global default, since I did not start from scratch, I assumed the disks would, there was an issue where until you clicked apply per disk it would not take) they did spin down. Copied and read some data from 2 different drives. Clicked "Stop" the array and then once it did stop i click "Reboot". The main page showed rebooting system but it never did. I telnet'ed in, it accepted my logon, I issued a "shutdown -h now" it accepted with the message "Broadcast message from root (pts/0) The system is going down for system halt NOW!" and normally one would see the processes, etc... shutting down, it never does with this command either. Had to warm reset the server. Once it came back up from the warm reboot it once again showed everything was fine. I started the array again. Clicked "Spin Down", they did. Waited 2 mins, Clicked "Spin up", they did, clicked "Stop" array. It stopped and then told me ALL my drives were "Unformatted" (The kicker here is I click stop on a perfectly fine running array). The only choices now were "Refresh", again "Stop" and a box to check off "Yes I want to do this" to Format (Which I did not check NOR do) no other options. I selected to click "Stop" again unRAID is hung AGAIN like the previous attempt to reboot. I can telnet in, nothing else.... Dont know if it is because I went from beta6d to this release, or there is more to it than that. So I can repeated the behavior twice. Warm rebooted again (not liking this now). unRAID rebooted once again "Stopped. Configuration valid." ready to be started anytime... What gives? I am attaching the last log I see on the flash drive but by the data/time stamp I dont think it was logging what happened. MEMEBER validated it was not the correct log (deleted from this post) All the hard drives are on LSI SAS Controllers. Leaving it in this states so I can perform anything Tom requests I do.
June 15, 201115 yr LOTS OF INFO... Are you running stock unRAID, any addon's, running unRAID via ESXi, etc.?
June 15, 201115 yr Dont know if it is because I went from beta6d to this release, or there is more to it than that. So I can repeated the behavior twice. I also upgraded from beta6d to beta7. Most of my drives are connected to an LSI SAS controller. I haven't experienced the problems which you report.
June 15, 201115 yr LOTS OF INFO... Are you running stock unRAID, any addon's, running unRAID via ESXi, etc.? I dont see where I used the words "LOTS OF INFO" not sure how you qouted that...? Not unrunning under any virtulization, physical unRAID. It has the same add-ons as before since I upgraded by copying those 2 files. It has unMENU, smarthistory, preclear_disk, APCUPSD, Powerdown, SSMTP, Status email, VIM, Screen, iStat just basic's for a lack of better words. What I did notice is... in this release the MTU size of 16110 did not take per the syslog, it always did previously, I changed it to 9000 and it took. Maybe the driver or something change, not a big deal, the goal was to go with the highest and then let the end to end negotiate. And I cant see this causing a problem being set at 9000 with this version. #The maximum MTU setting for Jumbo Frames is 16110. This value coincides with the maximum Jumbo Frames size of 16128. # Enable Jumbo Frames on eth0 NIC ifconfig eth0 mtu 16110
June 15, 201115 yr Dont know if it is because I went from beta6d to this release, or there is more to it than that. So I can repeated the behavior twice. I also upgraded from beta6d to beta7. Most of my drives are connected to an LSI SAS controller. I haven't experienced the problems which you report. I guess if Tom goes through that syslog I posted above and is interested in having me do something, i will, otherwise I will be left with only one option, which is wipe the usb key and start fresh. But as I questioned earlier how does one upgrade and the anwser was to just copy/upgrade the 2 files, this does not give a warm and fuzz feeling with this release.
June 15, 201115 yr I dont see where I used the words "LOTS OF INFO" not sure how you qouted that...? Lol, I changed the quoted text so not all of what you posted was reposted in the quote. It keeps the thread a little shorter and cleaner that way. If someone wants to see what you posted they can refer to the original post.
June 15, 201115 yr I dont see where I used the words "LOTS OF INFO" not sure how you qouted that...? Lol, I changed the quoted text so not all of what you posted was reposted in the quote. It keeps the thread a little shorter and cleaner that way. If someone wants to see what you posted they can refer to the original post. LOL, OK got u now, I was originally like "what the heck" went back and re-read what I posted LOL I am not upset or anything like that just a bit disappointed at the moment as I really was looking forward to this release greatly and even purchase 3t HD yesturday to test that out as well. I just want to get to the bottom of why its doing whats its doing. If I start from scratch and all is fine, I will be more than happy as well, but I am thinking in the lines once it a prod box for me and other release come out... (I know its BETA).
June 15, 201115 yr Madburg, I have the same issue (unformatted and freezing) and am on the way home to see what happened. I'll upload my syslog (such as it is) for review as well... Regards, Peter
June 15, 201115 yr I guess if it is not to much trouble, if everyone on this release could, select via the unRAID main page (not unmenu or anything else) to spin up any drives that are spun down, wait a 1 or 2 spin them down. Wait a minute or 2, spin them all back up and then select reboot. It would be most appreciated. If you see any issue with these few step, please post what hardware your using and syslog.
June 15, 201115 yr As mentioned earlier, I had the same issue that Madburg described. Updated v5.0b6d to v5.0b7. No errors noted. Functionality as expected although start and stop times seem a bit sluggish. Also a few delays when using the web gui as this version seems to spin up drives more than I would expect. Finished testing the copying to a cache drive and running mover as well as testing direct copies with no cache enabled. Stopped the array and then a number (not all) drives show as unformatted. But array was not really stopped. Tried stopping again and then the web gui became unresponsive. I unfortunately did NOT make note of the messages at the bottom of the window. I think it said something to the effect that it was still synching file systems (not sure though). Telnet worked fine as well as using the keyboard directly attached to the machine. I copied the syslog and then issued a shutdown command. Got the message that shutdown was commencing but it hung there. Hardware is as follows: MSI 790FX-GD70 Athlon X2 2.8GHz 4GB RAM 3 x IBM BR10i (LSI Controllers) for all attached drives (not using onboard controllers) Corsair HX750 power supply 20 WD or Hitachi 2TB drives + 1 WD 1TB drive for cache NO ADDONS or anything like that. 100% vanilla unRAID This hardware setup seems to run 5.0b6d without issues. Regards, Peter syslog_20110615.zip
June 15, 201115 yr Hello, I upgraded my server from 5.0 Beta 3 to Beta 7, deleted the bzroot and bzimage file along with the /config/super.dat file. When I rebooted my server all my drivers were unassigned (according to release notes this is normal) I re-assigned them but now it is staying "Initial Configuration" next to the Start Array button? Is this normal or if I hit start will it wipe the data out on the pre-existing drives?
June 15, 201115 yr LOTS OF INFO... Are you running stock unRAID, any addon's, running unRAID via ESXi, etc.? Not unrunning under any virtulization, physical unRAID. It has the same add-ons as before since I upgraded by copying those 2 files. It has unMENU, smarthistory, preclear_disk, APCUPSD, Powerdown, SSMTP, Status email, VIM, Screen, iStat just basic's for a lack of better words. What I did notice is... in this release the MTU size of 16110 did not take per the syslog, it always did previously, I changed it to 9000 and it took. Maybe the driver or something change, not a big deal, the goal was to go with the highest and then let the end to end negotiate. And I cant see this causing a problem being set at 9000 with this version. Something is very wrong in your posted syslog if you claim no virtualization and pure physical Unraid.: from the syslog: Jun 14 21:47:55 PNTower pspci[10195]: 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 08) Jun 14 21:47:55 PNTower pspci[10195]: 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08) Jun 14 21:47:55 PNTower pspci[10195]: 00:07.7 System peripheral: VMware Inc Virtual Machine Communication Interface (rev 10) Jun 14 21:47:55 PNTower pspci[10195]: 00:0f.0 VGA compatible controller: VMware Inc Abstract SVGA II Adapter Jun 14 21:47:55 PNTower pspci[10195]: 00:10.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:11.0 PCI bridge: VMware Inc PCI bridge (rev 02) Jun 14 21:47:55 PNTower pspci[10195]: 00:15.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:15.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:15.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:15.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:15.4 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:15.5 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:15.6 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:15.7 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:16.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:16.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:16.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) Jun 14 21:47:55 PNTower pspci[10195]: 00:16.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01) 440BX is Pentium II era and you have Xeon 3470 Jun 14 19:12:09 PNTower kernel: CPU0: Intel® Xeon® CPU X3470 @ 2.93GHz stepping 01
June 15, 201115 yr Hello, I upgraded my server from 5.0 Beta 3 to Beta 7, deleted the bzroot and bzimage file along with the /config/super.dat file. When I rebooted my server all my drivers were unassigned (according to release notes this is normal) I re-assigned them but now it is staying "Initial Configuration" next to the Start Array button? Is this normal or if I hit start will it wipe the data out on the pre-existing drives? You need to check that each of the drives have a filesystem, and that you don't see "unknown" on any of them. Click on each disk to see this information. Screenshots will help us. Don't do anything until you/we understand what's happening.
June 15, 201115 yr LOTS OF INFO... Are you running stock unRAID, any addon's, running unRAID via ESXi, etc.? Not unrunning under any virtulization, physical unRAID. It has the same add-ons as before since I upgraded by copying those 2 files. It has unMENU, smarthistory, preclear_disk, APCUPSD, Powerdown, SSMTP, Status email, VIM, Screen, iStat just basic's for a lack of better words. What I did notice is... in this release the MTU size of 16110 did not take per the syslog, it always did previously, I changed it to 9000 and it took. Maybe the driver or something change, not a big deal, the goal was to go with the highest and then let the end to end negotiate. And I cant see this causing a problem being set at 9000 with this version. Something is very wrong in your posted syslog if you claim no virtualization and pure physical Unraid.: from the syslog: I tested under both, I brought it up under ESXi one time to see if it would and then shutdown (as it never loaded my second controller, so I could not even start the array) I will try to delete that syslog then and update the post above that that was not avail. All my tests after were physically. As I stated, I did not see any syslog avaialbe around the time I ran these tests and had it freeze, I cannot explain why. So I attached the very last one that was available on the key, as you clearly saw it was not the log that should have been available to me, as i ran in once through ESX way before I started to test it physcally, with each freeze and warm reboot NO new logs appear in the \flash\log directory... I will delete all logs and go to reproduce a third time, are the syslog being written to the \flash\log dir in realtime, or just get copied there on boot ups or shutdowns? I think this would help me. I also had the tale log on via the main page, open during the testing and that too was frozen. I know I do not know the product/linx well but i am not trying to have anyone chase a tail, I want it perfect as can be just like eveyone else. I have gone throught many 5 betas, and I just know there is an issue with this one here (gut feeling is hardware with this new code). It will show itself sooner or later, I am offerring to get to the bottom of it before it hurts someone. In help I me I will take direction as what steps to take and results to post back. I can tell you hitting stop on an Array and then it shows all your disks with data on it as "unformatted" is not a pretty thing.
June 15, 201115 yr I guess if it is not to much trouble, if everyone on this release could, select via the unRAID main page (not unmenu or anything else) to spin up any drives that are spun down, wait a 1 or 2 spin them down. Wait a minute or 2, spin them all back up and then select reboot. It would be most appreciated. If you see any issue with these few step, please post what hardware your using and syslog. Madburg - Please be careful about giving directions that will leave the user in a vulnerable situation with their array. If this leaves the user with it appearing that all of their disks are unformatted, then someone will think they are supposed to press the format button, and next thing you know new users that are trying to help are running endless reiserfsck (best case) or have lost all of their data (worst case). At a minimum this should explain the state it left your array in, and what are the right next steps to avoid any data loss and restore their array to functionality.
June 16, 201115 yr I guess if it is not to much trouble, if everyone on this release could, select via the unRAID main page (not unmenu or anything else) to spin up any drives that are spun down, wait a 1 or 2 spin them down. Wait a minute or 2, spin them all back up and then select reboot. It would be most appreciated. If you see any issue with these few step, please post what hardware your using and syslog. Madburg - Please be careful about giving directions that will leave the user in a vulnerable situation with their array. If this leaves the user with it appearing that all of their disks are unformatted, then someone will think they are supposed to press the format button, and next thing you know new users that are trying to help are running endless reiserfsck (best case) or have lost all of their data (worst case). At a minimum this should explain the state it left your array in, and what are the right next steps to avoid any data loss and restore their array to functionality. I sort of understand what you are saying, but I clearly stated I ran into an issue and want to see if anyone else can reproduce it as well; that’s the only way! I personally am not running a production unRAID server testing this beta (I spent well over $1k to test various hardware and contributed where I can and still do. But I have yet to run a production system at all because it just not where I personally need it to be just yet for me. I purchased a dual Pro license, so I more than committed. ANd have a 3T drive coming to test this new funtionality as well.). At this time as others have asked whether to upgrade to this version or not, I would not recommend anyone upgrading their production system to this beta. I know some believe and stated it’s not much of a change from the previous betas but only Tom who is coding this known’s just how much has changed from the prior 6b-6d (Note in the release notes: - webGui: other misc changes, Anyone know what does are? Get my drift.). I have read many posts and even in this one where Joe L. and others clearly stated what steps to take and people either don’t wait for a reply or just do what they want and this can never be averted. You guys are a god save and are a great contribution to these forums. The response times are hands down the best and spot on I have seen anywhere and I have and still am moving friends of off ReadyNas’s, FreeNas, etc.. just by showing them the product and just how fast things move here. So if someone does not take the time out to read and get familiar and/or the patience to wait for an experts/moderators answer which will come sure enough then it just can not be helped. I cannot at minimum explain what the right next steps are when if you know that your disks which have data on them and were in a running array one minute, and when you stop an array magically shows they are ALL unformatted what to do from there. Clearly DON’T check of the box which will un-gray out the option to FORMAT them. Which I did state I did NOT do. But trying to reboot it once unRAID was hung does not work. I don’t think once it’s in that state anyone here can give the right steps to avoid data loss. I just know once I warm rebooted the server with the reset button it showed all the disks were fine (no longer unformatted) and allowed to start the array again. I was able to repeat this behavior twice in a row. Clearly this is not something you want to keep doing. I am going to uninstall all add-on’s and leave the default “/usr/local/sbin/emhttp &” in the GO script only now to make it plain vanilla unRAID, reboot twice and see what happens. It would be most helpfully if someone could explain how to get to the syslog so I can post it here. As I have the feeling the ones in \flash\logs directory get copied there only on shutdown or startups (maybe both)? I know Tom mentioned a few time in this post FIXED, FIXED, FIXED for various things, so maybe he is working on the next beta release, but hoping he can read and chime in here. So whatever is causing this behavior does not carry over into the next beta.
June 16, 201115 yr I only have the time to offer general knowledge. In the past there were issues with unrAID showing any drive that could not be mounted as a "reiserfs" as unformatted. Eventually, the wording when intially mounting drives was changed to "Mounting" When the array has a non-clean shutdown, as it did when you forced it down the file systems have to replay any transactions before they complete their "mount" commands. I've seen this take as much as 15 minutes with 2TB drives. 3TB drives will certainly be longer. During this time, older releases would show "unformatted", newer ones would show "mounting" The bug you experienced seems to be one where the disks had not yet finished their mounting... Or, as in one or two earlier releases, a race condition existed where no drive could get mounted. In fct, the same class of error occurred back in 2007 where I assisted in the analysis and helped Tom figure out what was happening with a picture of my system console. Basically, the "/dev/mdX" devices had not yet been created, so the attempt to mount disks failed, so they showed as "unformatted". The solution on the last release with this issue was to stop the array and then re-start it. The disks all would properly mount the second time. This bug is especially bad if you are adding a new disk and expected to hit the format button. Several users did on the 4.5.3 release, and formatted ALL their disks... fortunately, reiserfsck was able to scan their disks and recover nearly everything. You can read about the issue here: http://lime-technology.com/forum/index.php?topic=6206.0 It is certainly possible you encountered a similar issue. The most helpful would be a syslog when it occurs, and the output of the "mount" command possibly. Joe L
June 16, 201115 yr OK here is the evidence. I am attaching a text file (tail_log.txt) from a command Tom gave me a while back "tail -f /var/log/syslog". Here is what I did, I removed all entries in the GO script, so I was only left with: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & Rebooted unRAID, NO syslog's in \flash\log. So now i am wondering is it one of the add-on's with unMenu that actually does this for us? I kept the default to not start the array automatically. It showed all the disks were fine and the array could be started. But I reboot once more to make sure I am on a clean slate, plain vanilla unRAID 5.0Beta7. Once it rebooted I once again checked \Flash\logs directory NO syslog files. The following are the exact steps I took: 1) I telnet'ed in to the unRAID server. Logon as root, ran the command "tail -f /var/log/syslog". 2) With my web browser I went to the main URL. It showed "Stopped. Configuration valid" I clicked the "Start" button. Array started. 3) I clicked the "Spin Down" button. Drives spun down. Waited one minute 4) I clicked the "Spin Up" button. Drives spun up. Waited one minute 5) I clicked the "Stop" button to stop the array. Array stopped, it did not show drives were unformatted this time. Waited one minute 6) I clicked the "Reboot" button. Main page changed to "System is rebooting..." unRAID is now HUNG! I cannot get to the FLASH share either. You can ping the server though. I copied and pasted EVERY line from start to finish from the "tail -f /var/log/syslog" command in my windows command shell it is attached to this post. I am leaving the server hung like this and hope Tom can tell me what to do now asap. I have screenshots of each step of the webGUI for him if he needs them. So now there should be no doubt there is an issue here! tail_log.txt
June 16, 201115 yr madburg is right, but for me just stop the array once triggered the kernel bug: Jun 16 00:51:36 Servidor emhttp: _shcmd: shcmd (100): exit status: 1 Jun 16 00:51:36 Servidor emhttp: shcmd (101): rmdir /mnt/cache >/dev/null 2>&1 Jun 16 00:51:36 Servidor emhttp: _shcmd: shcmd (101): exit status: 1 Jun 16 00:51:36 Servidor emhttp: Retry unmounting disk share(s)... Jun 16 00:51:36 Servidor kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Jun 16 00:51:36 Servidor kernel: IP: [<c1037e75>] queue_delayed_work_on+0x33/0xbf Jun 16 00:51:36 Servidor kernel: *pdpt = 000000002e863001 *pde = 0000000000000000 Jun 16 00:51:36 Servidor kernel: Oops: 0000 [#1] SMP Jun 16 00:51:36 Servidor kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4:1.0/host0/target0:0:0/0:0:0:0/block/sdd/stat Jun 16 00:51:36 Servidor kernel: Modules linked in: bridge stp llc tun vboxnetflt vboxnetadp vboxdrv md_mod xor pata_jmicron mvsas libsas ahci jmicron r8169 libahci scsi_transport_sas asus_atk0110 hwmon Jun 16 00:51:36 Servidor kernel: Jun 16 00:51:36 Servidor kernel: Pid: 133, comm: sync_supers Not tainted 2.6.37.6-unRAID #2 System manufacturer System Product Name/M4A87TD/USB3 Jun 16 00:51:36 Servidor kernel: EIP: 0060:[<c1037e75>] EFLAGS: 00010246 CPU: 0 Jun 16 00:51:36 Servidor kernel: EIP is at queue_delayed_work_on+0x33/0xbf Jun 16 00:51:36 Servidor kernel: EAX: f8580138 EBX: ffffffff ECX: f8580134 EDX: 00000000 Jun 16 00:51:36 Servidor kernel: ESI: 00000000 EDI: f8580134 EBP: f0e0fed0 ESP: f0e0fec4 Jun 16 00:51:36 Servidor kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Jun 16 00:51:36 Servidor kernel: Process sync_supers (pid: 133, ti=f0e0e000 task=f0e013e0 task.ti=f0e0e000) Jun 16 00:51:36 Servidor kernel: Stack: Jun 16 00:51:36 Servidor kernel: f8570000 ec7ed6d4 ec7ed680 f0e0fedc c10382f3 0000000a f0e0ff40 c10d2c75 Jun 16 00:51:36 Servidor kernel: f8570000 00000012 00000000 e02d2e70 006d50ee 03c0c8b0 00000000 047804db Jun 16 00:51:36 Servidor kernel: ec7ed698 00000012 00000004 f8570000 00000763 00000000 e918c000 f1b47060 Jun 16 00:51:36 Servidor kernel: Call Trace: Jun 16 00:51:36 Servidor kernel: [<c10382f3>] ? queue_delayed_work+0x1b/0x1e Jun 16 00:51:36 Servidor kernel: [<c10d2c75>] ? do_journal_end+0x7e5/0xb46 Jun 16 00:51:36 Servidor kernel: [<c10d3031>] ? journal_end_sync+0x5b/0x63 Jun 16 00:51:36 Servidor kernel: [<c10c7289>] ? reiserfs_sync_fs+0x32/0x51 Jun 16 00:51:36 Servidor kernel: [<c10c72b5>] ? reiserfs_write_super+0xd/0xf Jun 16 00:51:36 Servidor kernel: [<c107d379>] ? sync_supers+0x5e/0xa2 Jun 16 00:51:36 Servidor kernel: [<c106555b>] ? bdi_sync_supers+0x0/0x44 Jun 16 00:51:36 Servidor kernel: [<c1065590>] ? bdi_sync_supers+0x35/0x44 Jun 16 00:51:36 Servidor kernel: [<c103af7e>] ? kthread+0x62/0x67 Jun 16 00:51:36 Servidor kernel: [<c103af1c>] ? kthread+0x0/0x67 Jun 16 00:51:36 Servidor kernel: [<c1002cb6>] ? kernel_thread_helper+0x6/0x10 Jun 16 00:51:36 Servidor kernel: Code: d6 53 89 c3 f0 0f ba 29 00 19 d2 31 c0 85 d2 0f 85 9d 00 00 00 83 79 10 00 74 04 0f 0b eb fe 8d 41 04 39 41 04 74 04 0f 0b eb fe <f6> 06 02 b8 08 00 00 00 75 19 89 c8 e8 b1 e6 ff ff 85 c0 74 08 Jun 16 00:51:36 Servidor kernel: EIP: [<c1037e75>] queue_delayed_work_on+0x33/0xbf SS:ESP 0068:f0e0fec4 Jun 16 00:51:36 Servidor kernel: CR2: 0000000000000000 Jun 16 00:51:36 Servidor kernel: ---[ end trace ba1b4febe6addce3 ]---
June 16, 201115 yr OK here is the evidence. I am attaching a text file (tail_log.txt) from a command Tom gave me a while back "tail -f /var/log/syslog". Here is what I did, I removed all entries in the GO script, so I was only left with: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & Rebooted unRAID, NO syslog's in \flash\log. So now i am wondering is it one of the add-on's with unMenu that actually does this for us? I kept the default to not start the array automatically. It showed all the disks were fine and the array could be started. But I reboot once more to make sure I am on a clean slate, plain vanilla unRAID 5.0Beta7. Once it rebooted I once again checked \Flash\logs directory NO syslog files. The following are the exact steps I took: 1) I telnet'ed in to the unRAID server. Logon as root, ran the command "tail -f /var/log/syslog". 2) With my web browser I went to the main URL. It showed "Stopped. Configuration valid" I clicked the "Start" button. Array started. 3) I clicked the "Spin Down" button. Drives spun down. Waited one minute 4) I clicked the "Spin Up" button. Drives spun up. Waited one minute 5) I clicked the "Stop" button to stop the array. Array stopped, it did not show drives were unformatted this time. Waited one minute 6) I clicked the "Reboot" button. Main page changed to "System is rebooting..." unRAID is now HUNG! I cannot get to the FLASH share either. You can ping the server though. I copied and pasted EVERY line from start to finish from the "tail -f /var/log/syslog" command in my windows command shell it is attached to this post. I am leaving the server hung like this and hope Tom can tell me what to do now asap. I have screenshots of each step of the webGUI for him if he needs them. So now there should be no doubt there is an issue here! I checked up on my telnet session this morning which was running the "tail -f /var/log/syslog" command in my windows command shell since I attached it's output last night for all. There is one new line now: Jun 15 22:26:29 PNTower emhttp: shcmd (169): sync Jun 16 04:40:01 PNTower logrotate: ALERT - exited abnormally. What was it doing for 5-6 hours? It is still hung, I cannot get to the FLASH share either. You can ping the server though.
June 16, 201115 yr Hello, I upgraded my server from 5.0 Beta 3 to Beta 7, deleted the bzroot and bzimage file along with the /config/super.dat file. When I rebooted my server all my drivers were unassigned (according to release notes this is normal) I re-assigned them but now it is staying "Initial Configuration" next to the Start Array button? Is this normal or if I hit start will it wipe the data out on the pre-existing drives? You need to check that each of the drives have a filesystem, and that you don't see "unknown" on any of them. Click on each disk to see this information. Screenshots will help us. Don't do anything until you/we understand what's happening. I believe each drive has a FileSystem, here are some screenshots: Before Upgrade: After Upgrade: I can't show images of each drive at the moment as the box appears to have locked up overnight and I am not home to reboot it manually.
June 16, 201115 yr madburg is right, but for me just stop the array once triggered the kernel bug: Jun 16 00:51:36 Servidor emhttp: _shcmd: shcmd (100): exit status: 1 Jun 16 00:51:36 Servidor emhttp: shcmd (101): rmdir /mnt/cache >/dev/null 2>&1 Jun 16 00:51:36 Servidor emhttp: _shcmd: shcmd (101): exit status: 1 Jun 16 00:51:36 Servidor emhttp: Retry unmounting disk share(s)... Jun 16 00:51:36 Servidor kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Jun 16 00:51:36 Servidor kernel: IP: [<c1037e75>] queue_delayed_work_on+0x33/0xbf Jun 16 00:51:36 Servidor kernel: *pdpt = 000000002e863001 *pde = 0000000000000000 Jun 16 00:51:36 Servidor kernel: Oops: 0000 [#1] SMP Jun 16 00:51:36 Servidor kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4:1.0/host0/target0:0:0/0:0:0:0/block/sdd/stat Jun 16 00:51:36 Servidor kernel: Modules linked in: bridge stp llc tun vboxnetflt vboxnetadp vboxdrv md_mod xor pata_jmicron mvsas libsas ahci jmicron r8169 libahci scsi_transport_sas asus_atk0110 hwmon Jun 16 00:51:36 Servidor kernel: Jun 16 00:51:36 Servidor kernel: Pid: 133, comm: sync_supers Not tainted 2.6.37.6-unRAID #2 System manufacturer System Product Name/M4A87TD/USB3 Jun 16 00:51:36 Servidor kernel: EIP: 0060:[<c1037e75>] EFLAGS: 00010246 CPU: 0 Jun 16 00:51:36 Servidor kernel: EIP is at queue_delayed_work_on+0x33/0xbf Jun 16 00:51:36 Servidor kernel: EAX: f8580138 EBX: ffffffff ECX: f8580134 EDX: 00000000 Jun 16 00:51:36 Servidor kernel: ESI: 00000000 EDI: f8580134 EBP: f0e0fed0 ESP: f0e0fec4 Jun 16 00:51:36 Servidor kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Jun 16 00:51:36 Servidor kernel: Process sync_supers (pid: 133, ti=f0e0e000 task=f0e013e0 task.ti=f0e0e000) Jun 16 00:51:36 Servidor kernel: Stack: Jun 16 00:51:36 Servidor kernel: f8570000 ec7ed6d4 ec7ed680 f0e0fedc c10382f3 0000000a f0e0ff40 c10d2c75 Jun 16 00:51:36 Servidor kernel: f8570000 00000012 00000000 e02d2e70 006d50ee 03c0c8b0 00000000 047804db Jun 16 00:51:36 Servidor kernel: ec7ed698 00000012 00000004 f8570000 00000763 00000000 e918c000 f1b47060 Jun 16 00:51:36 Servidor kernel: Call Trace: Jun 16 00:51:36 Servidor kernel: [<c10382f3>] ? queue_delayed_work+0x1b/0x1e Jun 16 00:51:36 Servidor kernel: [<c10d2c75>] ? do_journal_end+0x7e5/0xb46 Jun 16 00:51:36 Servidor kernel: [<c10d3031>] ? journal_end_sync+0x5b/0x63 Jun 16 00:51:36 Servidor kernel: [<c10c7289>] ? reiserfs_sync_fs+0x32/0x51 Jun 16 00:51:36 Servidor kernel: [<c10c72b5>] ? reiserfs_write_super+0xd/0xf Jun 16 00:51:36 Servidor kernel: [<c107d379>] ? sync_supers+0x5e/0xa2 Jun 16 00:51:36 Servidor kernel: [<c106555b>] ? bdi_sync_supers+0x0/0x44 Jun 16 00:51:36 Servidor kernel: [<c1065590>] ? bdi_sync_supers+0x35/0x44 Jun 16 00:51:36 Servidor kernel: [<c103af7e>] ? kthread+0x62/0x67 Jun 16 00:51:36 Servidor kernel: [<c103af1c>] ? kthread+0x0/0x67 Jun 16 00:51:36 Servidor kernel: [<c1002cb6>] ? kernel_thread_helper+0x6/0x10 Jun 16 00:51:36 Servidor kernel: Code: d6 53 89 c3 f0 0f ba 29 00 19 d2 31 c0 85 d2 0f 85 9d 00 00 00 83 79 10 00 74 04 0f 0b eb fe 8d 41 04 39 41 04 74 04 0f 0b eb fe <f6> 06 02 b8 08 00 00 00 75 19 89 c8 e8 b1 e6 ff ff 85 c0 74 08 Jun 16 00:51:36 Servidor kernel: EIP: [<c1037e75>] queue_delayed_work_on+0x33/0xbf SS:ESP 0068:f0e0fec4 Jun 16 00:51:36 Servidor kernel: CR2: 0000000000000000 Jun 16 00:51:36 Servidor kernel: ---[ end trace ba1b4febe6addce3 ]--- You maybe right, as I just repeated the steps I took originally when I noticed the issue. I was waiting for this release badly to have SAS controller spin up/down support, so that is what I started testing first. But they may not have anything to do with it. It maybe just as simple as start and stop arrray. Dont know though. Thanks for posting your experience.
June 16, 201115 yr I tried several things to recreate. I stopped and started my array without difficulty. Then stopped, clicked "Reboot", and system rebooted. Started array, no problem. Then tried to recreate these steps from Madburg: I guess if it is not to much trouble, if everyone on this release could, select via the unRAID main page (not unmenu or anything else) to spin up any drives that are spun down, wait a 1 or 2 spin them down. Wait a minute or 2, spin them all back up and then select reboot. It would be most appreciated. If you see any issue with these few step, please post what hardware your using and syslog. I spun down, waited, spun up, waited, spun down, waited, spun up. Instructions then say to click reboot. But reboot is not an option until array is stopped. So I clicked stop, array stopped, and then clicked reboot. No problem. If there are other steps to try, let me know. Whatever is the problem, is appears to be related to specific configurations. I am not running any addons that keep disks busy. My HW setup is: SuperMicro C2SEE-O (Intel MB / 4G RAM) SuperMicro AOC-SATA2-MV8 IBM BR10i Areca ARC-1200 Update on stability of beta7: Working great for me. I am waiting for Joe L.'s preclear update to add another disk. BTW, 3T disks are huge!
June 16, 201115 yr Whatever is the problem, is appears to be related to specific configurations. Seems to be the case, thanks for trying and posting the results. I am running on: SuperMicro X8SI6-F-O (Xeon 3470) Kingston Fully Buffered ECC (2 x 4GB RAM) Onboard SAS2008 (LSI) LSI SAS 9201-16i (Add-on card) Various HD's from 2TB->160GB Hitachi Deskstar's (from 7K -> 5k) (1) Seagate 7K 250GB (1) WD 10K 80gb FYI, just in case it helps, since it is not a prod box, I dont add a parity drive for these initial test.
Archived
This topic is now archived and is closed to further replies.