Using NAS4Free as NAS gateway to serve shared SAN storage to the network. Problem is that each time there is a reboot, the iscsi controller numbering changes.
When the numbering changes:
1) the HDDs have to be recreated
2) the mount points redefined
3) all partitions have to be fsck_ufs
4) all mount points re-mounted
The HDDs are formatted as UFS. Is there a way to keep the numbering static between reboots and also avoid fsck? Should I move to a full install with ZFS?
NAS4Free 10.3.0.3 Embedded
2x 3406MHz
8GB RAM
20GB HDD local
Running on top of ESX 6.0u1
EqualLogic SAN with 20TB over 10GB iSCSI
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!
iSCSI initiator numbering changes at reboot
-
davidgordonca
- NewUser

- Posts: 4
- Joined: 07 Jun 2016 19:25
- Status: Offline
-
davidgordonca
- NewUser

- Posts: 4
- Joined: 07 Jun 2016 19:25
- Status: Offline
Re: iSCSI initiator numbering changes at reboot
Any update?
-
mdsystems
- Starter

- Posts: 20
- Joined: 15 Oct 2015 11:08
- Status: Offline
Re: iSCSI initiator numbering changes at reboot
Are you referring to the fact that when your server reboots, the HDDs are given different itentifiers, that is what was da0 is now da1 and da1 becomes da0 (for example)? If so, you may want to consider creating gpt labels on each of your drives and then use the devices by label to create a zfs filesystem, on which you can then create iscsi targets. I do this and it works effectively and survives reboots.
To be honest, I am a little surprised that nas4free does not appear enforce disk labelling so that all disk management is independent of what appears to be the totally random way that freebsd names drives.
To be honest, I am a little surprised that nas4free does not appear enforce disk labelling so that all disk management is independent of what appears to be the totally random way that freebsd names drives.
-
davidgordonca
- NewUser

- Posts: 4
- Joined: 07 Jun 2016 19:25
- Status: Offline
Re: iSCSI initiator numbering changes at reboot
Thank you for the pointer, it worked. Instead of creating disks for every iscsi share and then a mount point, I bypass the disk creation completely. Instead, I use a Custom mount point using the gpt label as you suggested.
- alexey123
- Moderator

- Posts: 1469
- Joined: 19 Aug 2012 08:22
- Location: Israel, Karmiel
- Contact:
- Status: Offline
Re: iSCSI initiator numbering changes at reboot
davidgordonca, see output of It list order of services
I have such problem, but when I boot NAS4Free(tested) from iSCSI - kernel and root also, I not have such problems
UPD:
If you use as iSCSI target row disk and after reboot your disk change his number, some as
DISK NAME BEFORE -- AFTER
boot flash -- da0 ------- da0
disk1 ------- ada1 ------ ada1
disk 2 ------ ada2 ------ ada3
disk3 ------- ada3 ------ ada2
You have hardware trouble. In first - replace power supply. Each disk during start need 3A. If you have 5 disks, your power supply must give 18A on 12V bus
For detect it you can install boot0 FreeBSD boot manager on your da0 and configure his timeout as ~6 sec
Code: Select all
service -rI have such problem, but when I boot NAS4Free(tested) from iSCSI - kernel and root also, I not have such problems
UPD:
If you use as iSCSI target row disk and after reboot your disk change his number, some as
DISK NAME BEFORE -- AFTER
boot flash -- da0 ------- da0
disk1 ------- ada1 ------ ada1
disk 2 ------ ada2 ------ ada3
disk3 ------- ada3 ------ ada2
You have hardware trouble. In first - replace power supply. Each disk during start need 3A. If you have 5 disks, your power supply must give 18A on 12V bus
For detect it you can install boot0 FreeBSD boot manager on your da0 and configure his timeout as ~6 sec
Home12.1.0.4 - Ingva (revision 7091)/ x64-embedded on AMD A8-7600 Radeon R7 A88XM-PLUS/ 16G RAM / UPS Ippon Back Power Pro 600
Lab 12.1.0.4 - Ingva (revision 7091) /x64-embedded on Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz / H61M-DS2 / 4G RAM / UPS Ippon Back Power Pro 600
Lab 12.1.0.4 - Ingva (revision 7091) /x64-embedded on Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz / H61M-DS2 / 4G RAM / UPS Ippon Back Power Pro 600