August 23, 200817 yr Each time I reboot my server, three out of the 10 disk are listed as missing with the error "stopped: invalid configuration." It is easy enough to go into "devices" and selet the drives that are missing. Then the array start fine. Any suggestions regarding this? Thanks.
August 23, 200817 yr It could be as simple as your power supply not being able to spin up 10 drives at once. Please post a copy of your syslog. Instructions in the wiki here: http://lime-technology.com/wiki/index.php?title=Troubleshooting How are you shutting down? Are you stopping the array first? or just hitting the power button? Joe L.
August 23, 200817 yr Author Thanks for the response. Syslog is attached. To answer your other questions... 1. Reboot is from the web interface of unraid. 2. I have two power supplies and have not changed my configuration recently.
August 24, 200817 yr Thanks for the response. Syslog is attached. To answer your other questions... 1. Reboot is from the web interface of unraid. 2. I have two power supplies and have not changed my configuration recently. A couple of things about PSUs: 1) they fail, 2) hot weather drastically reduces their power output, so a PSU that works in February may not work in August, but will work again in February. Bill
August 24, 200817 yr Tom, there appears to be a problem in the way his IDE drives are being identified. His 4 IDE drives should be hda through hdd, but are being assigned sdg through sdj. The Device Inventory shows the following: Device inventory: pci-0000:00:1f.1-scsi-0:0:0:0 (sdg) ata-ST3750640A_5QD01XM4 pci-0000:00:1f.1-scsi-0:0:1:0 (sdh) ata-WDC_WD3200JB-00KFA0_WD-WCAMR2129482 pci-0000:00:1f.1-scsi-1:0:0:0 (sdi) ata-HDS724040KLAT80_KRFA06RAH7HLXC pci-0000:00:1f.1-scsi-1:0:1:0 (sdj) ata-Maxtor_6H500R0_H80R2ECH followed immediately by: restart_md_driver: stat pci-0000:00:1f.1-ide-1:0: No such file or directory restart_md_driver: stat pci-0000:00:1f.1-ide-1:1: No such file or directory restart_md_driver: stat pci-0000:00:1f.1-ide-0:0: No such file or directory restart_md_driver: stat pci-0000:00:1f.1-ide-0:1: No such file or directory ... shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=8,160,8,176,0,0,0,0,0,0,0,0,8,16,... ... md2: missing md3: missing md4: missing md5: missing These drives are assigned by the ata_piix driver, and here's a log sample: ata_piix 0000:00:1f.1: version 2.12 ... scsi9 : ata_piix scsi10 : ata_piix ata9: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14 ata10: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15 ata9.00: ATA-7: ST3750640A, 3.AAE, max UDMA/100 ata9.00: 1465149168 sectors, multi 16: LBA48 ata9.01: ATA-6: WDC WD3200JB-00KFA0, 08.05J08, max UDMA/100 ata9.01: 625142448 sectors, multi 16: LBA48 ata9.00: configured for UDMA/100 ata9.01: configured for UDMA/100 ... scsi 9:0:0:0: Direct-Access ATA ST3750640A 3.AA PQ: 0 ANSI: 5 sd 9:0:0:0: [sdg] 1465149168 512-byte hardware sectors (750156 MB) ... sdg: sdg1 sd 9:0:0:0: [sdg] Attached SCSI disk ... (repeats for the other 3 drives too) It uses the traditional PATA channels and IRQ's 14 and 15, but sets up SCSI ID's! I have a hard time understanding why others have not had the same problem. This is using v4.3.3. jgs2n: You might try loading a new system configuration (in /boot/config/super.dat and disk.cfg), by using the procedure here. Unfortunately, I'm too tired at the moment to think of the safest way to force the Restore button to appear. Perhaps Joe or Tom or someone else can help... It could be as easy as deleting the super.dat and/or disk.cfg files. Once you click the Restore button, Starting the array (and using that special command in the HowTo) will create and save a new config, and begin a parity check, which you can stop. Hopefully, the new config will save the newer SCSI device ID's in your config, but I don't know why that is not happening already.
August 25, 200817 yr Author Correction... I thought it worked but it didn't. I then decided to start at the beginning with a new config. I printed out the tower web page so I knew how drives were assigned. I then backed up my config folder on the flash and inserted a new config folder from 4.3. I copied my key from the backed up config file and booted up. I assigned all the drives and let unraid run a parity check. Everything is now working fine. I checked it with 3 reboots. I don't understand what the problem was and know nothing about linux but this worked...I think.
August 25, 200817 yr Let me know if this works long term. I find that sometimes I can reboot without the disks needing to be reassigned but 95% of the time I do. I would be curious to know if this fixes it permanently. I mailed Tom about this a while ago and never got a response.
September 14, 200817 yr Ok I tried the suggested fix and I STILL have the same problem. Tom, I mailed you twice. Can you assist? I wiped my config and rebuilt it and it made me rebuild parity but it still is a problem. I sent my syslog via e-mail.
Archived
This topic is now archived and is closed to further replies.