Disk ID changes when new Disk is added and unable to format

[phille1989]

Hello everyone
I have a problem with my NAS that I can not sort out.
my system.
MB: ASUS A8N-E
CPU: AMD 3200 + 2,0 Ghz @ 1,0 Ghz
MEM: 2048MB
HDDs:
1st Sata - 250GB for OS
2nd Sata - 1TB
3rd Sata - 1TB (2)
4th Sata - 3TB

Sata 2 and 3 in RAID1

Started OS with all disks except 3TB. The disks ID:
250GB - ada0
1TB - ada1
1TB (2) - ADA2.
configured ada1 and ada2 to RAID1 and everything works fine.

When I then plug my 3TB disk I get an error.
"There is wrong disk ID in the config. Please remove the disk and re-add it or
use 'clear and imports.' "
When I press Clear and Import, it changes all the disks ID to.
250gb, from ada0 to ada2
1TB, from ada1 to ada3
1TB (2), from ada2 to ada1
3TB becomes ada0

When I then try to format 3TB ada0 disk I get a new error message
"Can not format the OS disk"

does anyone know why the disk ID is changed after adding the new disk?
must the OS disk be the ada0 to work properly?
thanks in advance
/ Philip
Sweden

[RedAntz]

Which NAS4FREE version did you use ?
Did you have NAS4Free installed to your 3tb disk prior ?

[phille1989]

It's NAS4Free v9.1.0.1.847
The 3TB disk is brand new and no previous installations of any kind.

[alexey123]

Try reboot server after clear config. Server must reasign links

[RedAntz]

The system still have the config that your OS drive is ada0.
I suspect a restart will reload the config file and refresh it.

[phille1989]

i Will try this tomorrow.

Thanks everyone!

[phille1989]

Hi again
after rebooting the system serveral times, the error message refuses to dissappear.
When i press Clear config and Import Disk the disks appear in wrong order again.

is it possible that the motherboard is conflicting with the amount of storage in the new disk, 3TB? I've had two 2TB connected before without any problems.

[RedAntz]

Hi again
after rebooting the system serveral times, the error message refuses to dissappear.
When i press Clear config and Import Disk the disks appear in wrong order again.

is it possible that the motherboard is conflicting with the amount of storage in the new disk, 3TB? I've had two 2TB connected before without any problems.

I don't think it's the issue of BIOS not supporting > 2TB, since you mentioned that 3TB becomes ada0. Is this a full install ?

If so, can you do the following in console :

Code: Select all

cat /etc/cfdevice

[phille1989]

yes this is a full install.

what will this code do?
should press "clear config and import disks" before inserting the code?

[RedAntz]

Since you have limited knowledge with *nix commands, I'll suggest the heavy handed, but most straightforward way : do a full install again to overwrite your NAS4Free in your 250GB hard disks(with your 3TB disks in the system), so that it will detect all devices at their new sequence.

[phille1989]

I will do so, and hope it will work.
Thanks!

[phille1989]

Everything works fine after a complete reinstallation.

Thanks for the help!

[sodalimon]

Similar issue I've just had...

Add a drive to a free sata port on a cheap sata expansion card (Marvell 88SE9130 AHCI SATA controller).
The OS assigns ada0 to the drive.
All your config has to be made again, reenter smart values for 6 drives all over ONE BY ONE (come on guys how hard could that be)...
Add another record to smart tests queue.

This is what I've always encountered and complained about.
Well I guess, it is IMPOSSIBLE to implement. Cause the drives all (!) have the same serial numbers

Anyway...
What comes next is new to me...

Well, time to format...
Ooops, ada6 ise free to format... Yahoo, that frive is one of those from my raidz2 pool
Should I thrust N4F and go along?


Decided to use shell then... Well, why don't I restart, before that?
Restarted.
OK, it seems, now I can format the new ada0

The OP was lucky, it was their OS drive, so they couldn't format. What if I hadn't noticed?

I wonder, if this was the case all along...
My version is 9.2.0.1 - Shigawire (revision 943)...


I know, if the OS decides to assign ada0 to the new drive, no one can stop it. But just as ZFS is smart as to prevent a mess, the application should be too, in my opinion.

By the way, the source of all evil The bios.
It's so cool, that I have to KVM to the server to be able to boot again (after adding the drive), cause I can't get it to recall which device I set it to boot from...
The funny part is the way the objects are classified.
My original setup:
1. USB Drive
2. None
3. None
etc.

Add a drive. It changes into
1. HDD
2. None

I love modern technology Guess all these were inherited from Mars
Now, we just can't code a proper bios