July 12, 201114 yr So I see that the free space (Shown on the web gui) on drives doesn't appear to update in 8c (Possibly earlier versions and I didn't notice!) Apologies if this has been reported already, don't fancy reading all 12 pages
July 12, 201114 yr I upgraded to beta8d and I still have the same permission problem. The default permissions are the same as pre 5.0. Hopefully this permission issue is the same issue when my friend uses his laptop.
July 12, 201114 yr So I see that the free space (Shown on the web gui) on drives doesn't appear to update in 8c (Possibly earlier versions and I didn't notice!) Apologies if this has been reported already, don't fancy reading all 12 pages This was fixed in 8d
July 12, 201114 yr So I see that the free space (Shown on the web gui) on drives doesn't appear to update in 8c (Possibly earlier versions and I didn't notice!) Apologies if this has been reported already, don't fancy reading all 12 pages Nor 4 posts back for that matter... Note to everyone using betas: if you are not using the latest beta, do not post in this thread. Dont fancy you dont receive help either
July 12, 201114 yr Well I didn't read any of that, just the 5.0beta8d release notes, which didn't mention it.
July 12, 201114 yr After upgrading I cant see any file. It got fixed after I have set chmod to 777 for all files. What is the correct chmod setting?
July 12, 201114 yr Follow the release notes. They explicitly state to invoke the NEW PERMISSIONS utility.
July 12, 201114 yr Hey Tom, Quick question. Is there any way to determine array state as being in Maintenance mode via emhttp? Cheers
July 13, 201114 yr Hey Tom, Quick question. Is there any way to determine array state as being in Maintenance mode via emhttp? Cheers array started, but no disks mounted perhaps?
July 13, 201114 yr Hi Tom (and Joe L.) I'm not sure if this is kernel-related or preclear-script-related, but I'm getting what looks like cache-related errors in my syslog AS SOON AS THE PRECLEAR ENTERS STEP 2 - ZEROING. The first syslog snippet shows a read-ahead cache error, the second syslog snippet shows a write cache error. First time hardware was: X8SIL-F motherboard -> Motherboard SATA ports -> Hitachi 3TB green drive Second time hardware was: X8SIL-F motherboard -> MV8 SAS Controller card -> Hitachi 3TB green drive UPDATE: I found reference to this issue in the change log for Linux kernel v2.6.31. It looks as though it's a simple warning which can be ignored - is that correct?? http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.31 commit 83d349f35e1ae72268c5104dbf9ab2ae635425d4 Author: Linus Torvalds <[email protected]> Date: Fri Aug 21 09:23:57 2009 -0700 x86: don't send an IPI to the empty set of CPU's The default_send_IPI_mask_logical() function uses the "flat" APIC mode to send an IPI to a set of CPU's at once, but if that set happens to be empty, some older local APIC's will apparently be rather unhappy. So just warn if a caller gives us an empty mask, and ignore it. This fixes a regression in 2.6.30.x, due to commit 4595f9620 ("x86: change flush_tlb_others to take a const struct cpumask"), documented here: http://bugzilla.kernel.org/show_bug.cgi?id=13933 which causes a silent lock-up. It only seems to happen on PPro, P2, P3 and Athlon XP cores. Most developers sadly (or not so sadly, if you're a developer..) have more modern CPU's. Also, on x86-64 we don't use the flat APIC mode, so it would never trigger there even if the APIC didn't like sending an empty IPI mask. Reported-by: Pavel Vilim <[email protected]> Reported-and-tested-by: Thomas Björnell <[email protected]> Reported-and-tested-by: Martin Rogge <[email protected]> Cc: Mike Travis <[email protected]> Cc: Ingo Molnar <[email protected]> Cc: [email protected] Signed-off-by: Linus Torvalds <[email protected]> FIRST SYSLOG SNIPPET: Jul 11 10:54:41 Tower kernel: ------------[ cut here ]------------ Jul 11 10:54:41 Tower kernel: WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x2f/0xb9() (Minor Issues) Jul 11 10:54:41 Tower kernel: Hardware name: X8SIL Jul 11 10:54:41 Tower kernel: empty IPI mask Jul 11 10:54:41 Tower kernel: Modules linked in: md_mod xor mvsas ahci libsas libahci e1000e i2c_i801 i2c_core scsi_transport_sas [last unloaded: md_mod] (Drive related) Jul 11 10:54:41 Tower kernel: Pid: 5483, comm: dd Not tainted 2.6.37.6-unRAID #3 (Errors) Jul 11 10:54:41 Tower kernel: Call Trace: (Errors) Jul 11 10:54:41 Tower kernel: [<c1028ef6>] warn_slowpath_common+0x65/0x7a (Errors) Jul 11 10:54:41 Tower kernel: [<c10166ca>] ? default_send_IPI_mask_logical+0x2f/0xb9 (Errors) Jul 11 10:54:41 Tower kernel: [<c1028f6f>] warn_slowpath_fmt+0x26/0x2a (Errors) Jul 11 10:54:41 Tower kernel: [<c10166ca>] default_send_IPI_mask_logical+0x2f/0xb9 (Errors) Jul 11 10:54:41 Tower kernel: [<c1014da8>] native_send_call_func_ipi+0x4f/0x51 (Errors) Jul 11 10:54:41 Tower kernel: [<c1048848>] smp_call_function_many+0x183/0x19b (Errors) Jul 11 10:54:41 Tower kernel: [<c105c962>] ? drain_local_pages+0x0/0x10 (Errors) Jul 11 10:54:41 Tower kernel: [<c105c962>] ? drain_local_pages+0x0/0x10 (Errors) Jul 11 10:54:41 Tower kernel: [<c104887a>] smp_call_function+0x1a/0x20 (Errors) Jul 11 10:54:41 Tower kernel: [<c102d0ff>] on_each_cpu+0xf/0x1e (Errors) Jul 11 10:54:41 Tower kernel: [<c105d5b6>] drain_all_pages+0x14/0x16 (Errors) Jul 11 10:54:41 Tower kernel: [<c105dbc0>] __alloc_pages_nodemask+0x31b/0x458 (Errors) Jul 11 10:54:41 Tower kernel: [<c1059dd2>] grab_cache_page_write_begin+0x4f/0x8b (Errors) Jul 11 10:54:41 Tower kernel: [<c1099454>] block_write_begin+0x21/0x68 (Errors) Jul 11 10:54:41 Tower kernel: [<c109c926>] ? blkdev_write_end+0x2d/0x36 (Errors) Jul 11 10:54:41 Tower kernel: [<c109c94d>] blkdev_write_begin+0x1e/0x20 (Errors) Jul 11 10:54:41 Tower kernel: [<c109bda7>] ? blkdev_get_block+0x0/0xc4 (Errors) Jul 11 10:54:41 Tower kernel: [<c105882d>] generic_perform_write+0x82/0x153 (Errors) Jul 11 10:54:41 Tower kernel: [<c105893d>] generic_file_buffered_write+0x3f/0x6b (Errors) Jul 11 10:54:41 Tower kernel: [<c1059ad5>] __generic_file_aio_write+0x392/0x3d3 (Errors) Jul 11 10:54:41 Tower kernel: [<c109bff8>] blkdev_aio_write+0x2e/0x6d (Errors) Jul 11 10:54:41 Tower kernel: [<c107c8e8>] do_sync_write+0x8a/0xc5 (Errors) Jul 11 10:54:41 Tower kernel: [<c1003cdd>] ? do_IRQ+0x83/0x97 (Errors) Jul 11 10:54:41 Tower kernel: [<c109fb1e>] ? fsnotify+0x1ad/0x1c7 (Errors) Jul 11 10:54:41 Tower kernel: [<c1199733>] ? __clear_user+0x11/0x28 (Errors) Jul 11 10:54:41 Tower kernel: [<c107d130>] vfs_write+0x8a/0xfd (Errors) Jul 11 10:54:41 Tower kernel: [<c107c85e>] ? do_sync_write+0x0/0xc5 (Errors) Jul 11 10:54:41 Tower kernel: [<c107d23a>] sys_write+0x3b/0x60 (Errors) Jul 11 10:54:41 Tower kernel: [<c1321505>] syscall_call+0x7/0xb (Errors) Jul 11 10:54:41 Tower kernel: ---[ end trace 5ede26e52f190196 ]--- SECOND SYSLOG SNIPPET: Jul 13 00:22:48 Tower kernel: ------------[ cut here ]------------ Jul 13 00:22:48 Tower kernel: WARNING: at arch/x86/kernel/apic/ipi.c:109 default_send_IPI_mask_logical+0x2f/0xb9() (Minor Issues) Jul 13 00:22:48 Tower kernel: Hardware name: X8SIL Jul 13 00:22:48 Tower kernel: empty IPI mask Jul 13 00:22:48 Tower kernel: Modules linked in: w83627ehf hwmon_vid coretemp hwmon md_mod xor i2c_i801 i2c_core e1000e ahci libahci mvsas libsas scsi_transport_sas [last unloaded: i2c_dev] (Drive related) Jul 13 00:22:48 Tower kernel: Pid: 6114, comm: dd Not tainted 2.6.37.6-unRAID #3 (Errors) Jul 13 00:22:48 Tower kernel: Call Trace: (Errors) Jul 13 00:22:48 Tower kernel: [<c1028ef6>] warn_slowpath_common+0x65/0x7a (Errors) Jul 13 00:22:48 Tower kernel: [<c10166ca>] ? default_send_IPI_mask_logical+0x2f/0xb9 (Errors) Jul 13 00:22:48 Tower kernel: [<c1028f6f>] warn_slowpath_fmt+0x26/0x2a (Errors) Jul 13 00:22:48 Tower kernel: [<c10166ca>] default_send_IPI_mask_logical+0x2f/0xb9 (Errors) Jul 13 00:22:48 Tower kernel: [<c1014da8>] native_send_call_func_ipi+0x4f/0x51 (Errors) Jul 13 00:22:48 Tower kernel: [<c1048848>] smp_call_function_many+0x183/0x19b (Errors) Jul 13 00:22:48 Tower kernel: [<c105c962>] ? drain_local_pages+0x0/0x10 (Errors) Jul 13 00:22:48 Tower kernel: [<c105c962>] ? drain_local_pages+0x0/0x10 (Errors) Jul 13 00:22:48 Tower kernel: [<c104887a>] smp_call_function+0x1a/0x20 (Errors) Jul 13 00:22:48 Tower kernel: [<c102d0ff>] on_each_cpu+0xf/0x1e (Errors) Jul 13 00:22:48 Tower kernel: [<c105d5b6>] drain_all_pages+0x14/0x16 (Errors) Jul 13 00:22:48 Tower kernel: [<c105dbc0>] __alloc_pages_nodemask+0x31b/0x458 (Errors) Jul 13 00:22:48 Tower kernel: [<c105f0ce>] __do_page_cache_readahead+0x9d/0x16a (Errors) Jul 13 00:22:48 Tower kernel: [<c105f1b2>] ra_submit+0x17/0x1c (Errors) Jul 13 00:22:48 Tower kernel: [<c105f3dd>] ondemand_readahead+0x17c/0x188 (Errors) Jul 13 00:22:48 Tower kernel: [<c1058ffc>] ? sync_page_killable+0x0/0x2b (Errors) Jul 13 00:22:48 Tower kernel: [<c105f442>] page_cache_async_readahead+0x59/0x7c (Errors) Jul 13 00:22:48 Tower kernel: [<c105a390>] T.825+0xeb/0x399 (Errors) Jul 13 00:22:48 Tower kernel: [<c105a7e3>] generic_file_aio_read+0x1a5/0x1d6 (Errors) Jul 13 00:22:48 Tower kernel: [<c107c9ad>] do_sync_read+0x8a/0xc5 (Errors) Jul 13 00:22:48 Tower kernel: [<c109fb1e>] ? fsnotify+0x1ad/0x1c7 (Errors) Jul 13 00:22:48 Tower kernel: [<c107d2e7>] vfs_read+0x88/0xfb (Errors) Jul 13 00:22:48 Tower kernel: [<c107c923>] ? do_sync_read+0x0/0xc5 (Errors) Jul 13 00:22:48 Tower kernel: [<c107d3f1>] sys_read+0x3b/0x60 (Errors) Jul 13 00:22:48 Tower kernel: [<c1321505>] syscall_call+0x7/0xb (Errors) Jul 13 00:22:48 Tower kernel: ---[ end trace 1fd5c41864c1e6e5 ]--- Thanks Cheers Toby
July 13, 201114 yr I was running happily 5.0-beta8b, and today decided to upgrade to v8d. Did regular upgrade process and rebooted to no avail. The system starts to load bzimage and bzroot and then it either hangs or reboots. It hangs during the line "Booting No 0, Processors #1_". What do I next? (Ps: I had a working array with last parity check a few days ago with no errors. What would be the safest way to get the array back?) Thanks. To go back, just put back the older bzroot and bzimage and reboot. (It is why I always rename them instead of overwriting them) On my server I would have named the old files as bzroot.58b and bzimage.58b before putting the newer files into place from the most recent distribution. You might want to put the new bzroot and bzimages in place again. You might not have copied them into place in their entirety. Also, do a memory test. It too could cause an unusual error if it is not set up correctly or is defective.
July 13, 201114 yr Does anyone have the old Beta7 download? I was running it without issues, then I tried 8a,8b and 8d, none of them come up correctly. I cannot get on via network or browser.
July 13, 201114 yr Plugins, while a fantastic feature, can be the source of problems... particularly with upgrades. I'm liking the new "Maintenance" mode... perhaps also, could either Maintenance also bypass loading of all packages from /boot/extra, or in the alternative, perhaps add a "Safe Mode" boot option or additional option to Maintenance mode that would do so?
July 13, 201114 yr Plugins, while a fantastic feature, can be the source of problems... particularly with upgrades. I'm liking the new "Maintenance" mode... perhaps also, could either Maintenance also bypass loading of all packages from /boot/extra, or in the alternative, perhaps add a "Safe Mode" boot option or additional option to Maintenance mode that would do so? I like this idea of not loading anything in /boot/extra and the one step further thing. Perhaps checking that box and rebooting would cause the current go script to be renamed go.old and a new "default" go script would be created right before the reboot. After "Maintenance" mode is unchecked and reboot is hit, the go.old is set back as the current startup script.
July 13, 201114 yr unRAID newbie so please be patient. Built my server on 5.0beta7 because I was starting with some Hitachi 3TB drives (1 parity + 1 data + 1 WD2TB data). I have since updated to 5.0beta8d but have had problems expanding the array on both versions. After successful testing and data population in the 3 drive configuration I am now trying to add two more 3TB drives to my server (unRAID Pro license). Both drives were factory fresh and are physically installed (/dev/hde and /dev/hdf). I ran preclear_disk on hdf (took 52 hours). On the Main tab of the WebGUI both drives show up and selecting hde it shows as unformatted while the precleared hdf shows GPT: 4K-aligned. Both have file system type = unknown. Selecting just the "raw" hde drive and checking the "Yes I want to do this" box then pressing "Start" does not start the array. The disk status indicator for the new drive remains blue (the original 3 disks are green) and the Array status is red and "Stopped found 1 new disk". Looking at the disk settings it still shows Partition format and File system type as "unknown". The server's disk activity light does not indicate any disk activity. Running preclear_disk.sh -l at the server console does not show any of the 4 disks now supposedly assigned to the array as available, only hdf. If I attempt to add the precleared hdf instead, the Firefox WebGUI session hangs with "Transferring data from Tower..." Attempts to start a new session with //tower also hang (Firefox or IE) Running preclear_disk.sh -l at the server console now shows both hde & hdf as available. Is my expansion procedure correct or am I missing something ?
July 13, 201114 yr Perhaps checking that box and rebooting would cause the current go script to be renamed go.old and a new "default" go script would be created right before the reboot. I wouldn't go that far... I think go script mods will (should?) go away to be replaced by the event callouts. Particularly with a flag to check for "Maintenance" mode..... plugin devs need to take that into account.
July 13, 201114 yr Perhaps checking that box and rebooting would cause the current go script to be renamed go.old and a new "default" go script would be created right before the reboot. I wouldn't go that far... I think go script mods will (should?) go away to be replaced by the event callouts. Particularly with a flag to check for "Maintenance" mode..... plugin devs need to take that into account. Fair enough, I am still in the old mindset of not having the callouts. I know I try very hard to NOT put stuff in my go script. I think I have the one line for unMenu .auto_install packages and the emhttp line and that is it.
July 13, 201114 yr I saw in this thread somewhere that the unlicensed (free) version of 5.0 stopped working with one of the beta releases. I have been on beta4 for quite some time and would like to go to beta8d. Is it still broken for 8d? I haven't had any issues with it, so I can hold out. It gets limited use as a simple file and photo server.
July 13, 201114 yr I saw in this thread somewhere that the unlicensed (free) version of 5.0 stopped working with one of the beta releases. I have been on beta4 for quite some time and would like to go to beta8d. Is it still broken for 8d? I haven't had any issues with it, so I can hold out. It gets limited use as a simple file and photo server. Just rename the bzroot and bzimage of your current install before copying over the new stuff. If the new install does not work for you then delete the bzroot and bzimage and then rename the previous install files and reboot one last time.
July 13, 201114 yr I saw in this thread somewhere that the unlicensed (free) version of 5.0 stopped working with one of the beta releases. Is it still broken for 8d? This is fixed in the 8d release.
July 13, 201114 yr unRAID newbie so please be patient. Built my server on 5.0beta7 because I was starting with some Hitachi 3TB drives (1 parity + 1 data + 1 WD2TB data). I have since updated to 5.0beta8d but have had problems expanding the array on both versions. After successful testing and data population in the 3 drive configuration I am now trying to add two more 3TB drives to my server (unRAID Pro license). Both drives were factory fresh and are physically installed (/dev/hde and /dev/hdf). I ran preclear_disk on hdf (took 52 hours). On the Main tab of the WebGUI both drives show up and selecting hde it shows as unformatted while the precleared hdf shows GPT: 4K-aligned. Both have file system type = unknown. Selecting just the "raw" hde drive and checking the "Yes I want to do this" box then pressing "Start" does not start the array. The disk status indicator for the new drive remains blue (the original 3 disks are green) and the Array status is red and "Stopped found 1 new disk". Looking at the disk settings it still shows Partition format and File system type as "unknown". The server's disk activity light does not indicate any disk activity. Running preclear_disk.sh -l at the server console does not show any of the 4 disks now supposedly assigned to the array as available, only hdf. If I attempt to add the precleared hdf instead, the Firefox WebGUI session hangs with "Transferring data from Tower..." Attempts to start a new session with //tower also hang (Firefox or IE) Running preclear_disk.sh -l at the server console now shows both hde & hdf as available. Is my expansion procedure correct or am I missing something ? Just a comment, but I would not be surprised if IDE support (including pseudo-IDE support) is not being well maintained in current Linux kernels, in particular, keeping up with features needed for the larger-than-2GB drives. The fact that your drives are assigned hde and hdf instead of sde and sdf (or the appropriate sd? symbols) tells me that you are using pseudo-IDE support. Enter your BIOS settings and change the SATA drive support to be a native SATA support choice, such as AHCI. Just a reminder, including a syslog is very important for troubleshooting.
July 13, 201114 yr I just upgraded from beta7 to beta 8 and it seems to be working fine. Only thing I did was copy bzimage and bzroot over. However it booted right up, not in "STOPPED" Also do I need to rerun the permissions script? Also this was checked by default, is this ok "Correct any Parity-Check errors by writing the Parity disk with corrected parity." thanks
July 13, 201114 yr Does anyone have the old Beta7 download? I was running it without issues, then I tried 8a,8b and 8d, none of them come up correctly. I cannot get on via network or browser. I've got it - I'm trying to upload it right now - will provide a link as soon as it's finished. ( unRAID Server 5.0-beta7 AiO.zip ) edit: unRAID Server 5.0-beta7 AiO.zip
July 13, 201114 yr Hi all, I have a severe problem. I switched a 2TB with a 3TB drive, but the rebuild doesn't work properly. I also can't put back the old drive because then unRaid tells me it is not big enough. The 3TB disc has been pre cleared with the script in version 1.12. Rebuild stops somewhere around 2.3 - 2.4TB (estimated). Error log is attached. Please help!! Best wishes, Chris error.pdf
Archived
This topic is now archived and is closed to further replies.