Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Erased Raid 5, Hitachi 2TB disks unmountable

Featured Replies

Hi,

 

I've got 4 2TB Hitachi drives that i previously ran in a raid 5 array with a Highpoint Rocketraid 2310. I went into the raid admin page and erased the raid 5 array and then disconnected the drives, but I can't get unraid or windows to mount them.

 

Things I've tried:

 

*They turn up in Bios.

*unraid notices the drives but i can't mount them as device.

*In local disk manager in windows i can see the disk but it can't be initialized.

*I installed the rocketraid card in another pc and connected the disks, from there I could initialize them as JBOD. But when i tried to connect them to the sata port on the motherboard it was the same problem again.

 

I've been running a HDD low level format tool for 15 hours now but the progress bar hasn't even moved, it keeps giving me the following error:

"Format Error occured at offset 3,254,265,664" and the a different sector each time. It seems to be every 524288 bytes or whatever that the error occurs.

 

Is there anything i can try to make them work? Thanks!

You can not do a LL format on a SATA drive.

 

Put the drive in unRAID and run Joe's preclear script.

  • Author

I've tried running the preclear but I can't get it to start. The problem is that I don't know what my devices are named since i can't see the in unraid and they don't show up in the syslog.

 

I've tried running /preclear_disk.sh -l

but it only gives me some help commands.

 

Any advice?

 

syslog attached

syslog-2011-01-16.txt

try   ls -l /dev/disk/by-id

 

Sample output would be:

 

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 ata-Hitachi_HDS722020ALA330_JK1101YBJRHY1F -> ../../sdh

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 ata-Hitachi_HDS722020ALA330_JK1101YBJRHY1F-part1 -> ../../sdh1

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 ata-SAMSUNG_HD204UI_S2H7J1BZA28980 -> ../../sdg

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 ata-SAMSUNG_HD204UI_S2HGJDWZ806729 -> ../../sdf

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 ata-SAMSUNG_HD204UI_S2HGJDWZ806729-part1 -> ../../sdf1

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 ata-ST32000542AS_6XW1P9ED -> ../../sdb

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 ata-ST32000542AS_6XW1P9ED-part1 -> ../../sdb1

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 scsi-SATA_Hitachi_HDS7220_JK1101YBJRHY1F -> ../../sdh

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 scsi-SATA_Hitachi_HDS7220_JK1101YBJRHY1F-part1 -> ../../sdh1

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 scsi-SATA_SAMSUNG_HD204UIS2H7J1BZA28980 -> ../../sdg

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 scsi-SATA_SAMSUNG_HD204UIS2HGJDWZ806729 -> ../../sdf

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 scsi-SATA_SAMSUNG_HD204UIS2HGJDWZ806729-part1 -> ../../sdf1

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 scsi-SATA_ST32000542AS_6XW1P9ED -> ../../sdb

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 scsi-SATA_ST32000542AS_6XW1P9ED-part1 -> ../../sdb1

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 scsi-SATA_ST32000542AS_6XW1T2LJ -> ../../sdc

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 scsi-SATA_ST32000542AS_6XW1T2LJ-part1 -> ../../sdc1

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4045062 -> ../../sde

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4045062-part1 -> ../../sde1

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4310187 -> ../../sdd

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4310187-part1 -> ../../sdd1

lrwxrwxrwx 1 root root  9 2011-01-14 10:55 usb-SanDisk_Cruzer_355010189012F904-0:0 -> ../../sda

lrwxrwxrwx 1 root root 10 2011-01-14 10:55 usb-SanDisk_Cruzer_355010189012F904-0:0-part1 -> ../../sda1

 

 

so find the line with the drive/serial number and the end of the line tells you the device name. Ignore the lines that end in 1

 

  • Author

Thanks.

 

Can't see the disks in bios anymore i noticed, so i will have to solve that first i suppose. Connected one of the drives with esata to my windows pc and i shows up under disk manager but can't be initialized.

 

I've only go 3 Hitachi drives connected to the unraid server atm, and they are all empty of data so at least no risk of doing a mistake and loosing valuable data.

I've tried running the preclear but I can't get it to start. The problem is that I don't know what my devices are named since i can't see the in unraid and they don't show up in the syslog.

 

I've tried running /preclear_disk.sh -l

but it only gives me some help commands.

 

Any advice?

 

syslog attached

Are you using the new preclear_disk.sh ??

 

and the option is lower case "ell"  as in llama, not -1 (not the number one)

 

regardless, you can look at the output of

ls -l /dev/disk/by-id

 

 

Joe L.

  • Author

Yes I'm using the new script, and I was using the right option. The only media showing up is the flash card.

 

It seems like the rocketraid card adds a spin down feature to the harddrive so that it spins up when getting a signal from the raid card, which the motherboard can't replicate.

 

I can hear how the drives spin up once connected to the raid card, where's they stay completely silent when connected to the motherboard.

 

 

I dont think this is a Raid 5 signature related issue. I think it is a more fundamental AHCI/Kernel/Hardware issue. All three drives arent responding to SATA probe requests.

 

COMRESET failed (errno=-16)

 

Suggestions, turn off AHCI in the bios. Try different version of UnRaid. Stick in a different controller (SIL3132 PCI-e based). HP RR 2310 should work in UnRaid. Just leave disk undefined in the BIOS.

You have six unused ports on the motherboard - why not use them just for the preclear now and then try to figure out what is happening with the HP RR2310 (BTW check out if this controller is properly seated in the slot)

  • Author

I've got an ad out for the RR 2310 since i have a SUPERMICRO AOC-SASLP-MV8m incoming so I won't be needing it. Before i built the unRAID server i cleared the 4 Hitachi drives of all data and then deleted the raid5 array. So I've never actually tried th RR 2310 in the unraid server, just the disks connected directly to the slots on the MB.

 

I tried the same drives in my gaming PC and my previous server and it was the same problem, couldn't get a read on them at all, shows up in local disk manager but can't be initialized. Took ages to boot witht eh drives connected since bios could only tell there were drives connected, but no information of brand or size.

 

So i then proceeded to install the RR 2310 in my gaming pc for testing. When connecting the Hitachi drives to the slots in the RR 2310 they worked flawlessly in raid 0 and jbod. Tried to turn of NCQ before formatting the in the RR 2310 made no difference.

 

I read of a couple of other guys who had the same problem but with Western Digital drives, and WD asked him to RMA the drives. I did the same with mine today, hoping they will either fix or replace them.

 

I tried using preclear in two different computers but no result, couldn't even get it started. Today i plugged in a fresh WD20EARS and it just worked the way I was expecting it too, which felt nice since it's been uphill for a while before i i realized the drives were all faulty. At least it gave me the reason i needed to buy a completly new rig for the unRAID server which feels nice and fresh :)

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.