So I had a freenas box setup with a raid-0 stripe of 2 2TB drives with a single 3TB drive internally backing up that raid. Well I felt compelled to add in another 3TB drive to then create a new raid to replace the existing.. and upon adding it... it decided to not detect the drives correctly. It was saying my new drive was only a 2TB drive and screwed up the drive name in disk mount. Was wondering if this was some oddly known bug that has been resolved in Nas4Free because I am on the second to latest build of nas4free and I'm almost nervous to ever add in a new drive.
It really makes no sense but it happened and went all down hill since then. Luckily I had backups because I had to build out a new server and transfer the data over. And the new drive I put in was a good working drive that was tested.
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
Adding disk corrupts raid
-
Jtcdesigns
- Starter

- Posts: 28
- Joined: 05 Apr 2013 02:04
- Status: Offline
-
danic
- Starter

- Posts: 30
- Joined: 26 Jun 2012 21:07
- Status: Offline
Re: Adding disk corrupts raid
Only support I can give is some older SATA controllers do not have >2TB support. Is your original 3TB drive and new 3TB drive on the same sata controller?
Danic
Nas4Free - AMD X4 960T - GIGABYTE 990FXA-UD3 - 16GB RAM - IBM M1015/IT - Intel RS2WC080/IT- 6x 3TB - 4x 320GB - 3x 640GB - 120GB SSD - 240GB SSD
Nas4Free - AMD X4 960T - GIGABYTE 990FXA-UD3 - 16GB RAM - IBM M1015/IT - Intel RS2WC080/IT- 6x 3TB - 4x 320GB - 3x 640GB - 120GB SSD - 240GB SSD
-
Jtcdesigns
- Starter

- Posts: 28
- Joined: 05 Apr 2013 02:04
- Status: Offline
Re: Adding disk corrupts raid
I wish this place had a notification when someone replies to something I post. Everything is on the same controller.. just using the mobo no raid card. I have come across this same issue once before and it was very frustrating.. and that was with 2TB or smaller drives. Adding one would make the system think the already mounted disk was something else for some odd reason.. and I added the drives in order.... sata0 then sata1 then sata3 and the last one in sata4 screwed it all up.
- raulfg3
- Site Admin

- Posts: 4865
- Joined: 22 Jun 2012 22:13
- Location: Madrid (ESPAÑA)
- Contact:
- Status: Offline
Re: Adding disk corrupts raid
Jtcdesigns wrote:So I had a freenas box setup with a raid-0 stripe of 2 2TB drives with a single 3TB drive internally backing up that raid. Well I felt compelled to add in another 3TB drive to then create a new raid to replace the existing.. and upon adding it... it decided to not detect the drives correctly. It was saying my new drive was only a 2TB drive and screwed up the drive name in disk mount. Was wondering if this was some oddly known bug that has been resolved in Nas4Free because I am on the second to latest build of nas4free and I'm almost nervous to ever add in a new drive.
It really makes no sense but it happened and went all down hill since then. Luckily I had backups because I had to build out a new server and transfer the data over. And the new drive I put in was a good working drive that was tested.
In general there are problems when is a reuse disk in Nas4Free, is recomended to wipe first to delete all metadata prior to use:
http://wiki.nas4free.org/doku.php?id=faq:0129&s[]=wipe
12.1.0.4 - Ingva (revision 7743) on SUPERMICRO X8SIL-F 8GB of ECC RAM, 11x3TB disk in 1 vdev = Vpool = 32TB Raw size , so 29TB usable size (I Have other NAS as Backup)
Wiki
Last changes
HP T510
Wiki
Last changes
HP T510
-
Jtcdesigns
- Starter

- Posts: 28
- Joined: 05 Apr 2013 02:04
- Status: Offline
Re: Adding disk corrupts raid
Thats the weird thing. I had a brand new unformatted disk that I installed and it caused the hard drives to read as something else. Was quite weird to see that my first raid disk was appearing in a completely wrong size and name.