Stoke192

Ok, That works, not ideal as it requires both pc and server running but it establishes that it's the mounting of the .iso and not the playing of the video that's the problem. A work around non the less though until Syabas/Sigma sort out the mounting issue. Is there a addon/plugin or some other way to mount blu-ray .iso's within unraid ? Thanks for the suggestion.

Nice!!, can't wait to try this out, Thank you both for your hard work. Cheers

I knew there'd be a reason.... I will try mounting with Virtual Clone Drive though as i was thinking of trying that earlier. Thanks for the replys

Hi, I've got a PCH-A400 which is having trouble atm playing 3DBD.iso's due to it's current firmware, Now apparently if you get your NAS to mount the .iso and then browse to it on the A400, it'll play, as i said apparently but nothing ventured, nothing gained....as they say. I've done a search which came up with ShareIso within unmenu, i've tried this and it gives me errors saying it can't identify CD-ROM format and also missing code page. Is there something else i need to install or is there a different way of going about this in the latest version of unraid ? I'm obviously missing something being a unraid noob, So any help would be appreciated to get this work around for the A400 working. Currently using v5 rc11 Thanks Feb 16 00:21:56 Tower dhcpcd[1081]: eth0: renewing lease of 192.168.0.14 Feb 16 00:21:57 Tower dhcpcd[1081]: eth0: acknowledged 192.168.0.14 from 192.168.0.1 Feb 16 00:21:57 Tower dhcpcd[1081]: eth0: leased 192.168.0.14 for 86400 seconds Feb 16 00:32:24 Tower emhttp: get_filesystem_status: statfs: /mnt/user/tmp No such file or directory Feb 16 00:32:28 Tower last message repeated 2 times Feb 16 00:32:28 Tower logger: Enter sleep mode Feb 16 19:37:37 Tower kernel: PM: Syncing filesystems ... done. Feb 16 19:37:37 Tower kernel: Freezing user space processes ... (elapsed 0.01 seconds) done. Feb 16 19:37:37 Tower kernel: Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done. Feb 16 19:37:37 Tower kernel: Suspending console(s) (use no_console_suspend to debug) Feb 16 19:37:37 Tower kernel: sd 8:0:0:0: [sdh] Synchronizing SCSI cache Feb 16 19:37:37 Tower kernel: sd 6:0:0:0: [sdg] Synchronizing SCSI cache Feb 16 19:37:37 Tower kernel: sd 8:0:0:0: [sdh] Stopping disk Feb 16 19:37:37 Tower kernel: sd 5:0:0:0: [sdf] Synchronizing SCSI cache Feb 16 19:37:37 Tower kernel: sd 6:0:0:0: [sdg] Stopping disk Feb 16 19:37:37 Tower kernel: sd 4:0:0:0: [sde] Synchronizing SCSI cache Feb 16 19:37:37 Tower kernel: sd 5:0:0:0: [sdf] Stopping disk Feb 16 19:37:37 Tower kernel: sd 4:0:0:0: [sde] Stopping disk Feb 16 19:37:37 Tower kernel: sd 3:0:0:0: [sdd] Synchronizing SCSI cache Feb 16 19:37:37 Tower kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache Feb 16 19:37:37 Tower kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache Feb 16 19:37:37 Tower kernel: sd 2:0:0:0: [sdc] Stopping disk Feb 16 19:37:37 Tower kernel: sd 3:0:0:0: [sdd] Stopping disk Feb 16 19:37:37 Tower kernel: sd 1:0:0:0: [sdb] Stopping disk Feb 16 19:37:37 Tower kernel: serial 00:08: disabled Feb 16 19:37:37 Tower kernel: serial 00:08: wake-up capability disabled by ACPI Feb 16 19:37:37 Tower kernel: parport_pc 00:06: disabled Feb 16 19:37:37 Tower kernel: ACPI handle has no context! Feb 16 19:37:37 Tower kernel: pci 0000:00:14.4: wake-up capability enabled by ACPI Feb 16 19:37:37 Tower kernel: PM: suspend of devices complete after 979.739 msecs Feb 16 19:37:37 Tower kernel: PM: late suspend of devices complete after 0.219 msecs Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:14.5: wake-up capability enabled by ACPI Feb 16 19:37:37 Tower kernel: ehci_hcd 0000:00:13.2: wake-up capability enabled by ACPI Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:13.1: wake-up capability enabled by ACPI Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:13.0: wake-up capability enabled by ACPI Feb 16 19:37:37 Tower kernel: ehci_hcd 0000:00:12.2: wake-up capability enabled by ACPI Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:12.1: wake-up capability enabled by ACPI Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:12.0: wake-up capability enabled by ACPI Feb 16 19:37:37 Tower kernel: PM: noirq suspend of devices complete after 36.721 msecs Feb 16 19:37:37 Tower kernel: ACPI: Preparing to enter system sleep state S3 Feb 16 19:37:37 Tower kernel: PM: Saving platform NVS memory Feb 16 19:37:37 Tower kernel: Disabling non-boot CPUs ... Feb 16 19:37:37 Tower kernel: CPU 1 is now offline Feb 16 19:37:37 Tower kernel: Extended CMOS year: 2000 Feb 16 19:37:37 Tower kernel: ACPI: Low-level resume complete Feb 16 19:37:37 Tower kernel: PM: Restoring platform NVS memory Feb 16 19:37:37 Tower kernel: LVT offset 0 assigned for vector 0xf9 Feb 16 19:37:37 Tower kernel: Extended CMOS year: 2000 Feb 16 19:37:37 Tower kernel: Enabling non-boot CPUs ... Feb 16 19:37:37 Tower kernel: Booting Node 0 Processor 1 APIC 0x1 Feb 16 19:37:37 Tower kernel: Initializing CPU#1 Feb 16 19:37:37 Tower kernel: [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu Feb 16 19:37:37 Tower kernel: perf: IBS APIC setup failed on cpu #1 Feb 16 19:37:37 Tower kernel: CPU1 is up Feb 16 19:37:37 Tower kernel: ACPI: Waking up from system sleep state S3 Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:12.0: wake-up capability disabled by ACPI Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:12.1: wake-up capability disabled by ACPI Feb 16 19:37:37 Tower kernel: ehci_hcd 0000:00:12.2: wake-up capability disabled by ACPI Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:13.0: wake-up capability disabled by ACPI Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:13.1: wake-up capability disabled by ACPI Feb 16 19:37:37 Tower kernel: ehci_hcd 0000:00:13.2: wake-up capability disabled by ACPI Feb 16 19:37:37 Tower kernel: ohci_hcd 0000:00:14.5: wake-up capability disabled by ACPI Feb 16 19:37:37 Tower kernel: PM: noirq resume of devices complete after 93.760 msecs Feb 16 19:37:37 Tower kernel: PM: early resume of devices complete after 0.131 msecs Feb 16 19:37:37 Tower kernel: pci 0000:00:14.4: wake-up capability disabled by ACPI Feb 16 19:37:37 Tower kernel: parport_pc 00:06: activated Feb 16 19:37:37 Tower kernel: serial 00:08: activated Feb 16 19:37:37 Tower kernel: ata7: SATA link down (SStatus 0 SControl 300) Feb 16 19:37:37 Tower kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Feb 16 19:37:37 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:37:37 Tower kernel: ata8.00: configured for UDMA/133 Feb 16 19:37:37 Tower kernel: sd 8:0:0:0: [sdh] Starting disk Feb 16 19:37:37 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:37:37 Tower kernel: ata3.00: configured for UDMA/133 Feb 16 19:37:37 Tower kernel: sd 3:0:0:0: [sdd] Starting disk Feb 16 19:37:37 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:37:37 Tower kernel: ata4.00: configured for UDMA/133 Feb 16 19:37:37 Tower kernel: sd 4:0:0:0: [sde] Starting disk Feb 16 19:37:37 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:37:37 Tower kernel: ata2.00: configured for UDMA/133 Feb 16 19:37:37 Tower kernel: sd 2:0:0:0: [sdc] Starting disk Feb 16 19:37:37 Tower kernel: ata1: softreset failed (device not ready) Feb 16 19:37:37 Tower kernel: ata6: softreset failed (device not ready) Feb 16 19:37:37 Tower kernel: ata5: softreset failed (device not ready) Feb 16 19:37:37 Tower kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:37:37 Tower kernel: ata6.00: configured for UDMA/133 Feb 16 19:37:37 Tower kernel: sd 6:0:0:0: [sdg] Starting disk Feb 16 19:37:37 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:37:37 Tower kernel: ata1.00: configured for UDMA/133 Feb 16 19:37:37 Tower kernel: sd 1:0:0:0: [sdb] Starting disk Feb 16 19:37:37 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 16 19:37:37 Tower kernel: ata5.00: configured for UDMA/133 Feb 16 19:37:37 Tower kernel: sd 5:0:0:0: [sdf] Starting disk Feb 16 19:37:37 Tower kernel: PM: resume of devices complete after 14047.796 msecs Feb 16 19:37:37 Tower kernel: Restarting tasks ... mdcmd (65): spindown 0 Feb 16 19:37:37 Tower kernel: done. Feb 16 19:37:37 Tower logger: Wake-up from sleep mode Feb 16 19:37:37 Tower kernel: mdcmd (66): spindown 1 Feb 16 19:37:38 Tower kernel: mdcmd (67): spindown 2 Feb 16 19:37:38 Tower kernel: mdcmd (68): spindown 3 Feb 16 19:37:39 Tower kernel: mdcmd (69): spindown 4 Feb 16 19:37:40 Tower kernel: mdcmd (70): spindown 5 Feb 16 19:37:41 Tower emhttp: get_filesystem_status: statfs: /mnt/user/tmp No such file or directory Feb 16 19:37:41 Tower emhttp: get_filesystem_status: statfs: /mnt/user/tmp No such file or directory Feb 16 19:38:09 Tower crond[1216]: time disparity of 1145 minutes detected Feb 16 19:38:47 Tower emhttp: get_filesystem_status: statfs: /mnt/user/tmp No such file or directory Feb 16 19:39:00 Tower last message repeated 6 times Feb 16 19:39:04 Tower emhttp: shcmd (71): /usr/local/sbin/set_ncq sdf 1 &> /dev/null Feb 16 19:39:04 Tower emhttp: shcmd (72): /usr/local/sbin/set_ncq sdb 1 &> /dev/null Feb 16 19:39:04 Tower emhttp: shcmd (73): /usr/local/sbin/set_ncq sdd 1 &> /dev/null Feb 16 19:39:04 Tower emhttp: shcmd (74): /usr/local/sbin/set_ncq sdc 1 &> /dev/null Feb 16 19:39:04 Tower emhttp: shcmd (75): /usr/local/sbin/set_ncq sde 1 &> /dev/null Feb 16 19:39:04 Tower emhttp: shcmd (76): /usr/local/sbin/set_ncq sdg 1 &> /dev/null Feb 16 19:39:04 Tower emhttp: shcmd (77): /usr/local/sbin/set_ncq sdh 1 &> /dev/null Feb 16 19:39:04 Tower kernel: mdcmd (71): set md_num_stripes 1280 Feb 16 19:39:04 Tower kernel: mdcmd (72): set md_write_limit 768 Feb 16 19:39:04 Tower kernel: mdcmd (73): set md_sync_window 384 Feb 16 19:39:04 Tower kernel: mdcmd (74): set spinup_group 0 0 Feb 16 19:39:04 Tower kernel: mdcmd (75): set spinup_group 1 0 Feb 16 19:39:04 Tower kernel: mdcmd (76): set spinup_group 2 0 Feb 16 19:39:04 Tower kernel: mdcmd (77): set spinup_group 3 0 Feb 16 19:39:04 Tower kernel: mdcmd (78): set spinup_group 4 0 Feb 16 19:39:04 Tower kernel: mdcmd (79): set spinup_group 5 0 Feb 16 19:39:04 Tower emhttp: get_filesystem_status: statfs: /mnt/user/tmp No such file or directory Feb 16 19:39:13 Tower last message repeated 5 times Feb 16 19:41:22 Tower kernel: ISOFS: Unable to identify CD-ROM format. Feb 16 19:41:22 Tower unmenu[4245]: mount: wrong fs type, bad option, bad superblock on /dev/loop0, Feb 16 19:41:22 Tower unmenu[4245]: missing codepage or helper program, or other error Feb 16 19:41:22 Tower unmenu[4245]: In some cases useful info is found in syslog - try Feb 16 19:41:22 Tower unmenu[4245]: dmesg | tail or so Feb 16 19:41:22 Tower unmenu[4245]: Feb 16 19:41:39 Tower kernel: ISOFS: Unable to identify CD-ROM format. Feb 16 19:41:39 Tower unmenu[4245]: mount: wrong fs type, bad option, bad superblock on /dev/loop0, Feb 16 19:41:39 Tower unmenu[4245]: missing codepage or helper program, or other error Feb 16 19:41:39 Tower unmenu[4245]: In some cases useful info is found in syslog - try Feb 16 19:41:39 Tower unmenu[4245]: dmesg | tail or so Feb 16 19:41:39 Tower unmenu[4245]: Feb 16 19:42:36 Tower kernel: ISOFS: Unable to identify CD-ROM format. Feb 16 19:42:36 Tower unmenu[4245]: mount: wrong fs type, bad option, bad superblock on /dev/loop0, Feb 16 19:42:36 Tower unmenu[4245]: missing codepage or helper program, or other error Feb 16 19:42:36 Tower unmenu[4245]: In some cases useful info is found in syslog - try Feb 16 19:42:36 Tower unmenu[4245]: dmesg | tail or so Feb 16 19:42:36 Tower unmenu[4245]: Feb 16 19:45:10 Tower emhttp: get_filesystem_status: statfs: /mnt/user/tmp No such file or directory Feb 16 19:45:16 Tower last message repeated 2 times Feb 16 19:45:51 Tower kernel: ISOFS: Unable to identify CD-ROM format. Feb 16 19:45:51 Tower unmenu[4245]: mount: wrong fs type, bad option, bad superblock on /dev/loop0, Feb 16 19:45:51 Tower unmenu[4245]: missing codepage or helper program, or other error Feb 16 19:45:51 Tower unmenu[4245]: In some cases useful info is found in syslog - try Feb 16 19:45:51 Tower unmenu[4245]: dmesg | tail or so Feb 16 19:45:51 Tower unmenu[4245]: Feb 16 19:52:06 Tower emhttp: get_filesystem_status: statfs: /mnt/user/tmp No such file or directory Feb 16 19:52:37 Tower last message repeated 25 times

I'll also be interested in a guide to get this working, also how your getting on with it as i'll get the plus version if worth it. Thanks

Hi, Just a FYI The StarTech 2 port PCIe Internal Sata 2 Controller card (Part # PEXSATA221), Chipset : JMicron JMB363. Works within unRAID, shows connected drives as ide in the bios but after unRAID loads drivers they show as sata. I did a search for this card and nothing came back, so took a gamble and thankfully everything works ok. I'm using a Asus M5A 78L-M LX mobo and v5.0-rc5 btw. Cheers

Ok, thanks for the swift reply.

Hi, One of my drives (disk 1) is showing as MBR: unaligned its a new 2TB WDEARX.In SF it's showing as green and i can browse all the data on it. I only noticed after installing Rc5 and checking Partition format as per instructions.It was pre cleared and formatted with unraid as per instructions and showed no errors. Should i be concerned ? and is there a way to fix this should it be a problem ? Also, when i roll back to Rc4 it's the same. Thanks

I picked up a new Intel Pro1000 GT lan card for £7 delivered on ebay, so it wasn't the end of the world and as said solved the problem nicely, also as it was a PCI card so didn't take up any valuable PCIe slots required for future expansion.

Hi, I've the exact same setup, with the exception that the array (5TB) is made up of a WD 2TB and 3 Hitachi 1TB drives.I've just installed a WD 3TB Caviar Green Hard Drive WD30EZRX as a parity drive and as above all is working fine. What i will say though, is if you want to use the S3 sleep functions of Simple Features and WOL then you'll have to get a Intel network card as the onboard lan doesn't work once the server goes to sleep (driver problem apparently) have a look at this thread http://lime-technology.com/forum/index.php?topic=20230.0....but once Intel network card was installed WOL works without any probs. I've had the server up and running for about six weeks now without any probs and allows me to stream HD video to my various media players around the house. Have fun with your build

+2 Also, my server won't go to sleep automatically using the addon in Simple Features (i've disabled 'wait for network inactivity'), so once the drives spin down it should go to sleep but doesn't. I can force it to go to sleep and it does so quite happily, it'll wake with a magic packet also. Anyone else have this problem ? Thanks

My card turned up and worked also, just need to get my hdx to send a 'magic packet' to my server an everything would be sweet.

Cool, good to see it works, just grabbed a new one for 8 quid on ebay myself I take it you don't have any stuttering video probs with it being pci as apposed to pci-e, it's just that i had a few probs with stuttering 1080p video using a pci sata card rather than a pci-e one, but i suppose Gigabit is Gigabit regardless of the interface ?? Anyway, looking forward to the card arriving now as waking up my server from my HDX 1000 media player will be the icing on the cake for me, just need to setup the server to go to sleep after a hour or two of inactivity now lol. Cheers EDIT: Doh, just noticed the settings i require are in the 'Simple Features' settings page, solves that problem

Ok, Shame about the driver, but thanks for the effort anyway. Let me know how you get on with the new card, also where did you get it from as i'll order the same if it turns out to be ok. Cheers

Sorry, I can't help you out there but it doesn't sound good, let me know how you get on.

Hi, I never got a chance to try windows myself last night, but by the sounds of it it could be a driver issue with the realtek nic....there is a newer driver available (dated 13/3/2012) so it could be that.I will try to test over the weekend, but how you'd go about updating drivers in unraid (even if you could) is a closed book to me atm. If you go down the intel nic route, let me know how you get on as i'm keen to get WOL working as i like the idea of sending the 'magic packet' from my HDX1000 to wake my server. Cheers

Joe L. root@Tower2:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes I too get the same results when using the ethtool eth0 command.......I was also gonna try installing windows on a spare drive and see if WOL works under windows. Other than that, as Chris says very happy with it so far!!, apart from this sleep nigle

Thanks for the reply My bios settings are : Suspend mode : S3 only ACPI 2.0 : Enabled ACPI APIC : Enabled AMP Config Restore on ac power loss : last state Power on from S5 by PME# : enabled Power on frpm S5 ring : enabled Also...Onboard Lan boot rom : Enabled Are these settings correct as it still doesn't work ? and the lan port lights are still off. Thanks

HI, Thanks for the reply's and yes i'm using 5.0-rc3 basic. I've installed simple features and the S3 sleep button sends my server to sleep without any probs, but it won't wake back up again via the wol magic packet batch file posted on these forum's. It will wake up however if i press the power button and normal sevices are resumed. I have noticed that the lights on my lan port are inactive whilst sleeping, shouldn't they be active (waiting for wol signal) ? Also, do i need to configure the sleep script to enable this ?, if so, how do i go about it ? Thanks again

Hi, new user and first post, so be gentle. I just built my first unRAID server (using latest version) and everything is running fine, i've also installed unMENU and the powerdown script and they also are running fine.HDD's have been precleared, formatted and user shares set up.....so far so good. My mobo (Asus M5A78L-M LX V2) supports S3/WOL and i've configured the bios accordingly (i hope). Now, i'd like to send my server to sleep when not in use, ie, overnight and when i'm out at work during the day.I've read the various threads/how to's and my head is now spinning as i can't get it to work When i type the command : root@Tower:~# root@Tower:~# echo 3 >/proc/acpi/sleep I get this : -bash: /proc/acpi/sleep: No such file or directory root@Tower:~# Also i notice that in the "user scripts" tab of unMENU there's a button for putting your server to sleep but it has /proc/acpi/sleep: No such file or directory on it. I'm assuming that there's a script missing/not installed, so if someone could help a unRAID/Linux noob out i'd very much appreciate it. Thanks