MrD1234

Members
  • Posts

    35
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

MrD1234's Achievements

Noob

Noob (1/14)

0

Reputation

  1. attic? i hope it's cooled or you live in the north somewhere... my attic is 100+ degrees in the summer
  2. That 133 Mhz 64bit card is only running at 33Mhz 32 bit (i.e. an eight of its rated performance)
  3. Double confirm, something causes the "upgradepkg" script to die (i.e <defunct>) You can telnet into the box and kill the process and the rest of the system comes up. All the vmtools is installed, so I am not quite sure what the issue is. Perhaps there are some remnants from a previous vmtools package?
  4. Thanks! There is something weird going on for sure. I added another disk to the LSI 9211 controller, added it as a raw virtual disk and mapped it into Unraid. It completed the re-construction successfully, but when I checked the array after I got home, I saw the same errors on a different physical disk. I am wondering if there is some kind of spin up delay that the controller / driver is not waiting long enough and the driver thinks it is a physical error.
  5. ok that makes sense. By "clear" i mean simulate replacing the drive I don't believe the drive is bad. I think it's a ESXi issue.
  6. I had 2 read / 2 write errors occur on a disk. The statistics for that drive do not update but writes to that drive are still allowed to proceed via a samba share on a user share. Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] Device not ready Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] Sense Key : 0x2 [current] Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] ASC=0x4 ASCQ=0x2 Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] CDB: cdb[0]=0x28: 28 00 00 04 00 40 00 00 08 00 Jul 6 23:26:13 Tower2 kernel: end_request: I/O error, dev sdc, sector 262208 Jul 6 23:26:13 Tower2 kernel: md: disk2 read error Jul 6 23:26:13 Tower2 kernel: handle_stripe read error: 262144/2, count: 1 Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] Device not ready Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] Sense Key : 0x2 [current] Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] ASC=0x4 ASCQ=0x2 Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 04 00 40 00 00 08 00 Jul 6 23:26:14 Tower2 kernel: end_request: I/O error, dev sdc, sector 262208 Jul 6 23:26:14 Tower2 kernel: md: disk2 write error Jul 6 23:26:14 Tower2 kernel: handle_stripe write error: 262144/2, count: 1 Jul 6 23:26:14 Tower2 kernel: md: recovery thread woken up ... Jul 6 23:26:14 Tower2 kernel: md: recovery thread has nothing to resync Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Device not ready Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Sense Key : 0x2 [current] Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] ASC=0x4 ASCQ=0x2 Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] CDB: cdb[0]=0x28: 28 00 00 00 00 c0 00 00 08 00 Jul 6 23:26:15 Tower2 kernel: end_request: I/O error, dev sdc, sector 192 Jul 6 23:26:15 Tower2 kernel: md: disk2 read error Jul 6 23:26:15 Tower2 kernel: handle_stripe read error: 128/2, count: 1 Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Device not ready Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Sense Key : 0x2 [current] Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] ASC=0x4 ASCQ=0x2 Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 00 00 c0 00 00 08 00 Jul 6 23:26:15 Tower2 kernel: end_request: I/O error, dev sdc, sector 192 Jul 6 23:26:15 Tower2 kernel: md: disk2 write error Jul 6 23:26:15 Tower2 kernel: handle_stripe write error: 128/2, count: 1 Jul 6 23:37:01 Tower2 crond[1148]: ignoring /var/spool/cron/crontabs/root- (non-existent user) I've read the system should be in a read only mode. This feels like a bug. Also given this is a test array, what is the best way to "clear" the error without replacing the drive? EDIT -- and the parity check buttons are gone
  7. Curious how much you paid for those. I have dozens of sata cables in a box, that I've collected over time. Every motherboard I get comes with 6 or 8 cables and I never use them.
  8. Theoretically gigabit tops out at 125MB/s Gigabit on a good switch tops out at 110MB/s. not sure what you can use the last 7-23 MB/s for....
  9. a gigabit controller will saturate the PCI bus.
  10. It supports 256 drives via SAS expanders, theoretically with 10 unraid VMs that's a lot of future proofing
  11. aren't media (i.e. dvd / photos / music) storage drives idle most of the time... unless people spend more than 8-10 hours in front of the idiot box.
  12. The expander only uses the pcie slot for power. If you're reasonably competent with a soldering iron, you could probably order a pcie connector like this one and solder a molex pigtail to the proper pins. You also need to assert the power good signal for the card to run.