June 19, 200917 yr Running 4.5Beta6 and have been for a while with no problems until this. Yesterday I went to the webpage interface and noticed that disk #4 had the red dot. I thought to just do a power down and re-boot as this will normally get this back up fine. Rather the server came up and thought disk#2 and disk #3 were missing BUT disk#4 was now looking normal again, holy crap. What to do now I thought, so I powered down again and again re-started, this time it came up with ALL drives looking normal BUT sits there saying "Starting" and never goes past that point. I really don't know what to do next so any guidance would be great.
June 19, 200917 yr I'd suggest posting a syslog. This is always the right first step. Don't panic. Chances are very good that the drives and data are fine. Don't press restore or press the format button for any reason. Two likely causes come to mind: bad memory or a lose cable. The syslog should give some hints.
June 19, 200917 yr Author Well in the state noted above I would not have been able to provide a syslog becuase the system would never start. But I continued to play around and I'm in a totally different place now. I pulled out the last 5 drives as they were recent expansions and empty so not really needed (yet). I can now get the system to start but disk #1 looks to be unformatted and it's not. I know the normal fix for this is a re-boot but that does not change anything. Is there a way to force the software to accept the drive and mount it normally....?
June 19, 200917 yr Well in the state noted above I would not have been able to provide a syslog becuase the system would never start. But I continued to play around and I'm in a totally different place now. I pulled out the last 5 drives as they were recent expansions and empty so not really needed (yet). I can now get the system to start but disk #1 looks to be unformatted and it's not. I know the normal fix for this is a re-boot but that does not change anything. Is there a way to force the software to accept the drive and mount it normally....? post the output of fdisk -l /dev/sd? (Where sd? is the correct drive) It should show a single partition, sized to start at sector 63 to the end of the drive. If it does, then reiserfsck /dev/sd? To run a file-system check. Odds are it will tell you to run with --fix-fixable if it finds any corruption. I would run reiserfsck on each of your data disks in turn (all but the parity drive) With as many different errors, have you check the BIOS voltages, timing, and speed for your memory strips? Many MB get it wrong, especially if you have premium RAM. It must be set for your specific ram manufacturer's requirements. Are you certain it is not the parity drive? (The drive assignments to /dev/sda,b,c will change with hardware changes, but serial numbers won't) Joe L.
June 19, 200917 yr Author Joe I ran that first command but I don't know where the report whenb and how to get to it to post it.
June 19, 200917 yr Joe I ran that first command but I don't know where the report whenb and how to get to it to post it. It just comes to the screen. To get the output to a file fdisk -l /dev/sd? >/boot/fdisk-out.txt Then you can look for the file fdisk-out.txt on your flash drive. Again, replace the "?" with the appropriate letter for your drive.
June 19, 200917 yr Author Nothing comes on the screen when I run that command just pops right back to the prompt, ran it with the save out txt option and the text file it created was emply.
June 19, 200917 yr Nothing comes on the screen when I run that command just pops right back to the prompt, ran it with the save out txt option and the text file it created was emply. type ls -l /dev/disk/by-id What does it say? or vol_id /dev/sd?1 (note, this time with the "1" at the end, to signify the 1st partition. Again, replace the '?" with the correct drive letter) What exactly did you type? If you gave it the name of a valid disk device it would output something. Joe L.
June 19, 200917 yr Author Tower login: root Linux 2.6.29.1-unRAID. root@Tower:~# ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-ST31500341AS_9VS0TC9X -> ../../sdk lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-ST31500341AS_9VS0TC9X-part1 -> ../../ sdk1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-ST31500341AS_9VS0TDBQ -> ../../sdm lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-ST31500341AS_9VS0TDBQ-part1 -> ../../ sdm1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-ST31500341AS_9VS0VF79 -> ../../sdl lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-ST31500341AS_9VS0VF79-part1 -> ../../ sdl1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-ST31500341AS_9VS0VHMT -> ../../sdn lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-ST31500341AS_9VS0VHMT-part1 -> ../../ sdn1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-ST31500341AS_9VS1DCW8 -> ../../sdi lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-ST31500341AS_9VS1DCW8-part1 -> ../../ sdi1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-ST3500630A_5QG19HYK -> ../../hdb lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-ST3500630A_5QG19HYK-part1 -> ../../hd b1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ1111883 - > ../../sdj lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ1111883-p art1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ1904630 - > ../../sdb lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-WDC_WD10EACS-00ZJB0_WD-WCASJ1904630-p art1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-WL1000GSA1672_WOL240065932 -> ../../s dc lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-WL1000GSA1672_WOL240065932-part1 -> . ./../sdc1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-WL1000GSA1672_WOL240066149 -> ../../s de lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-WL1000GSA1672_WOL240066149-part1 -> . ./../sde1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-WL1000GSA1672_WOL240066502 -> ../../s df lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-WL1000GSA1672_WOL240066502-part1 -> . ./../sdf1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-WL1000GSA1672_WOL240066649 -> ../../s dh lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-WL1000GSA1672_WOL240066649-part1 -> . ./../sdh1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-WL1000GSA1672_WOL240066650 -> ../../s da lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-WL1000GSA1672_WOL240066650-part1 -> . ./../sda1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 ata-WL1000GSA1672_WOL240066743 -> ../../s dd lrwxrwxrwx 1 root root 10 Jan 18 19:45 ata-WL1000GSA1672_WOL240066743-part1 -> . ./../sdd1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS0TC9X -> ../../ sdk lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS0TC9X-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS0TDBQ -> ../../ sdm lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS0TDBQ-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS0VF79 -> ../../ sdl lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS0VF79-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS0VHMT -> ../../ sdn lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS0VHMT-part1 -> ../../sdn1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS1DCW8 -> ../../ sdi lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_ST31500341AS_9VS1DCW8-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_WDC_WD10EACS-00_WD-WCASJ1111883 -> ../../sdj lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_WDC_WD10EACS-00_WD-WCASJ1111883 -part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_WDC_WD10EACS-00_WD-WCASJ1904630 -> ../../sdb lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_WDC_WD10EACS-00_WD-WCASJ1904630 -part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240065932 -> . ./../sdc lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240065932-part 1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066149 -> . ./../sde lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066149-part 1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066502 -> . ./../sdf lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066502-part 1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066649 -> . ./../sdh lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066649-part 1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066650 -> . ./../sda lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066650-part 1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066743 -> . ./../sdd lrwxrwxrwx 1 root root 10 Jan 18 19:45 scsi-SATA_WL1000GSA1672_WOL240066743-part 1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Jan 18 19:45 usb-LEXAR_JD_FIREFLY_106A6601141919290706 -0:0 -> ../../sdg lrwxrwxrwx 1 root root 10 Jan 18 19:45 usb-LEXAR_JD_FIREFLY_106A6601141919290706 -0:0-part1 -> ../../sdg1 root@Tower:~#
June 23, 200917 yr Author Turns out that what was my disk1 had some issues but more than that I think expanding an older original tower to more than 12 drives is not a good idea. Remember that the original Intel MB has only 2 SATA ports on-board AND only has PCI slots so SATA expansion cards all sit on the same PCI bus. I reduced the number of drives to 10 total and the system is running normal again.
Archived
This topic is now archived and is closed to further replies.