Pulling my hair out, the last few I still have :-).
First question.
Bought several 8TB drives. In order to have bays available I started to remove several of my 3TB drives.
The first went OK an swapped it with the 8TB drive.
The second gave an error when removing, due to IO error!? Shortly after the scanner returned 16 unreadable sectors and that this drive was overheating (34 C).
Could this be a false positive?
There was a lot of IO during the swapping of the drives, maybe the controller choked?
Drivepool is currently force removing the drive. Am I doing the right thing or should I first scan the whole disk?
Second question.
The 3TB drives will be used in a different server an I usually go in to disk management and delete the current volume and create a new simple volume without path and driveletter when moving drives.
Apparently I was not paying attention and am now stuck with a 2048 GB drive. I am not seeing a 768 GB unallocated part.
Went into diskpart and even there the drive has a max capacity of 2047 GB. tried "clean", "convert to gpt" but no success (diskpart states that it performed requested actions successfully). When listing the volumes it states there are no volumes.
With Seatools I only have the Basic checks option (using an external e-sata hot swap bay).
I know Drivepool can handle this drive since it was showing as 3TB drive and it worked perfectly for almost 2 years. Currently it does not even recognize the drive.
I googled extensivley, but only end up at results that I already have tried.
Is there a way to reset a drive to its factory settings?
Question
Allineedis
Pulling my hair out, the last few I still have :-).
First question.
Bought several 8TB drives. In order to have bays available I started to remove several of my 3TB drives.
The first went OK an swapped it with the 8TB drive.
The second gave an error when removing, due to IO error!? Shortly after the scanner returned 16 unreadable sectors and that this drive was overheating (34 C).
Could this be a false positive?
There was a lot of IO during the swapping of the drives, maybe the controller choked?
Drivepool is currently force removing the drive. Am I doing the right thing or should I first scan the whole disk?
Second question.
The 3TB drives will be used in a different server an I usually go in to disk management and delete the current volume and create a new simple volume without path and driveletter when moving drives.
Apparently I was not paying attention and am now stuck with a 2048 GB drive. I am not seeing a 768 GB unallocated part.
Went into diskpart and even there the drive has a max capacity of 2047 GB. tried "clean", "convert to gpt" but no success (diskpart states that it performed requested actions successfully). When listing the volumes it states there are no volumes.
With Seatools I only have the Basic checks option (using an external e-sata hot swap bay).
I know Drivepool can handle this drive since it was showing as 3TB drive and it worked perfectly for almost 2 years. Currently it does not even recognize the drive.
I googled extensivley, but only end up at results that I already have tried.
Is there a way to reset a drive to its factory settings?
Maybe one of you guys have a trick.
Thank you, thank you, thank you...
Link to comment
Share on other sites
6 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.