December 5, 201015 yr I just finished building this machine a couple days ago and missed the part in the instructions about running preclear first. I assigned 2 drives (I actually assigned all 3, but then unassigned the parity drive). I went in an unassigned the drives, so now in the Main menu under //tower I have the following: parity: no installed disk 1: Missing (along with sdX of the previously assigned drive) disk 2: Missing (along with sdX of the previously assigned drive) When I go to run the preclear command, I get the following message: Sorry: /dev/sdX does not exist as a block device Clearing will NOT be performed I tried initconfig, didn't seem to do anything Not really sure what to try next. What am I doing wrong?
December 5, 201015 yr You need to use the correct device names as detected on your hardware. /dev/sdX will be /dev/sda, /dev/sdb, /dev/sdc etc. To see YOUR devices type: ls -l /dev/disk/by-id The device name is at the very end of the line. Joe L.
December 5, 201015 yr Author well I was using x as a placeholder what I've been typing in is ./preclear_disk.sh /dev/SAMSUNG_HD20401_S2H7J902A00660 etc. for each drive. Is that not right?
December 5, 201015 yr well I was using x as a placeholder what I've been typing in is ./preclear_disk.sh /dev/SAMSUNG_HD20401_S2H7J902A00660 etc. for each drive. Is that not right? No that is not right.
December 5, 201015 yr Author lol ok. I'm misreading the config tutorial. Here's what the cmd prom looks like when I run that cmd you posted above: Not entirely clear what is the correct name
December 5, 201015 yr Author oooooooooohhhhhh so you only need to put in sda, sdb, sdc, etc. (whatever the respective one for that drive)?
December 5, 201015 yr oooooooooohhhhhh so you only need to put in sda, sdb, sdc, etc. (whatever the respective one for that drive)? Yes, and also on note you will probably want to read this post about the samsung drives
December 5, 201015 yr Author Thanks for the heads up on the samsung drives. And thanks for the other help too
Archived
This topic is now archived and is closed to further replies.