Ironcross

Members
  • Posts

    9
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Ironcross's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks for the update Tom. Much appreciated.
  2. Those only give me a bread: Cannot read the block (2): (Input/output error) message. I know the drives are good. I can even pull data from them using YaReg. Could it be the card? They are on the same card but different breakout cables.
  3. I am in need of some help. On Friday I had a drive (1.5TB) go down on my system. I replaced with a new drive (2TB) and started a rebuild on it. Everything went well until it seemed to stick at 97.7% complete. It stayed there for 5 hours. While researching the issue on the boards another disk became read only. The system then locked up before being able to retrieve another syslog. Attempts to use resierfsck on either drive give me the following result. bread: Cannot read the block (2): (Input/output error) I have checked my cables and power connections etc. Disk11 (the original, failed drive shows as DISK_INVALID and Disk12 (read only drive, shows as DISK_DSBL). Nothing I have found on the boards has been successful. System Config: Unraid 4.7 Add-ons: UnMenu APCUPSD slimserver Subsonic Supermicro C2SEA Mobo (2) SuperMicro AOC-SASLP-MV8 cards (1) (Silicon Image SIL3132) card 4 gig ram Celeron Processor disk0-disk5 on mobo disk6-disk7 SIL card disk8-disk11 SASLP card 1 cable 1 disk12-disk15 SASLP card 1 cable 2 disk16-disk19 SASLP card 2 cable 1 disk20 SASLP card 2 cable 2 syslog-2012-05-20.txt Disk1112_HD_Parm.txt Disk1112_smartctl.txt
  4. The search database is built but all searches return with no results. Is anyone else having this problem? It used to work on but stopped a few months ago. I have try a fresh install even to no avail. I'm running the latest stable subsonic and using the package developed here. Any thoughts would be appreciated.
  5. You need to change the permissions. It doesn't like 777. For the slimserver folder use 774 For the Folders in Music find . -type d -exec chmod 755 {} \; For the files find . -type f -exec chmod 644{} \;
  6. Cable is fine. Tried it just in case though. Will try a static IP tonight. I have always had it set to use DHCP. It appears that it is something with 4.5.3. Going back to 5.5.1 fixes the problem right away. I have a Asus P5B-VM DO mobo it my system. Using the onbaord NIC.
  7. I just tried updating from 4.5.1 to 4.5.3. When i do I am not able to get a network connection. I revert back and all is fine. Any Ideas? Attached is my syslog. Please let me know if any other info is needed. Thanks in advance. syslog.txt