supasin

If corruption is detected it is made read-only to prevent further damage. Use checkdisk, or scandisk in a windows PC to fix. Joe L. Joe, Running a windows error check fixed the problem. Thanks for the quick response! Kent

hi, any particular reason why my "/boot" folder is read-only? root@unraid:/boot# cd /boot root@unraid:/boot# mkdir a mkdir: cannot create directory `a': Read-only file system root@unraid:/boot# pwd /boot root@unraid:/boot# directory listing: drwxrwxrwx 12 root root 16384 2011-12-19 18:02 boot/ root@unraid:/# cat /etc/fstab /dev/disk/by-label/UNRAID /boot vfat auto,rw,exec,noatime,nodiratime,umask=0,shortname=mixed 0 0 thanks!

I had trouble starting v4.1 on my unraid. I had to change the subsonic_RAM.sh script (got this from another site) : Delete or comment out the following lines: cd $(dirname $0) if [ -e /bin/readlink ] || [ -e /usr/bin/readlink ]; then cd $(dirname $(readlink -f $0)) fi Replace above with: cd `dirname $0` Note the that above is a " ` " not a " ' "

Guys, can somebody please re-upload the dependencies package please? Romir's link doesn't work. Thanks a lot in advance try here: http://www.lockstockmods.net/2010/06/03/unraid-with-sabnzbd-and-sickbeard/ il be using this guide as son as i get a cache drive installed the lockstockmods site has older v1.3 dependencies and 0.5.2 of sabnzbd

i got my case at newegg

I am using the F3 BIOS. It spins down and goes to sleep. The only negative I would say is the PCI bus, which means that an expansion card would be slower than the rest of the SATA2 ports. Otherwise it's working like a charm.

The "\" characters are not really there. They are put there in the "ls" output to help you see there are spaces. cool thanks for the quick reply joe

On the underlying file system of unraid it adds "\" to the files with spaces that are copied or created. On the samba or nfs shares it shows up as normal without the "\". Any particular reason? How do I resolve this? Thanks!

Got my 2 WD20EARS 2TB drives and looks like unraid has passed level 1 3 drives active, parity synced and green dots across the board Specs: Case: Lian Li Q08B MB: Gigabyte GAD525TUD RAM: 2GB Kingston DDR3 1333 PSU: Antec Neo ECO 400C 400W Power HD: 2 x Seagate 7200.10 400GB SATA2 Drives, 2 x Western Digital Green WD20EARS 2TB SATA2 Drives syslog-2010-09-15.txt

Currently testing the GA-525TUD - Atom D525 motherboard. So far so good. I only have 2 drives, but I'm not sure when I'm going to add the 3rd drive. Everything seems to start fine. Did some initial copying of files, no problems. Still have parity to do. *UPDATE* Parity check ran fine Currently copying files I just ordered 2 x WD20EARS which I plan to add to the mix I do have a question regarding performance and SATA & UDMA/133. "ata2.00: configured for UDMA/133" is that normal for a SATA configuration? My motherboard is setup for the SATA to use AHCI. Sep 7 21:25:50 myNAS kernel: scsi1 : ahci Sep 7 21:25:50 myNAS kernel: scsi2 : ahci Sep 7 21:25:50 myNAS kernel: scsi3 : ahci Sep 7 21:25:50 myNAS kernel: scsi4 : ahci Sep 7 21:25:50 myNAS kernel: ata1: SATA max UDMA/133 abar m1024@0xfdffe000 port 0xfdffe100 irq 27 Sep 7 21:25:50 myNAS kernel: ata2: SATA max UDMA/133 abar m1024@0xfdffe000 port 0xfdffe180 irq 27 Sep 7 21:25:50 myNAS kernel: ata3: SATA max UDMA/133 abar m1024@0xfdffe000 port 0xfdffe200 irq 27 Sep 7 21:25:50 myNAS kernel: ata4: SATA max UDMA/133 abar m1024@0xfdffe000 port 0xfdffe280 irq 27 Sep 7 21:25:50 myNAS kernel: ahci 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Sep 7 21:25:50 myNAS kernel: ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode Sep 7 21:25:50 myNAS kernel: ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part Sep 7 21:25:50 myNAS kernel: ahci 0000:02:00.0: setting latency timer to 64 Sep 7 21:25:50 myNAS kernel: scsi5 : ahci Sep 7 21:25:50 myNAS kernel: scsi6 : ahci Sep 7 21:25:50 myNAS kernel: ata5: SATA max UDMA/133 abar m8192@0xfdefe000 port 0xfdefe100 irq 17 Sep 7 21:25:50 myNAS kernel: ata6: SATA max UDMA/133 abar m8192@0xfdefe000 port 0xfdefe180 irq 17 Sep 7 21:25:50 myNAS kernel: usb 5-2: new full speed USB device using uhci_hcd and address 2 Sep 7 21:25:50 myNAS kernel: usb 5-2: configuration #1 chosen from 1 choice Sep 7 21:25:50 myNAS kernel: hub 5-2:1.0: USB hub found Sep 7 21:25:50 myNAS kernel: hub 5-2:1.0: 3 ports detected Sep 7 21:25:50 myNAS kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 7 21:25:50 myNAS kernel: ata4: SATA link down (SStatus 0 SControl 300) Sep 7 21:25:50 myNAS kernel: ata3: SATA link down (SStatus 0 SControl 300) Sep 7 21:25:50 myNAS kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 7 21:25:50 myNAS kernel: ata5: SATA link down (SStatus 0 SControl 300) Sep 7 21:25:50 myNAS kernel: ata6: SATA link down (SStatus 0 SControl 300) Sep 7 21:25:50 myNAS kernel: ata1.00: ATA-7: ST3400620AS, 3.AAE, max UDMA/133 Sep 7 21:25:50 myNAS kernel: ata1.00: 781422768 sectors, multi 16: LBA48 NCQ (depth 31/32) Sep 7 21:25:50 myNAS kernel: ata2.00: ATA-7: ST3400620AS, 3.AAE, max UDMA/133 Sep 7 21:25:50 myNAS kernel: ata2.00: 781422768 sectors, multi 16: LBA48 NCQ (depth 31/32) Sep 7 21:25:50 myNAS kernel: ata1.00: configured for UDMA/133 Sep 7 21:25:50 myNAS kernel: scsi 1:0:0:0: Direct-Access ATA ST3400620AS 3.AA PQ: 0 ANSI: 5 Sep 7 21:25:50 myNAS kernel: sd 1:0:0:0: [sda] 781422768 512-byte logical blocks: (400 GB/372 GiB) Sep 7 21:25:50 myNAS kernel: sd 1:0:0:0: [sda] Write Protect is off Sep 7 21:25:50 myNAS kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 Sep 7 21:25:50 myNAS kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 7 21:25:50 myNAS kernel: sda: Sep 7 21:25:50 myNAS kernel: ata2.00: configured for UDMA/133 Sep 7 21:25:50 myNAS kernel: scsi 2:0:0:0: Direct-Access ATA ST3400620AS 3.AA PQ: 0 ANSI: 5 Sep 7 21:25:50 myNAS kernel: sd 2:0:0:0: [sdb] 781422768 512-byte logical blocks: (400 GB/372 GiB) Sep 7 21:25:50 myNAS kernel: sd 2:0:0:0: [sdb] Write Protect is off Sep 7 21:25:50 myNAS kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Sep 7 21:25:50 myNAS kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 7 21:25:50 myNAS kernel: sdb: sda1 Sep 7 21:25:50 myNAS kernel: sd 1:0:0:0: [sda] Attached SCSI disk Sep 7 21:25:50 myNAS kernel: sdb1 Sep 7 21:25:50 myNAS kernel: sd 2:0:0:0: [sdb] Attached SCSI disk Thanks! syslog.zip