Jump to content

Jelly-Monster

Member
  • Posts

    8
  • Joined

  • Last visited

Awards

This user doesn't have any awards

  1. Yeah, that's what I'm thinking. I bought the drive from Ebay, and although it was advertised as new it didn't come in sealed packaging. The format took about 30 hours, and thankfully worked. Thanks everyone for the help
  2. I've potentially found the solution! Whilst playing around with smartctl, I noticed it was formatted with type 2 protection. Not really knowing what this is, I did a bit of Google-ing and found this: http://talesinit.blogspot.com/2015/11/formatted-with-type-2-protection-huh.html I'm currently in the process of formatting (it's at 1.26%), which feels like progress.
  3. I did think about the cables, as the Dell branded cables are so expensive I got some from AliExpress. But I've moved the drive into a known working slot, and still get the same issue. Do you think it could still be a bad cable? I'm running firmware ver sion 20.00.07.00-IT, and in the SAS topology it is seeing the 8TB drive. I've attached screen captures that might help. I've attached the logs from fresh boot, and using the GREP "sd" command. Hopefully it makes more sense to you. I'll do a bit more Googleing of the errors in the meantime. DMESG DMESG GREP SD
  4. Good shout. I'm no good at reading the logs though.... it does seem to be spewing up some errors: [14624.392973] mpt2sas_cm0: log_info(0x3112043b): originator(PL), code(0x12), sub_code(0x043b) [14624.393010] sd 0:0:2:0: [sdc] Unaligned partial completion (resid=113928, sector_sz=512) [14624.393016] sd 0:0:2:0: [sdc] tag#3096 CDB: Read(32) [14624.393021] sd 0:0:2:0: [sdc] tag#3096 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00 [14624.393025] sd 0:0:2:0: [sdc] tag#3096 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 [14624.393033] sd 0:0:2:0: [sdc] tag#3096 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_SENSE [14624.393038] sd 0:0:2:0: [sdc] tag#3096 Sense Key : Illegal Request [current] [14624.393043] sd 0:0:2:0: [sdc] tag#3096 Add. Sense: Logical block guard check failed [14624.393051] sd 0:0:2:0: [sdc] tag#3096 CDB: Read(32) [14624.393058] sd 0:0:2:0: [sdc] tag#3096 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00 [14624.393062] sd 0:0:2:0: [sdc] tag#3096 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 [14624.393066] blk_update_request: protection error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 17 prio class 0 No idea what this means though?
  5. Yeah, I'm thinking the same. I've got a SATA to SAS adapter coming next week, so I guess we'll see what happens.
  6. I've swapped both, the 8TB is now /dev/sdc and still the same input/output error.
  7. Unfortunately I haven't got an other way to test it. I could order SATA to SAS adapter and try it in my gaming PC.
  8. Hi everyone, I recently upgraded the Perc6 Raid controller in my Dell R710 to a H200 which I've flashed to IT mode. My current drive setup is: (2x) 1TB hard drives in RAID1 (1x) 2TB hard drive (1x) 8TB hard drive which I purchased from eBay at the same time as the H200 I can boot into Proxmox fine, and see all 4 disks. However, when I clicked "Initialize Disk with GPT" on the 8TB, I get "command '/sbin/sgdisk /dev/sdb -U R' failed: exit code 2". Also, when I try and use fdisk I get "fdisk: cannot open /dev/sdb: Input/output error". I've also booted a Ubuntu live image and get the same error with fdisk. The drive was advertised as "new", but I guess it could be faulty. Does anyone have any ideas?
×