Joe L. Posted August 19, 2011 Share Posted August 19, 2011 Please if someone could help, this is my second try at rebuilding parity & expanding the array after replacing a 1TB drive with a 3 TB. It starts up, says it will take 700 minutes to complete, after two hours the web panel is still accessible, I leave it overnight, and in the morning the machine is non responsive. IF I reset it the whole rebuilding starts over. Not to say there is something going wrong, but 700 minutes = 11.66 hours. (more than 2 hours, and perhaps more than just overnight) Only way to know what is happening is to capture a copy of the syslog, zip it (they compress well) and attach it to your next post. Quote Link to comment
dandirk Posted August 19, 2011 Share Posted August 19, 2011 I ran into just a slight problem with the setup. Installed SS as per your post, everything went fine. When I go to set it up, it asks for a playlist directory. So I created a new folder on my user share, within SS went to /mnt/Share/Storage and the folder is not listed. I tried to stop/start SS, no go. I stopped the array, rebooted. No go the folder still does not appear... Not a big deal, just selected an existing dir. Here is the syslog from the gui.. I figured out my issue... I had to set a new path before running slimserver for the first time... For some reason if I messed it up, I had to delete the slimserver folder from plugins and reinstall and try again before it would work properly (damn linux and case sensitive paths lol). Quote Link to comment
speeding_ant Posted August 19, 2011 Share Posted August 19, 2011 Please if someone could help, this is my second try at rebuilding parity & expanding the array after replacing a 1TB drive with a 3 TB. It starts up, says it will take 700 minutes to complete, after two hours the web panel is still accessible, I leave it overnight, and in the morning the machine is non responsive. IF I reset it the whole rebuilding starts over. I believe if you are expanding the array with parity protection, everything will be unresponsive until it is finished. Quote Link to comment
brent112 Posted August 20, 2011 Share Posted August 20, 2011 I had a kernel error when stopping the array. Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: Oops: 0000 [#1] SMP Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/host6/target6:0:0/6:0:0:0/block/sdg/stat Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: Process umount (pid: 29823, ti=dc892000 task=f77ff1b0 task.ti=dc892000) Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: Stack: Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: Call Trace: Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion 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 a9 e6 ff ff 85 c0 74 08 Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: EIP: [<c103819d>] queue_delayed_work_on+0x33/0xbf SS:ESP 0068:dc893e38 Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: CR2: 0000000000000000 Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: Oops: 0002 [#2] SMP Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/host6/target6:0:0/6:0:0:0/block/sdg/stat Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: Process mdrecoveryd (pid: 2238, ti=f7680000 task=f6e31730 task.ti=f7680000) Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: Stack: Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: Call Trace: Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: Code: eb f6 5d c3 55 89 e5 9c 59 fa ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 f3 90 8a 10 eb f6 89 c8 5d c3 55 89 e5 fa ba 00 01 00 00 <f0> 66 0f c1 10 38 f2 74 06 f3 90 8a 10 eb f6 5d c3 55 89 e5 fe Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: EIP: [<c131ffdf>] _raw_spin_lock_irq+0x9/0x1a SS:ESP 0068:f7681e18 Message from syslogd@Orion at Sat Aug 20 05:36:18 2011 ... Orion kernel: CR2: 0000000000000040 Quote Link to comment
Interstellar Posted August 20, 2011 Share Posted August 20, 2011 Tom, What is your plan regarding the Realtek drivers? Clearly for me and many others the r8168 are the way forward, but for others the r8169 is required. If there is to r8170 or newer then the only options are: A. Let the user choose the driver. B. Fix whatever is wrong with either driver set. Personally I can't move past b10 if you keep the r8169 driver! Quote Link to comment
BRiT Posted August 20, 2011 Share Posted August 20, 2011 If the manufacturer and Linux NIC device driver writers can't even get the drivers correct, I have high doubts that anyone outside those 2 groups would be able to do anything meaningful. You also missed listing the easiest fix option: C) User replaces faulty NIC with reliable NIC Quote Link to comment
Joe L. Posted August 20, 2011 Share Posted August 20, 2011 Or... since some chipsets seem to work with one driver, and not the other, and the drivers are loadable modules, have the alternate driver available for download. Then one or two lines in the go script will load the one that will work for a given chipset. Quote Link to comment
meep Posted August 20, 2011 Share Posted August 20, 2011 Since updated to 5.0 beta 10 and now this beta 11 (from beta 6) I have noticed a significant slowdown accessing unRAID shares over AFP from OSX Clients (Snow Leopard). AFP was a little slower than SMB previously but now there is a 15-20 second wait from clicking on a share / sub-directory to the file listing displaying. Peter Quote Link to comment
Interstellar Posted August 20, 2011 Share Posted August 20, 2011 If the manufacturer and Linux NIC device driver writers can't even get the drivers correct, I have high doubts that anyone outside those 2 groups would be able to do anything meaningful. You also missed listing the easiest fix option: C) User replaces faulty NIC with reliable NIC There is absolutely no reason why people with a perfectly working NIC like mine, should go out and buy a new NIC. It's not a faulty NIC at all. It works perfectly with driver r8168. I hope the official line is a little better than that!!! Quote Link to comment
sunnyville Posted August 20, 2011 Share Posted August 20, 2011 Please if someone could help, this is my second try at rebuilding parity & expanding the array after replacing a 1TB drive with a 3 TB. It starts up, says it will take 700 minutes to complete, after two hours the web panel is still accessible, I leave it overnight, and in the morning the machine is non responsive. IF I reset it the whole rebuilding starts over. I believe if you are expanding the array with parity protection, everything will be unresponsive until it is finished. ok well in that case, I shall wait to see if it becomes accessible again! Quote Link to comment
BRiT Posted August 20, 2011 Share Posted August 20, 2011 There is absolutely no reason why people with a perfectly working NIC like mine, should go out and buy a new NIC. It's not a faulty NIC at all. It works perfectly with driver r8168. I hope the official line is a little better than that!!! I'm not venting at you, I'm venting at Realtek because they're incapable of making a single driver package that supports all their current products. In that regards I consider it, the NIC, from a holistic approach to be faulty. Anything which needs special and delicate care I consider to be faulty. Their past hardware needed special care. Their current hardware needs special care. How is that not some kind of faulty? Of course, as Joe L pointed out, if indeed both drivers are modules and are not mutually exclusive , then perhaps Limetech can build and include both, then selectively load the proper one via a configuration setting at boot time. Quote Link to comment
gerhard911 Posted August 20, 2011 Share Posted August 20, 2011 Anything which needs special and delicate care I consider to be faulty. There is no need to drag wives and girlfriends into this discussion. Quote Link to comment
BRiT Posted August 20, 2011 Share Posted August 20, 2011 Anything which needs special and delicate care I consider to be faulty. There is no need to drag wives and girlfriends into this discussion. Perfect examples of faulty... Quote Link to comment
DoeBoye Posted August 20, 2011 Share Posted August 20, 2011 Anything which needs special and delicate care I consider to be faulty. There is no need to drag wives and girlfriends into this discussion. Perfect examples of faulty... 10 foot pole... Check. Backing away slowly... Check. .... Oh... Look! Someone's having share security problems over there. What's that? ... OK! I'll be right over! Quote Link to comment
Joe L. Posted August 20, 2011 Share Posted August 20, 2011 Anything which needs special and delicate care I consider to be faulty. There is no need to drag wives and girlfriends into this discussion. Perfect examples of faulty... I think there is another post needing my attention too... Yes... there it is... a discussion on fan spin-direction and how it relates to case color... Joe L. Quote Link to comment
Interstellar Posted August 20, 2011 Share Posted August 20, 2011 There is absolutely no reason why people with a perfectly working NIC like mine, should go out and buy a new NIC. It's not a faulty NIC at all. It works perfectly with driver r8168. I hope the official line is a little better than that!!! I'm not venting at you, I'm venting at Realtek because they're incapable of making a single driver package that supports all their current products. In that regards I consider it, the NIC, from a holistic approach to be faulty. Anything which needs special and delicate care I consider to be faulty. Their past hardware needed special care. Their current hardware needs special care. How is that not some kind of faulty? Of course, as Joe L pointed out, if indeed both drivers are modules and are not mutually exclusive , then perhaps Limetech can build and include both, then selectively load the proper one via a configuration setting at boot time. Fair enough However, you could argue that most PC add-on cards have the same problems time to time. My 4870 runs better with a driver from 2010 than it does 2011, so does that mean thats faulty? The way forward here is either let the user decide (less hassle) or let the system detect the correct driver. Quote Link to comment
crazytony Posted August 21, 2011 Share Posted August 21, 2011 Upgraded from 10b6 to 10b11 by copying to a fresh USB stick and replacing the bzroot and bzimage. Unraid boots and shows a valid configuration but I'm seeing "File sytem type: unknown" for all disks. All disks have the expected "MBR: unaligned" message (none are unknown or error). The syslog looks nice and clean: no errors or warnings. Is this a safe configuration to start? Normally I would just test this out by mounting the disk outside of the array (mount -t reiserfs /dev/sdc1 /tmp/lolol) but a little birdy is telling me that will confuse the parity when the system comes back online. The only thread I could find that was related was: http://lime-technology.com/forum/index.php?topic=14158.msg135124#msg135124. But I think he had a set of bad disks . I don't really want to run fixmbr unless I must. Update: all good -- mounted, started and ran a parity check (check only) 0 errors. Quote Link to comment
Interstellar Posted August 21, 2011 Share Posted August 21, 2011 Mine comes up with file system unknown when the array is stopped but the server runs fine, I think it's because it's not mounted so it doesn't know what it is formatted. The big issue that Tom is having is the bug that causes the alignment to become unknown, but if all your drives are showing as OK on that front then it is fine IMO. Quote Link to comment
Joe L. Posted August 21, 2011 Share Posted August 21, 2011 I just got the same kernel OOps.. when I tried to stop the array on beta11. Aug 21 08:44:46 Tower2 kernel: BUG: unable to handle kernel NULL pointer dereference at 00000040 Aug 21 08:44:46 Tower2 kernel: IP: [<c131ffdf>] _raw_spin_lock_irq+0x9/0x1a Aug 21 08:44:46 Tower2 kernel: *pdpt = 0000000034ef1001 *pde = 0000000000000000 Aug 21 08:44:46 Tower2 kernel: Oops: 0002 [#1] SMP Aug 21 08:44:46 Tower2 kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.0/host8/target8:0:0/8:0:0:0/block/sdd/stat Aug 21 08:44:46 Tower2 kernel: Modules linked in: ntfs md_mod xor pata_jmicron sata_sil i2c_i801 r8169 jmicron i2c_core ahci libahci Aug 21 08:44:46 Tower2 kernel: Aug 21 08:44:46 Tower2 kernel: Pid: 1897, comm: mdrecoveryd Tainted: G W 2.6.37.6-unRAID #4 Supermicro C2SEA/C2SEA Aug 21 08:44:46 Tower2 kernel: EIP: 0060:[<c131ffdf>] EFLAGS: 00010093 CPU: 0 Aug 21 08:44:46 Tower2 kernel: EIP is at _raw_spin_lock_irq+0x9/0x1a Aug 21 08:44:46 Tower2 kernel: EAX: 00000040 EBX: 00000000 ECX: 00000000 EDX: 00000100 Aug 21 08:44:46 Tower2 kernel: ESI: 00000000 EDI: 00000000 EBP: f752fe18 ESP: f752fe18 Aug 21 08:44:46 Tower2 kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Aug 21 08:44:46 Tower2 kernel: Process mdrecoveryd (pid: 1897, ti=f752e000 task=f0234d40 task.ti=f752e000) Aug 21 08:44:46 Tower2 kernel: Stack: Aug 21 08:44:46 Tower2 kernel: f752fe74 f84f3833 00000004 c131f3aa 00000000 f752fe34 c131f382 f752fe48 Aug 21 08:44:46 Tower2 kernel: c109604e 00000040 00000000 00000000 f752fe68 c10960b2 00000fff 00000000 Aug 21 08:44:46 Tower2 kernel: 00000000 00000000 00000000 f75b9028 00000000 00000000 f75b9028 f752fe88 Aug 21 08:44:46 Tower2 kernel: Call Trace: Aug 21 08:44:46 Tower2 kernel: [<f84f3833>] ? get_active_stripe+0x32/0x3a8 [md_mod] Aug 21 08:44:46 Tower2 kernel: [<c131f3aa>] ? __mutex_unlock_slowpath+0x26/0x2c Aug 21 08:44:46 Tower2 kernel: [<c131f382>] ? mutex_unlock+0x14/0x16 Aug 21 08:44:46 Tower2 kernel: [<c109604e>] ? vfs_fsync_range+0x4d/0x5e Aug 21 08:44:46 Tower2 kernel: [<c10960b2>] ? generic_write_sync+0x53/0x62 Aug 21 08:44:46 Tower2 kernel: [<f84f3bb7>] ? unraid_sync+0xe/0x42 [md_mod] Aug 21 08:44:46 Tower2 kernel: [<f84efb48>] ? md_do_sync+0x14c/0x3b4 [md_mod] Aug 21 08:44:46 Tower2 kernel: [<f84f00f1>] ? write_file+0xb1/0xdd [md_mod] Aug 21 08:44:46 Tower2 kernel: [<c107c256>] ? do_sync_write+0x0/0xc5 Aug 21 08:44:46 Tower2 kernel: [<f84f02b7>] ? md_do_recovery+0x115/0x197 [md_mod] Aug 21 08:44:46 Tower2 kernel: [<f84f02b7>] ? md_do_recovery+0x115/0x197 [md_mod] Aug 21 08:44:46 Tower2 kernel: [<f84f0948>] ? md_thread+0xd6/0xed [md_mod] Aug 21 08:44:46 Tower2 kernel: [<c103b5c5>] ? autoremove_wake_function+0x0/0x2f Aug 21 08:44:46 Tower2 kernel: [<f84f0872>] ? md_thread+0x0/0xed [md_mod] Aug 21 08:44:46 Tower2 kernel: [<c103b2ca>] ? kthread+0x62/0x67 Aug 21 08:44:46 Tower2 kernel: [<c103b268>] ? kthread+0x0/0x67 Aug 21 08:44:46 Tower2 kernel: [<c1002cf6>] ? kernel_thread_helper+0x6/0x10 Aug 21 08:44:46 Tower2 kernel: Code: eb f6 5d c3 55 89 e5 9c 59 fa ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 f3 90 8a 10 eb f6 89 c8 5d c3 55 89 e5 fa ba 00 01 00 00 <f0> 66 0f c1 10 38 f2 74 06 f 3 90 8a 10 eb f6 5d c3 55 89 e5 fe Aug 21 08:44:46 Tower2 kernel: EIP: [<c131ffdf>] _raw_spin_lock_irq+0x9/0x1a SS:ESP 0068:f752fe18 Aug 21 08:44:46 Tower2 kernel: CR2: 0000000000000040 Aug 21 08:44:46 Tower2 kernel: ---[ end trace a5bc7a30721d0267 ]--- Aug 21 08:44:46 Tower2 emhttp: shcmd (69): rmmod md-mod |& logger Aug 21 08:44:46 Tower2 emhttp: shcmd (70): udevadm settle Aug 21 08:44:46 Tower2 kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Aug 21 08:44:46 Tower2 kernel: IP: [<c103f9d0>] exit_creds+0xc/0x72 Aug 21 08:44:46 Tower2 kernel: *pdpt = 000000002054a001 *pde = 0000000000000000 Aug 21 08:44:46 Tower2 kernel: Oops: 0000 [#2] SMP Aug 21 08:44:46 Tower2 kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.0/host8/target8:0:0/8:0:0:0/block/sdd/stat Aug 21 08:44:46 Tower2 kernel: Modules linked in: ntfs md_mod(-) xor pata_jmicron sata_sil i2c_i801 r8169 jmicron i2c_core ahci libahci Aug 21 08:44:46 Tower2 kernel: Aug 21 08:44:46 Tower2 kernel: Pid: 20950, comm: rmmod Tainted: G D W 2.6.37.6-unRAID #4 Supermicro C2SEA/C2SEA Aug 21 08:44:46 Tower2 kernel: EIP: 0060:[<c103f9d0>] EFLAGS: 00210202 CPU: 0 Aug 21 08:44:46 Tower2 kernel: EIP is at exit_creds+0xc/0x72 Aug 21 08:44:46 Tower2 kernel: EAX: 00000000 EBX: f0234d40 ECX: 40000040 EDX: 00800072 Aug 21 08:44:46 Tower2 kernel: ESI: 00000009 EDI: 00000000 EBP: f68c1f04 ESP: f68c1f00 Aug 21 08:44:46 Tower2 kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Aug 21 08:44:46 Tower2 kernel: Process rmmod (pid: 20950, ti=f68c0000 task=f01f0000 task.ti=f68c0000) Aug 21 08:44:46 Tower2 kernel: Stack: Aug 21 08:44:46 Tower2 kernel: f0234d40 f68c1f10 c1028797 f0234d40 f68c1f20 c103b3d8 efa07140 00000880 Aug 21 08:44:46 Tower2 kernel: f68c1f2c f84f0656 f75b8000 f68c1f40 f84f0679 f84f57a8 00000880 00000000 Aug 21 08:44:46 Tower2 kernel: f68c1f48 f84f3e16 f68c1fac c104ac0a 6d5f646d 0000646f b776e840 f4f8e6c0 Aug 21 08:44:46 Tower2 kernel: Call Trace: Aug 21 08:44:46 Tower2 kernel: [<c1028797>] ? __put_task_struct+0x54/0x78 Aug 21 08:44:46 Tower2 kernel: [<c103b3d8>] ? kthread_stop+0x45/0x4b Aug 21 08:44:46 Tower2 kernel: [<f84f0656>] ? md_unregister_thread+0x2c/0x38 [md_mod] Aug 21 08:44:46 Tower2 kernel: [<f84f0679>] ? free_mddev+0x17/0x5d [md_mod] Aug 21 08:44:46 Tower2 kernel: [<f84f3e16>] ? md_exit+0x3a/0x4a [md_mod] Aug 21 08:44:46 Tower2 kernel: [<c104ac0a>] ? sys_delete_module+0x16f/0x1c0 Aug 21 08:44:46 Tower2 kernel: [<c106de6d>] ? remove_vma+0x41/0x47 Aug 21 08:44:46 Tower2 kernel: [<c106ec0d>] ? do_munmap+0x217/0x231 Aug 21 08:44:46 Tower2 kernel: [<c1320325>] ? syscall_call+0x7/0xb Aug 21 08:44:46 Tower2 kernel: Code: 83 b4 01 00 00 89 83 b8 01 00 00 31 d2 eb 0a e8 bc fd ff ff ba ea ff ff ff 89 d0 5b 5e 5d c3 55 89 e5 53 89 c3 8b 80 b8 01 00 00 <8b> 00 8b 83 b4 01 00 00 c7 8 3 b4 01 00 00 00 00 00 00 f0 ff 08 Aug 21 08:44:46 Tower2 kernel: EIP: [<c103f9d0>] exit_creds+0xc/0x72 SS:ESP 0068:f68c1f00 Aug 21 08:44:46 Tower2 kernel: CR2: 0000000000000000 Aug 21 08:44:46 Tower2 kernel: ---[ end trace a5bc7a30721d0268 ]--- Aug 21 08:44:46 Tower2 emhttp: Device inventory: Aug 21 08:44:46 Tower2 emhttp: ST31500341AS_9VS4F16T (sda) 1465138584 Aug 21 08:44:46 Tower2 emhttp: Hitachi_HDS722020ALA330_JK1130YAG162AT (sdc) 1953514584 Aug 21 08:44:46 Tower2 emhttp: Hitachi_HDS722020ALA330_JK11A1YAJBBMAV (sdb) 1953514584 Aug 21 08:44:46 Tower2 emhttp: Hitachi_HDS722020ALA330_JK1130YAG6XPMT (sde) 1953514584 Aug 21 08:44:46 Tower2 emhttp: Hitachi_HDS5C3020ALA632_ML0220F30DMUZD (sdf) 1953514584 Aug 21 08:44:46 Tower2 emhttp: ST31500341AS_9VS1BVX8 (sdg) 1465138584 Aug 21 08:44:46 Tower2 emhttp: ST31500341AS_9VS069T8 (sdh) 1465138584 Aug 21 08:44:46 Tower2 emhttp: ST31500341AS_9VS0G9D8 (sdi) 1465138584 Aug 21 08:44:46 Tower2 emhttp: Hitachi_HDS722020ALA330_JK1101YAH0EAEV (sdk) 1953514584 Aug 21 08:44:46 Tower2 emhttp: Hitachi_HDS5C3020ALA632_ML0220F30XR4ED (sdj) 1953514584 Aug 21 08:44:46 Tower2 emhttp: Hitachi_HDS5C3020ALA632_ML0220F30XGTPD (sdl) 1953514584 Aug 21 08:44:46 Tower2 emhttp: shcmd (71): modprobe md-mod super=/boot/config/super.dat slots=21 |& logger Quote Link to comment
Yorgo Posted August 21, 2011 Share Posted August 21, 2011 Upgraded from 10b6 to 10b11 by copying to a fresh USB stick and replacing the bzroot and bzimage. Unraid boots and shows a valid configuration but I'm seeing "File sytem type: unknown" for all disks. All disks have the expected "MBR: unaligned" message (none are unknown or error). The syslog looks nice and clean: no errors or warnings. Is this a safe configuration to start? Normally I would just test this out by mounting the disk outside of the array (mount -t reiserfs /dev/sdc1 /tmp/lolol) but a little birdy is telling me that will confuse the parity when the system comes back online. The only thread I could find that was related was: http://lime-technology.com/forum/index.php?topic=14158.msg135124#msg135124. But I think he had a set of bad disks . I don't really want to run fixmbr unless I must. I've experienced the same thing and it seems to be fine. Once the array is started, file system type diplays the correct type (ie, reiserfs). Y Quote Link to comment
Yorgo Posted August 21, 2011 Share Posted August 21, 2011 There is absolutely no reason why people with a perfectly working NIC like mine, should go out and buy a new NIC. It's not a faulty NIC at all. It works perfectly with driver r8168. I hope the official line is a little better than that!!! I'm not venting at you, I'm venting at Realtek because they're incapable of making a single driver package that supports all their current products. In that regards I consider it, the NIC, from a holistic approach to be faulty. Anything which needs special and delicate care I consider to be faulty. Their past hardware needed special care. Their current hardware needs special care. How is that not some kind of faulty? Of course, as Joe L pointed out, if indeed both drivers are modules and are not mutually exclusive , then perhaps Limetech can build and include both, then selectively load the proper one via a configuration setting at boot time. That would be great. Hopefully it's doable and something that can be implemented easily. Y Quote Link to comment
cpshoemake Posted August 22, 2011 Share Posted August 22, 2011 How close are we getting to a final release build for 5.0? All these new features are so tempting, but I fear for my data. Quote Link to comment
xamindar Posted August 22, 2011 Share Posted August 22, 2011 Does anyone know where the php.ini file is that emhttp in this beta uses? Nevermind, looks like it is /etc/httpd/php.ini-dist Quote Link to comment
xamindar Posted August 22, 2011 Share Posted August 22, 2011 When I click on a data drive it says: Partition format: MBR: unaligned File sytem type: unknown Is it supposed to say filesystem type unknown? Other than that, the main page states my configuration is valid. This was from upgrading from 4.5.4 to 4.7, verifying it still works, than then upgrading to 5.0 beta 11. EDIT: I guess I need to go to bed I see this was already answered just above. Sorry guys. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.