jkeyser14

I get the following error when trying to install. I'm using unraid 4.5 and unmenu 1.2. Can anyone help? minidlna-1.0.22-i486-1.tgz installation: /boot/packages/minidlna-1.0.22-i486-1.tgz.manual_install: line 132: /minidlna-1.0.22-i486-1.tgz: No such file or directory tar-1.13: Cannot add file *: No such file or directory tar-1.13: Error exit delayed from previous errors Verifying package minidlna-1.0.22-i486-1Q.tgz. Installing package minidlna-1.0.22-i486-1Q.tgz: PACKAGE DESCRIPTION: WARNING: Package has not been created with 'makepkg' Package minidlna-1.0.22-i486-1Q.tgz installed. sed: can't read /boot/custom/minidlna/minidlnactl: No such file or directory sed: can't read /boot/custom/minidlna/minidlnactl: No such file or directory /boot/packages/minidlna-1.0.22-i486-1.tgz.manual_install: line 152: /boot/custom/minidlna/minidlnactl: No such file or directory minidlna daemon installed

SOLVED: I bought another drive and had no problem getting unraid back up and running. I tried putting the non-functional drive in another machine and it's toast. Must have gotten damaged by the power supply browning out?

but I can't log in at the console. Unraid never gets to a command prompt because it hangs on boot.

How do I get a system log the machine never turns on the network adapter and gets an IP? I don't even get a command. I get an endless loop of the messages above during boot.

I've been getting a lot of failed drives lately and thought I had just bought a bad batch of drives. I put in a replacement for my parity drive tonight. I booted up and started sync and that's when I noticed my fan speed changing and the hard drives seeking at the same time. I grabbed a meter and checked my power supply just to find out that it was browning out. I hit stop sync and did a graceful power down. I replaced the power supply and now unraid is hanging during boot. I can't get a syslog, but this message repeats continuously during boot (text copyied from a different post): Apr 18 19:42:37 storage kernel: ata3.00: status: { DRDY ERR } Apr 18 19:42:37 storage kernel: ata3.00: error: { UNC } Apr 18 19:42:37 storage kernel: ata3.00: configured for UDMA/133 Apr 18 19:42:37 storage kernel: ata3: EH complete Apr 18 19:56:14 storage kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 18 19:56:14 storage kernel: ata3.00: BMDMA stat 0x25 Apr 18 19:56:14 storage kernel: ata3.00: failed command: READ DMA EXT Apr 18 19:56:14 storage kernel: ata3.00: cmd 25/00:58:8f:c0:24/00:03:1c:00:00/e0 tag 0 dma 438272 in Apr 18 19:56:14 storage kernel: res 51/40:17:c0:c3:24/40:00:1c:00:00/e0 Emask 0x9 (media error) Apr 18 19:56:14 storage kernel: ata3.00: status: { DRDY ERR } Apr 18 19:56:14 storage kernel: ata3.00: error: { UNC } If I unplug the parity drive unraid boots fine and it just shows the drive as missing. If I plug the drive back in it goes back to repeating the above. I tried to move the drive to a different SATA port and no luck. Is there a way to make unraid think this is a new drive so I can restart the parity re-build?

I have been using windows 7 for about two months now and haven't run into any issues except one. If my wireless signal gets interrupted my music or video streams won't resume. I have to close the programs and restart them.