January 16, 200818 yr To start with, I am not using 4.2, but there isn't a 1.0 forum and that is probably the version I am on. My unraid server has been running happily unattened for 2 years but decided to stop serving movies last week. I tried to telnet in and when I open a telnet window it tries to connect to tower and then closes. I have a monitor hooked up to the server now and it is stuck at md(9,5) :Using r5 hash to sort names remount: /dev/md5 md(9,5):can't shrink filesystem on-line when I type root at login I get LINUX 2.4.29. ROOT@TOWER:~# Not being a linux guy I have no idea what I'm looking at or what to do. I typed top and got TOP: ERROR WHILE LOADING SHARED LIBRARIRS: LIBGPM.SO.1: CANNOT OPEN SHARED OBJEC T FILE: NO SUCH FILE OR DIRECTORY I know from looking at the management page last week that one of my drives was bad. There was nothing on it so I didn't rush out to fix it. I don't know if my problem is related to that or not. HELP... I don't know where to begin
January 16, 200818 yr Author Progress?? I can now telenet in. A couple of samba stop and samba starts later and I can see the flash drive with a \\tower command //tower gets me nothin Right now the server screen is scrolling hdh: lost interrupt I'm still lost
January 16, 200818 yr The first console messages you saw are normal and expected. The error for top is clearly wrong, and, I think, indicates a corrupted environment, at which point you really don't want to trust any message or error the system tells you. You want to shut it down as cleanly as possible, and power all the way off. Then bring it up clean, and after a fresh boot, you can begin to assess what works and what doesn't, what is good, and what may have some corruption. The 'lost interrupt' error is bad, but until you have rebooted, you really don't know if the error is true or not. Plus, it is too vague and it doesn't really help us know what is wrong. I would deal with what you do know, that you have a bad drive, and either pull it and rebuild parity on the rest, or replace it.
January 16, 200818 yr Author I pulled out the bad disk, but I still can't get in with the management utility. How do I rebuild parity from a telnet session? Remeber I'm linux challenged. I only knew to type in samba start cause I found it in another post, but had no idea what i was doing.
January 16, 200818 yr Author Pardon my ignorance, but since the only thing I can see is my flash drive I looked to see what was on it. There is a system folder with 3 folders in it, pervious, grub and current. They all appear to be empty. Should I be able to see files in them?
January 16, 200818 yr I have no experience with any version prior to 4.0 betas, and what you are finding on the flash is completely different than current versions, so I'm going to have to leave you to someone with much longer experience than I. You do need the management page working. Try capturing a syslog and posting it, perhaps that will have a clue as to what is wrong with your setup.
January 16, 200818 yr Pardon my ignorance, but since the only thing I can see is my flash drive I looked to see what was on it. There is a system folder with 3 folders in it, pervious, grub and current. They all appear to be empty. Should I be able to see files in them? The files probably are there. To see them you need to set windows explorer to allow you to see hidden and system files. You really don't want to be removing or re-arranging disks without being able to see the management utility, especially on a 1.0 version of unRaid. It had a serious bug related to the installation of replacement disks. To stop the array, I seem to remember a "stop" command on the older versions of unRaid. you can try typing that at the linux command line. stop Follow it by typing sync reboot You might have had a power glitch in your house. You might just need to reboot to get the management utility working. You might want to think about upgrading. Tom offered two Pro keys to early users of unRaid. You would need to purchase a flash drive loacally and install the current version of unRaid on it,, but you would be way ahead in the ability to manage the disks. Send Tom an e-mail... I'm sure he will help get you going again if a simple reboot does not do it. Other than that, at the linux command line to capture the syslog type: cp /var/log/syslog /boot/syslog.txt Then, in windows, copy the file from the flash drive and attach it to a post here. Joe L.
January 16, 200818 yr Author Thanks for the quick feedback. I have a battery backup that I hoped was protecting the server from power issues, but who knows. I'll try the stuff you gave me tonight and see if I can get it working
January 17, 200818 yr Author Back home and here is what my syslog looks like.... I hope it does more for you than for me All drive lights of front of case are green.. even the one that said it was a bad disk before, #9 In case it helps, i have disks in 1,2,3,4,5,9,10&11. I'm planning on upgrading to version 4 when I get out of this. If upgrading now helps my situation, I'll try anything Jan 16 23:17:15 Tower kernel: Linux version 2.4.29 (root@Develop) (gcc version 3.3.4) #11 Fri Sep 2 01:38:25 PDT 2005 Jan 16 23:17:15 Tower kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) Jan 16 23:17:15 Tower kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) Jan 16 23:17:15 Tower kernel: BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved) Jan 16 23:17:15 Tower kernel: BIOS-e820: 0000000000100000 - 000000001fe2fc00 (usable) Jan 16 23:17:15 Tower kernel: BIOS-e820: 000000001fe2fc00 - 000000001fe30000 (ACPI NVS) Jan 16 23:17:15 Tower kernel: BIOS-e820: 000000001fe30000 - 000000001fe40000 (ACPI data) Jan 16 23:17:15 Tower kernel: BIOS-e820: 000000001fe40000 - 000000001fef0000 (ACPI NVS) Jan 16 23:17:15 Tower kernel: BIOS-e820: 000000001fef0000 - 000000001ff00000 (reserved) Jan 16 23:17:15 Tower kernel: BIOS-e820: 00000000fecf0000 - 00000000fecf1000 (reserved) Jan 16 23:17:15 Tower kernel: BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved) Jan 16 23:17:15 Tower kernel: On node 0 totalpages: 130607 Jan 16 23:17:15 Tower kernel: zone(0): 4096 pages. Jan 16 23:17:15 Tower kernel: zone(1): 126511 pages. Jan 16 23:17:15 Tower kernel: zone(2): 0 pages. Jan 16 23:17:15 Tower kernel: Kernel command line: root=/dev/ram0 ramdisk_size=120000 Jan 16 23:17:15 Tower kernel: Detected 2261.089 MHz processor. Jan 16 23:17:15 Tower kernel: Console: colour VGA+ 80x25 Jan 16 23:17:15 Tower kernel: Calibrating delay loop... 4508.87 BogoMIPS Jan 16 23:17:15 Tower kernel: Page-cache hash table entries: 131072 (order: 7, 524288 bytes) Jan 16 23:17:15 Tower kernel: CPU: Intel® Celeron® CPU 2.26GHz stepping 01 Jan 16 23:17:15 Tower kernel: POSIX conformance testing by UNIFIX Jan 16 23:17:15 Tower kernel: PCI: Probing PCI hardware (bus 00) Jan 16 23:17:15 Tower kernel: Transparent bridge - Intel Corp. 82801BA/CA/DB/EB PCI Bridge Jan 16 23:17:15 Tower kernel: Initializing RT netlink socket Jan 16 23:17:15 Tower kernel: Starting kswapd Jan 16 23:17:15 Tower kernel: pty: 256 Unix98 ptys configured Jan 16 23:17:15 Tower kernel: keyboard: Timeout - AT keyboard not present?(ed) Jan 16 23:17:15 Tower kernel: keyboard: Timeout - AT keyboard not present?(f4) Jan 16 23:17:15 Tower kernel: RAMDISK driver initialized: 16 RAM disks of 120000K size 1024 blocksize Jan 16 23:17:15 Tower kernel: PCI: Enabling device 00:1f.1 (0005 -> 0007) Jan 16 23:17:15 Tower kernel: hda: HDS725050KLAT80, ATA DISK drive Jan 16 23:17:15 Tower kernel: hdb: HDS725050KLAT80, ATA DISK drive Jan 16 23:17:15 Tower kernel: blk: queue c031d520, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:15 Tower kernel: blk: queue c031d65c, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:15 Tower kernel: hdc: HDS725050KLAT80, ATA DISK drive Jan 16 23:17:15 Tower kernel: hdd: HDS725050KLAT80, ATA DISK drive Jan 16 23:17:15 Tower kernel: blk: queue c031d974, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:15 Tower kernel: blk: queue c031dab0, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:15 Tower kernel: hdh: HDS725050KLAT80, ATA DISK drive Jan 16 23:17:15 Tower kernel: blk: queue c031e358, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:15 Tower kernel: hdi: HDS725050KLAT80, ATA DISK drive Jan 16 23:17:15 Tower kernel: hdj: HDS725050KLAT80, ATA DISK drive Jan 16 23:17:15 Tower kernel: blk: queue c031e670, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:15 Tower kernel: blk: queue c031e7ac, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:15 Tower kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Jan 16 23:17:15 Tower kernel: ide1 at 0x170-0x177,0x376 on irq 15 Jan 16 23:17:15 Tower kernel: ide3 at 0xb000-0xb007,0xac02 on irq 10 Jan 16 23:17:15 Tower kernel: ide4 at 0xcc00-0xcc07,0xc802 on irq 10 Jan 16 23:17:15 Tower kernel: hda: attached ide-disk driver. Jan 16 23:17:15 Tower kernel: hda: host protected area => 1 Jan 16 23:17:15 Tower kernel: hdb: attached ide-disk driver. Jan 16 23:17:15 Tower kernel: hdb: host protected area => 1 Jan 16 23:17:15 Tower kernel: hdc: attached ide-disk driver. Jan 16 23:17:15 Tower kernel: hdc: host protected area => 1 Jan 16 23:17:15 Tower kernel: hdd: attached ide-disk driver. Jan 16 23:17:15 Tower kernel: hdd: host protected area => 1 Jan 16 23:17:15 Tower kernel: hdh: attached ide-disk driver. Jan 16 23:17:15 Tower kernel: hdh: host protected area => 1 Jan 16 23:17:15 Tower kernel: hdi: attached ide-disk driver. Jan 16 23:17:15 Tower kernel: hdi: host protected area => 1 Jan 16 23:17:15 Tower kernel: hdj: attached ide-disk driver. Jan 16 23:17:15 Tower kernel: hdj: host protected area => 1 Jan 16 23:17:15 Tower kernel: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 Jan 16 23:17:15 Tower kernel: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 Jan 16 23:17:15 Tower kernel: ehci_hcd 00:1d.7: BIOS handoff failed (104, 1010001) Jan 16 23:17:15 Tower kernel: host/usb-uhci.c: Detected 2 ports Jan 16 23:17:15 Tower last message repeated 3 times Jan 16 23:17:15 Tower kernel: Vendor: Flash Model: Drive UT_USB20 Rev: 0.00 Jan 16 23:17:15 Tower kernel: Type: Direct-Access ANSI SCSI revision: 02 Jan 16 23:17:15 Tower kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Jan 16 23:17:15 Tower kernel: SCSI device sda: 256000 512-byte hdwr sectors (131 MB) Jan 16 23:17:15 Tower kernel: sda: Write Protect is off Jan 16 23:17:15 Tower kernel: VFS: Mounted root (ext2 filesystem) readonly. Jan 16 23:17:15 Tower kernel: SCSI error: host 0 id 0 lun 0 return code = 8000002 Jan 16 23:17:15 Tower kernel: ^ISense class 7, sense error 0, extended sense 0 Jan 16 23:17:38 Tower kernel: blk: queue c031d520, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:38 Tower kernel: blk: queue c031d65c, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:38 Tower kernel: blk: queue c031d974, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:38 Tower kernel: blk: queue c031dab0, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:38 Tower kernel: blk: queue c031e670, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:38 Tower kernel: blk: queue c031e7ac, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:38 Tower kernel: blk: queue c031e358, I/O limit 4095Mb (mask 0xffffffff) Jan 16 23:17:39 Tower kernel: 8regs : 2552.000 MB/sec Jan 16 23:17:39 Tower kernel: 32regs : 1648.400 MB/sec Jan 16 23:17:39 Tower kernel: pIII_sse : 3934.800 MB/sec Jan 16 23:17:39 Tower kernel: pII_mmx : 2412.800 MB/sec Jan 16 23:17:39 Tower kernel: p5_mmx : 2434.000 MB/sec Jan 16 23:17:39 Tower kernel: md: using function: pIII_sse (3934.800 MB/sec) Jan 16 23:17:39 Tower kernel: get_token: status Jan 16 23:17:39 Tower kernel: md: reading superblock from device sda2 Jan 16 23:17:39 Tower kernel: md: superblock events: 78 Jan 16 23:17:39 Tower kernel: md: import hda HDS725050KLAT80 KRVA03ZAG3DD1D offset: 63 size: 488386552 Jan 16 23:17:39 Tower kernel: md: import hdb HDS725050KLAT80 KRVA03ZAG3VZ0D offset: 63 size: 488386552 Jan 16 23:17:39 Tower kernel: md: import hdc HDS725050KLAT80 KRVA03ZAG35RJD offset: 63 size: 488386552 Jan 16 23:17:39 Tower kernel: md: import hdd HDS725050KLAT80 KRVA03ZAG4VAVD offset: 63 size: 488386552 Jan 16 23:17:39 Tower kernel: md: import hdi HDS725050KLAT80 KRVA03ZAG4V6MD offset: 63 size: 488386552 Jan 16 23:17:39 Tower kernel: md: import hdj HDS725050KLAT80 KRVA02ZAG3X8WC offset: 63 size: 488386552 Jan 16 23:17:39 Tower kernel: md: blkdev_get error: -6 Jan 16 23:17:39 Tower last message repeated 3 times Jan 16 23:17:39 Tower kernel: md9: removed Jan 16 23:17:39 Tower kernel: md: blkdev_get error: -6 Jan 16 23:17:39 Tower kernel: md10: missing Jan 16 23:17:39 Tower kernel: md: import hdh HDS725050KLAT80 KRVA02ZAG3X5ZC offset: 63 size: 488386552 Jan 16 23:17:42 Tower kernel: get_token: status Jan 16 23:17:42 Tower kernel: md: reading superblock from device sda2 Jan 16 23:17:42 Tower kernel: md: superblock events: 78 Jan 16 23:17:42 Tower kernel: md: import hda HDS725050KLAT80 KRVA03ZAG3DD1D offset: 63 size: 488386552 Jan 16 23:17:42 Tower kernel: md: import hdb HDS725050KLAT80 KRVA03ZAG3VZ0D offset: 63 size: 488386552 Jan 16 23:17:42 Tower kernel: md: import hdc HDS725050KLAT80 KRVA03ZAG35RJD offset: 63 size: 488386552 Jan 16 23:17:42 Tower kernel: md: import hdd HDS725050KLAT80 KRVA03ZAG4VAVD offset: 63 size: 488386552 Jan 16 23:17:42 Tower kernel: md: import hdi HDS725050KLAT80 KRVA03ZAG4V6MD offset: 63 size: 488386552 Jan 16 23:17:42 Tower kernel: md: import hdj HDS725050KLAT80 KRVA02ZAG3X8WC offset: 63 size: 488386552 Jan 16 23:17:42 Tower kernel: md: blkdev_get error: -6 Jan 16 23:17:42 Tower last message repeated 3 times Jan 16 23:17:42 Tower kernel: md9: removed Jan 16 23:17:42 Tower kernel: md: blkdev_get error: -6 Jan 16 23:17:42 Tower kernel: md10: missing Jan 16 23:17:42 Tower kernel: md: import hdh HDS725050KLAT80 KRVA02ZAG3X5ZC offset: 63 size: 488386552 Jan 16 23:17:44 Tower kernel: get_token: start Jan 16 23:17:44 Tower kernel: get_token: STOPPED Jan 16 23:17:44 Tower kernel: md: reading superblock from device sda2 Jan 16 23:17:44 Tower kernel: md: superblock events: 78 Jan 16 23:17:44 Tower kernel: md: import hda HDS725050KLAT80 KRVA03ZAG3DD1D offset: 63 size: 488386552 Jan 16 23:17:44 Tower kernel: md: import hdb HDS725050KLAT80 KRVA03ZAG3VZ0D offset: 63 size: 488386552 Jan 16 23:17:44 Tower kernel: md: import hdc HDS725050KLAT80 KRVA03ZAG35RJD offset: 63 size: 488386552 Jan 16 23:17:45 Tower kernel: md: import hdd HDS725050KLAT80 KRVA03ZAG4VAVD offset: 63 size: 488386552 Jan 16 23:17:45 Tower kernel: md: import hdi HDS725050KLAT80 KRVA03ZAG4V6MD offset: 63 size: 488386552 Jan 16 23:17:45 Tower kernel: md: import hdj HDS725050KLAT80 KRVA02ZAG3X8WC offset: 63 size: 488386552 Jan 16 23:17:45 Tower kernel: md: blkdev_get error: -6 Jan 16 23:17:45 Tower last message repeated 3 times Jan 16 23:17:45 Tower kernel: md9: removed Jan 16 23:17:45 Tower kernel: md: blkdev_get error: -6 Jan 16 23:17:45 Tower kernel: md10: missing Jan 16 23:17:45 Tower kernel: md: import hdh HDS725050KLAT80 KRVA02ZAG3X5ZC offset: 63 size: 488386552 Jan 16 23:17:45 Tower kernel: md1: running, size: 488386552 blocks Jan 16 23:17:45 Tower kernel: md2: running, size: 488386552 blocks Jan 16 23:17:45 Tower kernel: md3: running, size: 488386552 blocks Jan 16 23:17:45 Tower kernel: md4: running, size: 488386552 blocks Jan 16 23:17:45 Tower kernel: md5: running, size: 488386552 blocks Jan 16 23:17:45 Tower kernel: md9: running, size: 293036152 blocks Jan 16 23:17:45 Tower kernel: md10: running, size: 293057320 blocks Jan 16 23:17:45 Tower kernel: md11: running, size: 488386552 blocks Jan 16 23:17:45 Tower kernel: get_token: status Jan 16 23:17:47 Tower kernel: get_token: check Jan 16 23:17:47 Tower kernel: md: writing superblock to device sda2 Jan 16 23:17:47 Tower kernel: md: recovery thread has nothing to resync Jan 16 23:17:47 Tower kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Jan 16 23:17:47 Tower kernel: printing eip: Jan 16 23:17:47 Tower kernel: 00000000 Jan 16 23:17:47 Tower kernel: *pde = 00000000 Jan 16 23:17:47 Tower kernel: Oops: 0000 Jan 16 23:17:47 Tower kernel: CPU: 0 Jan 16 23:17:47 Tower kernel: EIP: 0010:[<00000000>] Not tainted Jan 16 23:17:47 Tower kernel: EFLAGS: 00010282 Jan 16 23:17:47 Tower kernel: eax: c031e21c ebx: df8a1da0 ecx: c031e15c edx: 00001298 Jan 16 23:17:47 Tower kernel: esi: 00000000 edi: 00000000 ebp: 00000000 esp: de67bcb8 Jan 16 23:17:47 Tower kernel: ds: 0018 es: 0018 ss: 0018 Jan 16 23:17:47 Tower kernel: Process emhttp (pid: 854, stackpage=de67b000) Jan 16 23:17:47 Tower kernel: Stack: c01c42d0 c031e21c 00000000 df8a1da0 c6a3eb4b 83f9e84f 00000010 df8a1da0 Jan 16 23:17:47 Tower kernel: d7b43ce4 00000000 00000007 e0844be9 00000000 df8a1da0 314fec48 d7b43cfc Jan 16 23:17:47 Tower kernel: 00000006 00000000 00000001 00000000 00000000 00000008 00000000 00000000 Jan 16 23:17:47 Tower kernel: Call Trace: [<c01c42d0>] [<e0844be9>] [<e08450a5>] [<c01c42d0>] [<c01c436e>] Jan 16 23:17:47 Tower kernel: [<c013a56b>] [<c01c451a>] [<c0138402>] [<c018f57c>] [<c018fe47>] [<c013afba>] Jan 16 23:17:47 Tower kernel: [<c013b87b>] [<c014cbe7>] [<c013bbcd>] [<c014dc67>] [<c014df54>] [<c014ddb5>] Jan 16 23:17:47 Tower kernel: [<c014e350>] [<c0108bbb>] Jan 16 23:17:47 Tower kernel: Jan 16 23:17:47 Tower kernel: Code: Bad EIP value. Jan 16 23:17:47 Tower kernel: reiserfs: found format "3.6" with standard journal Jan 16 23:17:47 Tower kernel: reiserfs: found format "3.6" with standard journal Jan 16 23:17:47 Tower last message repeated 3 times Jan 16 23:18:56 Tower kernel: reiserfs: checking transaction log (device md(9,4)) ... Jan 16 23:18:56 Tower kernel: for (md(9,4)) Jan 16 23:19:10 Tower kernel: reiserfs: checking transaction log (device md(9,3)) ... Jan 16 23:19:10 Tower kernel: for (md(9,3)) Jan 16 23:19:14 Tower kernel: md(9,4):Using r5 hash to sort names Jan 16 23:19:14 Tower kernel: md(9,3):Using r5 hash to sort names Jan 16 23:19:14 Tower kernel: md(9,4):can't shrink filesystem on-line Jan 16 23:19:14 Tower kernel: md(9,3):can't shrink filesystem on-line Jan 16 23:19:14 Tower kernel: reiserfs: checking transaction log (device md(9,1)) ... Jan 16 23:19:14 Tower kernel: for (md(9,1)) Jan 16 23:19:14 Tower kernel: md(9,1):Using r5 hash to sort names Jan 16 23:19:14 Tower kernel: md(9,1):can't shrink filesystem on-line Jan 16 23:19:14 Tower kernel: reiserfs: checking transaction log (device md(9,5)) ... Jan 16 23:19:14 Tower kernel: for (md(9,5)) Jan 16 23:19:15 Tower kernel: md(9,5):Using r5 hash to sort names Jan 16 23:19:15 Tower kernel: md(9,5):can't shrink filesystem on-line Jan 16 23:19:15 Tower kernel: reiserfs: checking transaction log (device md(9,2)) ... Jan 16 23:19:15 Tower kernel: for (md(9,2)) Jan 16 23:19:15 Tower kernel: md(9,2):Using r5 hash to sort names Jan 16 23:19:15 Tower kernel: md(9,2):can't shrink filesystem on-line Jan 16 23:33:42 Tower kernel: get_token: stop Jan 16 23:33:42 Tower kernel: md: 3 devices still in use.
January 17, 200818 yr Author OK, so I got the managenet utility back with half the drives. I only powered up disks 1-5 and the management utility showed them as good but showed disk 9 (the original bad disk) as not working and disks 10 & 11 as missing. So I reset the array and now I can read disks 1-5 again. It doesn't see disks 10 & 11 (i removed disk 9 and powered on the lower 6 drives) and I'd like to get those back intact, but there wasn't a lot of important stuff on them, so that is on my todo list, but I would like to upgrade to a newer version first. So I'll start a new thread to find out the best upgrade path from 1.050826
Archived
This topic is now archived and is closed to further replies.