UFS Why can't I mount volume for external local backup disk?

dalpets · Sep 29, 2019

Code:

$ su
Password:
root@FreeBSD11:/home/Brenton # newfs -jU /dev/da0p2
/dev/da0p2: 305244.8MB (625141344 sectors) block size 32768, fragment size 4096
    using 488 cylinder groups of 626.22MB, 20039 blks, 80256 inodes.
    with soft updates
super-block backups (for fsck_ffs -b #) at:
192, 1282688, 2565184, 3847680, 5130176, 6412672, 7695168, 8977664, 10260160,
11542656, 12825152, 14107648, 15390144, 16672640, 17955136, 19237632,
20520128, 21802624, 23085120, 24367616, 25650112, 26932608, 28215104,
29497600, 30780096, 32062592, 33345088, 34627584, 35910080, 37192576,
38475072, 39757568, 41040064, 42322560, 43605056, 44887552, 46170048,
47452544, 48735040, 50017536, 51300032, 52582528, 53865024, 55147520,
56430016, 57712512, 58995008, 60277504, 61560000, 62842496, 64124992,
65407488, 66689984, 67972480, 69254976, 70537472, 71819968, 73102464,
74384960, 75667456, 76949952, 78232448, 79514944, 80797440, 82079936,
83362432, 84644928, 85927424, 87209920, 88492416, 89774912, 91057408,
92339904, 93622400, 94904896, 96187392, 97469888, 98752384, 100034880,
101317376, 102599872, 103882368, 105164864, 106447360, 107729856, 109012352,
110294848, 111577344, 112859840, 114142336, 115424832, 116707328, 117989824,
119272320, 120554816, 121837312, 123119808, 124402304, 125684800, 126967296,
128249792, 129532288, 130814784, 132097280, 133379776, 134662272, 135944768,
137227264, 138509760, 139792256, 141074752, 142357248, 143639744, 144922240,
146204736, 147487232, 148769728, 150052224, 151334720, 152617216, 153899712,
155182208, 156464704, 157747200, 159029696, 160312192, 161594688, 162877184,
164159680, 165442176, 166724672, 168007168, 169289664, 170572160, 171854656,
173137152, 174419648, 175702144, 176984640, 178267136, 179549632, 180832128,
182114624, 183397120, 184679616, 185962112, 187244608, 188527104, 189809600,
191092096, 192374592, 193657088, 194939584, 196222080, 197504576, 198787072,
200069568, 201352064, 202634560, 203917056, 205199552, 206482048, 207764544,
209047040, 210329536, 211612032, 212894528, 214177024, 215459520, 216742016,
218024512, 219307008, 220589504, 221872000, 223154496, 224436992, 225719488,
227001984, 228284480, 229566976, 230849472, 232131968, 233414464, 234696960,
235979456, 237261952, 238544448, 239826944, 241109440, 242391936, 243674432,
244956928, 246239424, 247521920, 248804416, 250086912, 251369408, 252651904,
253934400, 255216896, 256499392, 257781888, 259064384, 260346880, 261629376,
262911872, 264194368, 265476864, 266759360, 268041856, 269324352, 270606848,
271889344, 273171840, 274454336, 275736832, 277019328, 278301824, 279584320,
280866816, 282149312, 283431808, 284714304, 285996800, 287279296, 288561792,
289844288, 291126784, 292409280, 293691776, 294974272, 296256768, 297539264,
298821760, 300104256, 301386752, 302669248, 303951744, 305234240, 306516736,
307799232, 309081728, 310364224, 311646720, 312929216, 314211712, 315494208,
316776704, 318059200, 319341696, 320624192, 321906688, 323189184, 324471680,
325754176, 327036672, 328319168, 329601664, 330884160, 332166656, 333449152,
334731648, 336014144, 337296640, 338579136, 339861632, 341144128, 342426624,
343709120, 344991616, 346274112, 347556608, 348839104, 350121600, 351404096,
352686592, 353969088, 355251584, 356534080, 357816576, 359099072, 360381568,
361664064, 362946560, 364229056, 365511552, 366794048, 368076544, 369359040,
370641536, 371924032, 373206528, 374489024, 375771520, 377054016, 378336512,
379619008, 380901504, 382184000, 383466496, 384748992, 386031488, 387313984,
388596480, 389878976, 391161472, 392443968, 393726464, 395008960, 396291456,
397573952, 398856448, 400138944, 401421440, 402703936, 403986432, 405268928,
406551424, 407833920, 409116416, 410398912, 411681408, 412963904, 414246400,
415528896, 416811392, 418093888, 419376384, 420658880, 421941376, 423223872,
424506368, 425788864, 427071360, 428353856, 429636352, 430918848, 432201344,
433483840, 434766336, 436048832, 437331328, 438613824, 439896320, 441178816,
442461312, 443743808, 445026304, 446308800, 447591296, 448873792, 450156288,
451438784, 452721280, 454003776, 455286272, 456568768, 457851264, 459133760,
460416256, 461698752, 462981248, 464263744, 465546240, 466828736, 468111232,
469393728, 470676224, 471958720, 473241216, 474523712, 475806208, 477088704,
478371200, 479653696, 480936192, 482218688, 483501184, 484783680, 486066176,
487348672, 488631168, 489913664, 491196160, 492478656, 493761152, 495043648,
496326144, 497608640, 498891136, 500173632, 501456128, 502738624, 504021120,
505303616, 506586112, 507868608, 509151104, 510433600, 511716096, 512998592,
514281088, 515563584, 516846080, 518128576, 519411072, 520693568, 521976064,
523258560, 524541056, 525823552, 527106048, 528388544, 529671040, 530953536,
532236032, 533518528, 534801024, 536083520, 537366016, 538648512, 539931008,
541213504, 542496000, 543778496, 545060992, 546343488, 547625984, 548908480,
550190976, 551473472, 552755968, 554038464, 555320960, 556603456, 557885952,
559168448, 560450944, 561733440, 563015936, 564298432, 565580928, 566863424,
568145920, 569428416, 570710912, 571993408, 573275904, 574558400, 575840896,
577123392, 578405888, 579688384, 580970880, 582253376, 583535872, 584818368,
586100864, 587383360, 588665856, 589948352, 591230848, 592513344, 593795840,
595078336, 596360832, 597643328, 598925824, 600208320, 601490816, 602773312,
604055808, 605338304, 606620800, 607903296, 609185792, 610468288, 611750784,
613033280, 614315776, 615598272, 616880768, 618163264, 619445760, 620728256,
622010752, 623293248, 624575744
Using inode 4 in cg 0 for 33554432 byte journal
newfs: soft updates journaling set
mount: /dev/da0p2: operation not permitted
root@FreeBSD11:/home/Brenton #
CANNOT MOUNT VOLUME

ralphbsz · Sep 29, 2019

Your cut and paste gets confused at the bottom. I can't see the mount command line. What directory are you trying to mount it on? Do you have permissions to do that? I presume you have IO permissions on the device, otherwise the newfs command wouldn't have worked.

dalpets · Sep 29, 2019

I haven't nominated a directory. I'm trying to mount a 1TB ufs disk as a backup disk. How do I check the IO permissions?
Thank you for helping. I'm a relatively new user.
The error message I'm getting is as follows;

Code:

Using inode 4 in cg 0 for 33554432 byte journal
newfs: soft updates journaling set
mount: /dev/da0p2: operation not permitted

Beastie · Sep 29, 2019

dalpets said:
I haven't nominated a directory.

What do you mean by that? You need a directory (preferably empty) to act as a mountpoint. That's how it works. What command are you using to mount the device? It must be in the form mount /dev/device /path/to/mountpoint.

dalpets said:
I'm trying to mount a 1TB ufs disk as a backup disk. How do I check the IO permissions?

https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#idp49149688

You also must add your user to the operator group.

ralphbsz · Sep 29, 2019

OK, let's slow down. Looking at your output above, we can see that you have entered one command, namely newfs. The options on the command look reasonable (-jU for soft updates and soft updatse journaling). The device name is plausible. The command proceeds, and seems to succeed. It's last two lines of output are "Using ... for journal" and "... journaling set", and those are not error messages.

Then, for some reason we can not see, there is an attempt to mount the new file system. The transcript doesn't contain a mount command, and you say that you have not "nominated a directory" as a mount point. This makes no sense: every file system needs a mount point to be mounted, and that mount point needs to be a directory. But the mount point doesn't have to be on the command line of the mount command, it can be in the file /etc/fstab.

Is it possible that you are not actually issuing these commands from the command line, but as part of another work flow, perhaps from a GUI tool? Is it possible that the mount point came from /etc/fstab?

Given the prompt in the output above (the "#" sign), I guess that you are running as root; in that case, permission problems are unlikely. But that's just a guess.

In order for us to help you, we need more information: How did you issue the commands, and what is the content of /etc/fstab.

dalpets · Sep 30, 2019

Thanks all for your help. Unfortunately, I haven't had success with all your appreciated suggestions.
One of the problems I am having is that the sade editor will allow me to record a label but not to record a mount point.
The other is that I do not know how to find the full pathname to the data directory.
Below are some output snippets of my failed attempts.
I can't make any changes to the sade editor because when I now try to modify it, it says its busy.
Just to recap the da0 device (a WD 1TB sata nas drive) is an external drive in a usb drive caddy. I have tried a second nas drive with the same result, so I think I can rule out disk failure.
The Luckybackup software I have does not recognise the data folder on the backup drive.

operator

Code:

crw-r-----   1 root     operator  0x7f Sep 30 11:30 da0p1
crw-r-----   1 root     operator  0x80 Sep 30 11:30 da0p2

/etc/fstab

Code:

# Device        Mountpoint      FStype  Options Dump    Pass#
/dev/ada0p2     /               ufs     rw      1       1
/dev/ada0p3     none            swap    sw      0       0
proc    /proc           procfs  rw      0       0
/dev/ada0p2     /               ufs     rw      1       1
/dev/da0p2          /data       ufs     rw      2       2 (entered manually)
           ┌                
$ su
Password:
root@FreeBSD11:/home/Brenton # [B]mount[/B]
/dev/ada0p2 on / (ufs, local, journaled soft-updates)
devfs on /dev (devfs, local, multilabel)
procfs on /proc (procfs, local)
/dev/gptid/bdc8d51d-e1a8-11e9-8fac-00d8615800d0 on /media/disk (ufs, local, nosuid, soft-updates)
/dev/gptid/8babe8b9-e259-11e9-a13c-00d8615800d0 on /media/disk-1 (ufs, local, nosuid, journaled soft-updates)


root@FreeBSD11:/home/Brenton # mount /dev/da0p2 /data (data directory created)
mount: /dev/da0p2: Operation not permitted

ralphbsz · Sep 30, 2019

I have no idea what a sade editor is. When I do a web search for it, I find references to the Marquis de Sade, which is probably not appropriate reading material. Can you explain what an editor has to do with it?

I also don't understand what you mean by the "full pathname to the data directory". That seems pretty clear: At the very end, you show the mount command, and it is trying to mount on /data, which must be the full pathname.

Everything on your outputs look right: The directory listing of devices in /dev/da* look good, your /etc/fstab seems right, your mount output is fine.

I have no idea what the two "media..." things are. Could it be that your disk /dev/da0p2 is already mounted as one of the /media/... mount points? Could it be that you are running some auto-mounter, which found that device, and mounted it using a different device name (namely the gpt ID) already, and the "operation not permitted" message simply means that you can't mount the same disk in two different places?

shkhln · Sep 30, 2019

This thread looks like a continuation of https://forums.freebsd.org/threads/error-device-busy.72408.

shkhln · Sep 30, 2019

dalpets said:
/dev/gptid/bdc8d51d-e1a8-11e9-8fac-00d8615800d0 on /media/disk (ufs, local, nosuid, soft-updates)
/dev/gptid/8babe8b9-e259-11e9-a13c-00d8615800d0 on /media/disk-1 (ufs, local, nosuid, journaled soft-updates)

I'll be surprised of one of those is not /dev/da0.

shkhln · Sep 30, 2019

Ah, now I see. Assuming https://forums.freebsd.org/threads/error-device-busy.72408/#post-440318 still applies, there is only one partition on disk and da0p2 doesn't exist. That should produce a different error message, though

Just how many disks are there?

dalpets · Sep 30, 2019

ralphbsz said:
I have no idea what a sade editor is. When I do a web search for it, I find references to the Marquis de Sade, which is probably not appropriate reading material. Can you explain what an editor has to do with it?

SEE: https://man.freebsd.org › sade
It is a graphical editor like bsdinstall, but limited to partition metrics

dalpets · Oct 1, 2019

shkhln said:
Ah, now I see. Assuming https://forums.freebsd.org/threads/error-device-busy.72408/#post-440318 still applies, there is only one partition on disk and da0p2 doesn't exist. That should produce a different error message, though Just how many disks are there?

only 2: ada0 & dao

dalpets · Oct 1, 2019

In order for us to help you, we need more information: How did you issue the commands, and what is the content of /etc/fstab.

/etc/fstab

Code:

Device        Mountpoint      FStype  Options Dump    Pass#
/dev/ada0p2     /               ufs     rw      1       1
/dev/ada0p3     none            swap    sw      0       0
proc    /proc           procfs  rw      0       0
/dev/ada0p2     /               ufs     rw      1       1
/dev/da0p2          /data       ufs     rw      2       2 #this was inserted manually

$ su
Password:
root@FreeBSD11:/home/Brenton # camcontrol devlist
<WDC WD10EFRX-68FYTN0 82.00A82>    at scbus2 target 0 lun 0 (ada0,pass0)
<AHCI SGPIO Enclosure 1.00 0001>   at scbus6 target 0 lun 0 (ses0,pass1)
<SABRENT  0104> [/B]                   at scbus9 target 0 lun 0 (da0,pass2)
root@FreeBSD11:/home/Brenton #
-----------------------------------------------------------------------------------------------------------------------------
$ su
Password:
root@FreeBSD11:/home/Brenton # gpart show -p da0
=>       40  625142368    da0  GPT  (298G)
         40       1024  da0p1  freebsd-boot  (512K)
       1064  625141344  da0p2  freebsd-ufs  (298G)

root@FreeBSD11:/home/Brenton # gpart show -p da0p2
gpart: No such geom: da0p2.
root@FreeBSD11:/home/Brenton #
-------------------------------------------------------------------------------------------------------------------------------
root@FreeBSD11:/home/Brenton # mount /dev/da0p2  /data
mount: /dev/da0p2: Device busy
root@FreeBSD11:/home/Brenton #

-------------------------------------------------------------------------------------------------------------------------------

My backup program Luckybackup does not recognize the required backup disk /dev/da0p2 or its directory 'data'. I actually created that directory & it shows as empty in the / directory structure.
It seems that I am going around in circles with this & wasting people's time & that I should be going back to basics. I am very appreciative of your help so far and I would ask if there is a set of logical commands that I could use to diagnose the problem e.g., for starters is the dao disk really mounted & where is it mounted in more than one place ('busy').....etc, etc.
If I can achieve this I can get rid of windows once & for all. If I can't I'll have to completely reinstall this OS & try again.
Thanks

shkhln · Oct 2, 2019

glabel status?

dalpets · Oct 3, 2019

shkhln said:
glabel status?

root@FreeBSD11:/home/Brenton # glabel status
Name Status Components
gptid/f62cb7dd-e4c9-11e9-8668-00d8615800d0 N/A ada0p1
gptid/bdc8d51d-e1a8-11e9-8fac-00d8615800d0 N/A da0p1
---------------------------------------------------------------------------------------------

Why is /dev/ad0p2 not recognised? Thanks for any help.
root@FreeBSD11:/home/Brenton # newfs -jU /dev/da0p2
newfs: /dev/da0p2: failed to open disk for writing
---------------------------------------------------------------------------------------------
┌──────────────────Partition Editor────────────────────┐
│ Create partitions for FreeBSD. No changes will be │
│ made until you select Finish. │
│┌────────────────────────────────────────────────────┐│
││ada0 932 GB GPT ││
││ ada0p1 512 KB freebsd-boot ││
││ ada0p2 928 GB freebsd-ufs / ││
││ ada0p3 3.5 GB freebsd-swap none ││
││da0 298 GB GPT ││
││ da0p1 512 KB freebsd-boot ││
││ da0p2 298 GB freebsd-ufs /data ││
││ ││
│└────────────────────────────────────────────────────┘│
├──────────────────────────────────────────────────────┤
│<Create> <Delete> <Modify> <Revert> < Auto > <Finish> │
└──────────────────────────────────────────────────────┘
---------------------------------------------------------------------------------------------------------------------------------------------
$ mount /dev/da0p2 /data
mount: /dev/da0p2: Operation not permitted
$ mount
/dev/ada0p2 on / (ufs, local, journaled soft-updates)
devfs on /dev (devfs, local, multilabel)
procfs on /proc (procfs, local)
/dev/da0p2 on /data (ufs, local, journaled soft-updates)
/dev/gptid/bdc8d51d-e1a8-11e9-8fac-00d8615800d0 on /media/disk (ufs, local, nosuid, soft-updates)
$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ada0p2 899G 7.1G 820G 1% /
devfs 1.0K 1.0K 0B 100% /dev
procfs 4.0K 4.0K 0B 100% /proc
/dev/da0p2 289G 32M 266G 0% /data
/dev/gptid/bdc8d51d-e1a8-11e9-8fac-00d8615800d0 316K 8.0K 284K 3% /media/disk
---------------------------------------------------------------------------------------------------------------------------------------------------

Warning - KBackup
The file '/data/backup XXXXXXXX_cannot be opened for writing

T-Daemon · Oct 3, 2019

You have a duplicate entry for the systems root in /etc/fstab

dalpets said:
# Device Mountpoint FStype Options Dump Pass#
/dev/ada0p2 / ufs rw 1 1
/dev/ada0p3 none swap sw 0 0
proc /proc procfs rw 0 0
/dev/ada0p2 / ufs rw 1 1
/dev/da0p2 /data ufs rw 2 2 (entered manually)

I'm following this thread from the beginning, and have tried to reproduse the situation, but was unable to.

The hostname in the shell prompt indicates you are runing FreeBSD 11, which version exactly? Please post uname -a, dmesg with all external devices plugged in you wish to use, and /etc/rc.conf.

What are those disks mounted at /media/disk and /media/disk-1?

Also it would be helpful if you list all steps you have taken and every command you have executed or setting entered (sade(8)) to initialize the said external drive.

dalpets · Oct 3, 2019

T-Daemon said:
You have a duplicate entry for the systems root in /etc/fstab

I'm following this thread from the beginning, and have tried to reproduse the situation, but was unable to.

The hostname in the shell prompt indicates you are runing FreeBSD 11, which version exactly? Please post uname -a, dmesg with all external devices plugged in you wish to use, and /etc/rc.conf.

What are those disks mounted at /media/disk and /media/disk-1?

Also it would be helpful if you list all steps you have taken and every command you have executed or setting entered (sade(8)) to initialize the said external drive.

Duplicate in /etc/fstab has not applied since I reinstalled the system a few days ago. It now reads;

Code:

Device        Mountpoint      FStype  Options Dump    Pass#
/dev/ada0p2     /               ufs     rw      1       1
/dev/ada0p3     none            swap    sw      0       0
proc           /proc            procfs   rw     0       0
/dev/da0p2     /data            ufs     rw      2       2

Code:

root@FreeBSD11:/home/Brenton # uname -a
FreeBSD FreeBSD11.3 11.3-RELEASE FreeBSD 11.3-RELEASE #0 r349754: Fri Jul  5 04:31:33 UTC 2019     [EMAIL]root@releng2.nyi.freebsd.org[/EMAIL]:/usr/obj/usr/src/sys/GENERIC  i386

dmesg

Code:

ukbd0 on uhub0
ukbd0: <USB Keyboard> on usbus0
kbd2 at ukbd0
ugen0.4: <SABRENT SABRENT> at usbus0
umass0 on uhub0
umass0: <SABRENT SABRENT, class 0/0, rev 2.10/1.04, addr 3> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:9:0: Attached to scbus9
da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
da0: <SABRENT  0104> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number DB98765432143
da0: 40.000MB/s transfers
da0: 305245MB (625142448 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
lo0: link state changed to UP
em0: link state changed to UP
ums0 on uhub0
ums0: <Microsoft Microsoft Basic Optical Mouse v2.0, class 0/0, rev 1.10/1.99, addr 1> on usbus0
ums0: 3 buttons and [XYZ] coordinates ID=0
uhid0 on uhub0
uhid0: <USB Keyboard> on usbus0
pid 1001 (tracker-miner-fs), jid 0, uid 1001: exited on signal 11 (core dumped)

What are those disks mounted at /media/disk and /media/disk-1

I wouldn't have a clue, I didn't initiate them, /dev/gptid/ generated them. Maybe since the re-installation they have disappeared.

Code:

root@FreeBSD11:/home/Brenton # uname -a
FreeBSD FreeBSD11.3 11.3-RELEASE FreeBSD 11.3-RELEASE #0 r349754: Fri Jul  5 04:31:33 UTC 2019     [EMAIL]root@releng2.nyi.freebsd.org[/EMAIL]:/usr/obj/usr/src/sys/GENERIC  i386

Code:

root@FreeBSD11:/home/Brenton # dmesg
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.3-RELEASE #0 r349754: Fri Jul  5 04:31:33 UTC 2019
    root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386
FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLVM 8.0.0)
VT(vga): resolution 640x480
CPU: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz (3600.14-MHz 686-class CPU)
  Origin="GenuineIntel"  Id=0x906eb  Family=0x6  Model=0x9e  Stepping=11
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x7ffafbbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100000<NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended Features=0x29c67af<FSGSBASE,TSCADJ,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE>
  Structured Extended Features3=0x9c000000<IBPB,STIBP,L1DFL,SSBD>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 2232438784 (2129 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <ALASKA A M I >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
ioapic0 <Version 2.0> irqs 0-119 on motherboard
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1800072129 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
module_register_init: MOD_LOAD (vesa, 0xc1022f50, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
acpi0: <ALASKA A M I > on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 24000000 Hz quality 950
Event timer "HPET" frequency 24000000 Hz quality 550
Event timer "HPET1" frequency 24000000 Hz quality 440
Event timer "HPET2" frequency 24000000 Hz quality 440
Event timer "HPET3" frequency 24000000 Hz quality 440
Event timer "HPET4" frequency 24000000 Hz quality 440
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pcib0: _OSC returned error 0x10
pci0: <ACPI PCI bus> on pcib0
vgapci0: <VGA-compatible display> port 0x3000-0x303f mem 0xa0000000-0xa0ffffff,0x90000000-0x9fffffff irq 16 at device 2.0 on pci0
vgapci0: Boot video device
xhci0: <XHCI (generic) USB 3.0 controller> mem 0xa1120000-0xa112ffff irq 16 at device 20.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
pci0: <memory, RAM> at device 20.2 (no driver attached)
pci0: <simple comms> at device 22.0 (no driver attached)
ahci0: <Intel Cannon Lake AHCI SATA controller> port 0x3090-0x3097,0x3080-0x3083,0x3060-0x307f mem 0xa1134000-0xa1135fff,0xa113a000-0xa113a0ff,0xa1139000-0xa11397ff irq 16 at device 23.0 on pci0
ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
ahciem0: <AHCI enclosure management bridge> on ahci0
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
hdac0: <Intel Coffee Lake HDA Controller> mem 0xa1130000-0xa1133fff,0xa1000000-0xa10fffff irq 16 at device 31.3 on pci0
pci0: <serial bus> at device 31.5 (no driver attached)
em0: <Intel(R) PRO/1000 Network Connection 7.6.1-k> mem 0xa1100000-0xa111ffff irq 16 at device 31.6 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: 00:d8:61:58:00:d0
acpi_button0: <Sleep Button> on acpi0
acpi_button1: <Power Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_syscontainer0: <System Container> on acpi0
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xcffff pnpid ORM0000 on isa0
ata0: <ATA channel> at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0
ata1: <ATA channel> at port 0x170-0x177,0x376 irq 15 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atrtc0: <AT realtime clock> at port 0x70 irq 8 on isa0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
ppc0: parallel port not found.
uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
uart1: <16550 or compatible> at port 0x2f8 irq 3 on isa0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est3: <Enhanced SpeedStep Frequency Control> on cpu3
Timecounters tick every 1.000 msec
hdacc0: <Realtek ALC892 HDA CODEC> at cad 0 on hdac0
hdaa0: <Realtek ALC892 Audio Function Group> at nid 1 on hdacc0
pcm0: <Realtek ALC892 (Rear Analog 5.1/2.0)> at nid 20,22,21 and 24,26 on hdaa0
pcm1: <Realtek ALC892 (Front Analog)> at nid 27 and 25 on hdaa0
pcm2: <Realtek ALC892 (Rear Digital)> at nid 30 on hdaa0
hdacc1: <Intel Kaby Lake HDA CODEC> at cad 2 on hdac0
hdaa1: <Intel Kaby Lake Audio Function Group> at nid 1 on hdacc1
pcm3: <Intel Kaby Lake (HDMI/DP 8ch)> at nid 3 on hdaa1
ugen0.1: <0x8086 XHCI root HUB> at usbus0
ses0 at ahciem0 bus 0 scbus6 target 0 lun 0
uhub0: ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
ada0 at ahcich2 bus 0 scbus2 target 0 lun 0
<0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ada0: <WDC WD10EFRX-68FYTN0 82.00A82> ACS-2 ATA SATA 3.x device
ada0: Serial Number WD-WCC4J3CZDRRK
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 953869MB (1953525168 512 byte sectors)
ada0: quirks=0x1<4K>
Trying to mount root from ufs:/dev/ada0p2 [rw]...
random: unblocking device.
uhub0: 22 ports with 22 removable, self powered
ugen0.2: <Microsoft Microsoft Basic Optical Mouse v2.0> at usbus0
ugen0.3: <Logitech USB Keyboard> at usbus0
ukbd0 on uhub0
ukbd0: <USB Keyboard> on usbus0
kbd2 at ukbd0
ugen0.4: <SABRENT SABRENT> at usbus0
umass0 on uhub0
umass0: <SABRENT SABRENT, class 0/0, rev 2.10/1.04, addr 3> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:9:0: Attached to scbus9
da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
da0: <SABRENT  0104> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number DB98765432143
da0: 40.000MB/s transfers
da0: 305245MB (625142448 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
lo0: link state changed to UP
em0: link state changed to UP
ums0 on uhub0
ums0: <Microsoft Microsoft Basic Optical Mouse v2.0, class 0/0, rev 1.10/1.99, addr 1> on usbus0
ums0: 3 buttons and [XYZ] coordinates ID=0
uhid0 on uhub0
uhid0: <USB Keyboard> on usbus0
pid 1001 (tracker-miner-fs), jid 0, uid 1001: exited on signal 11 (core dumped)

Code:

root@FreeBSD11:/home/Brenton # sade

What you see below is sade as it appears now at boot time in the new installation, except that I created the 'data' entry there as a folder in the (root?) directory for backups on /dev/da0p2 (the external hard drive).
In /etc/fstab I have manually set the 'data' disk to function from boot (2/2).
It may be of help to know that when I run kbackup that the backup is not going to the 'data' folder in /dev/da0p2 as intended. It remains empty. Is this because 'mkdir' is too generalised a command. In other words how does that bare command distinguish between the /dev/ada0p2 & /dev/da0p2 drives. The fact that I have added /data to da0p2, in the editor below, has obviously not had any effect.

Code:

           ┌──────────────────Partition Editor────────────────────┐
           │ Create partitions for FreeBSD. No changes will be    │
           │ made until you select Finish.                        │
           │┌────────────────────────────────────────────────────┐│
           ││ada0            932 GB  GPT                         ││
           ││  ada0p1        512 KB  freebsd-boot                ││
           ││  ada0p2        928 GB  freebsd-ufs    /            ││
           ││  ada0p3        3.5 GB  freebsd-swap   none         ││
           ││da0             298 GB  GPT                         ││
           ││  da0p1         512 KB  freebsd-boot                ││
           ││  da0p2         298 GB  freebsd-ufs    /data        ││
           ││                                                    ││
           │└────────────────────────────────────────────────────┘│
           ├──────────────────────────────────────────────────────┤
           │<Create> <Delete> <Modify> <Revert> < Auto > <Finish> │
           └──────────────────────────────────────────────────────┘

SirDice · Oct 3, 2019

dalpets please format your posts properly.

Formatting Guidelines

D-FENS · Oct 3, 2019

dalpets said:

Duplicate in /etc/fstab has not applied since I reinstalled the system a few days ago. It now reads;

Code:

Device        Mountpoint      FStype  Options Dump    Pass#
/dev/ada0p2     /               ufs     rw      1       1
/dev/ada0p3     none            swap    sw      0       0
proc           /proc            procfs   rw     0       0
/dev/da0p2     /data            ufs     rw      2       2

Code:

root@FreeBSD11:/home/Brenton # uname -a
FreeBSD FreeBSD11.3 11.3-RELEASE FreeBSD 11.3-RELEASE #0 r349754: Fri Jul  5 04:31:33 UTC 2019     [EMAIL]root@releng2.nyi.freebsd.org[/EMAIL]:/usr/obj/usr/src/sys/GENERIC  i386

dmesg

Code:

ukbd0 on uhub0
ukbd0: <USB Keyboard> on usbus0
kbd2 at ukbd0
ugen0.4: <SABRENT SABRENT> at usbus0
umass0 on uhub0
umass0: <SABRENT SABRENT, class 0/0, rev 2.10/1.04, addr 3> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:9:0: Attached to scbus9
da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
da0: <SABRENT  0104> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number DB98765432143
da0: 40.000MB/s transfers
da0: 305245MB (625142448 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
lo0: link state changed to UP
em0: link state changed to UP
ums0 on uhub0
ums0: <Microsoft Microsoft Basic Optical Mouse v2.0, class 0/0, rev 1.10/1.99, addr 1> on usbus0
ums0: 3 buttons and [XYZ] coordinates ID=0
uhid0 on uhub0
uhid0: <USB Keyboard> on usbus0
pid 1001 (tracker-miner-fs), jid 0, uid 1001: exited on signal 11 (core dumped)

What are those disks mounted at /media/disk and /media/disk-1

I wouldn't have a clue, I didn't initiate them, /dev/gptid/ generated them. Maybe since the re-installation they have disappeared.

Code:

root@FreeBSD11:/home/Brenton # uname -a
FreeBSD FreeBSD11.3 11.3-RELEASE FreeBSD 11.3-RELEASE #0 r349754: Fri Jul  5 04:31:33 UTC 2019     [EMAIL]root@releng2.nyi.freebsd.org[/EMAIL]:/usr/obj/usr/src/sys/GENERIC  i386

Code:

root@FreeBSD11:/home/Brenton # dmesg
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.3-RELEASE #0 r349754: Fri Jul  5 04:31:33 UTC 2019
    root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386
FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on LLVM 8.0.0)
VT(vga): resolution 640x480
CPU: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz (3600.14-MHz 686-class CPU)
  Origin="GenuineIntel"  Id=0x906eb  Family=0x6  Model=0x9e  Stepping=11
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x7ffafbbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100000<NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended Features=0x29c67af<FSGSBASE,TSCADJ,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE>
  Structured Extended Features3=0x9c000000<IBPB,STIBP,L1DFL,SSBD>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 2232438784 (2129 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <ALASKA A M I >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
ioapic0 <Version 2.0> irqs 0-119 on motherboard
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1800072129 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
module_register_init: MOD_LOAD (vesa, 0xc1022f50, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
nexus0
vtvga0: <VT VGA driver> on motherboard
cryptosoft0: <software crypto> on motherboard
acpi0: <ALASKA A M I > on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 24000000 Hz quality 950
Event timer "HPET" frequency 24000000 Hz quality 550
Event timer "HPET1" frequency 24000000 Hz quality 440
Event timer "HPET2" frequency 24000000 Hz quality 440
Event timer "HPET3" frequency 24000000 Hz quality 440
Event timer "HPET4" frequency 24000000 Hz quality 440
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pcib0: _OSC returned error 0x10
pci0: <ACPI PCI bus> on pcib0
vgapci0: <VGA-compatible display> port 0x3000-0x303f mem 0xa0000000-0xa0ffffff,0x90000000-0x9fffffff irq 16 at device 2.0 on pci0
vgapci0: Boot video device
xhci0: <XHCI (generic) USB 3.0 controller> mem 0xa1120000-0xa112ffff irq 16 at device 20.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
pci0: <memory, RAM> at device 20.2 (no driver attached)
pci0: <simple comms> at device 22.0 (no driver attached)
ahci0: <Intel Cannon Lake AHCI SATA controller> port 0x3090-0x3097,0x3080-0x3083,0x3060-0x307f mem 0xa1134000-0xa1135fff,0xa113a000-0xa113a0ff,0xa1139000-0xa11397ff irq 16 at device 23.0 on pci0
ahci0: AHCI v1.31 with 6 6Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
ahciem0: <AHCI enclosure management bridge> on ahci0
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
hdac0: <Intel Coffee Lake HDA Controller> mem 0xa1130000-0xa1133fff,0xa1000000-0xa10fffff irq 16 at device 31.3 on pci0
pci0: <serial bus> at device 31.5 (no driver attached)
em0: <Intel(R) PRO/1000 Network Connection 7.6.1-k> mem 0xa1100000-0xa111ffff irq 16 at device 31.6 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: 00:d8:61:58:00:d0
acpi_button0: <Sleep Button> on acpi0
acpi_button1: <Power Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_syscontainer0: <System Container> on acpi0
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xcffff pnpid ORM0000 on isa0
ata0: <ATA channel> at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0
ata1: <ATA channel> at port 0x170-0x177,0x376 irq 15 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atrtc0: <AT realtime clock> at port 0x70 irq 8 on isa0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
ppc0: parallel port not found.
uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
uart1: <16550 or compatible> at port 0x2f8 irq 3 on isa0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est3: <Enhanced SpeedStep Frequency Control> on cpu3
Timecounters tick every 1.000 msec
hdacc0: <Realtek ALC892 HDA CODEC> at cad 0 on hdac0
hdaa0: <Realtek ALC892 Audio Function Group> at nid 1 on hdacc0
pcm0: <Realtek ALC892 (Rear Analog 5.1/2.0)> at nid 20,22,21 and 24,26 on hdaa0
pcm1: <Realtek ALC892 (Front Analog)> at nid 27 and 25 on hdaa0
pcm2: <Realtek ALC892 (Rear Digital)> at nid 30 on hdaa0
hdacc1: <Intel Kaby Lake HDA CODEC> at cad 2 on hdac0
hdaa1: <Intel Kaby Lake Audio Function Group> at nid 1 on hdacc1
pcm3: <Intel Kaby Lake (HDMI/DP 8ch)> at nid 3 on hdaa1
ugen0.1: <0x8086 XHCI root HUB> at usbus0
ses0 at ahciem0 bus 0 scbus6 target 0 lun 0
uhub0: ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
ada0 at ahcich2 bus 0 scbus2 target 0 lun 0
<0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ada0: <WDC WD10EFRX-68FYTN0 82.00A82> ACS-2 ATA SATA 3.x device
ada0: Serial Number WD-WCC4J3CZDRRK
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 953869MB (1953525168 512 byte sectors)
ada0: quirks=0x1<4K>
Trying to mount root from ufs:/dev/ada0p2 [rw]...
random: unblocking device.
uhub0: 22 ports with 22 removable, self powered
ugen0.2: <Microsoft Microsoft Basic Optical Mouse v2.0> at usbus0
ugen0.3: <Logitech USB Keyboard> at usbus0
ukbd0 on uhub0
ukbd0: <USB Keyboard> on usbus0
kbd2 at ukbd0
ugen0.4: <SABRENT SABRENT> at usbus0
umass0 on uhub0
umass0: <SABRENT SABRENT, class 0/0, rev 2.10/1.04, addr 3> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:9:0: Attached to scbus9
da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
da0: <SABRENT  0104> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number DB98765432143
da0: 40.000MB/s transfers
da0: 305245MB (625142448 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
lo0: link state changed to UP
em0: link state changed to UP
ums0 on uhub0
ums0: <Microsoft Microsoft Basic Optical Mouse v2.0, class 0/0, rev 1.10/1.99, addr 1> on usbus0
ums0: 3 buttons and [XYZ] coordinates ID=0
uhid0 on uhub0
uhid0: <USB Keyboard> on usbus0
pid 1001 (tracker-miner-fs), jid 0, uid 1001: exited on signal 11 (core dumped)

Code:

root@FreeBSD11:/home/Brenton # sade

What you see below is sade as it appears now at boot time in the new installation, except that I created the 'data' entry there as a folder in the (root?) directory for backups on /dev/da0p2 (the external hard drive).
In /etc/fstab I have manually set the 'data' disk to function from boot (2/2).
It may be of help to know that when I run kbackup that the backup is not going to the 'data' folder in /dev/da0p2 as intended. It remains empty. Is this because 'mkdir' is too generalised a command. In other words how does that bare command distinguish between the /dev/ada0p2 & /dev/da0p2 drives. The fact that I have added /data to da0p2, in the editor below, has obviously not had any effect. Code: ┌──────────────────Partition Editor────────────────────┐ │ Create partitions for FreeBSD. No changes will be │ │ made until you select Finish. │ │┌────────────────────────────────────────────────────┐│ ││ada0 932 GB GPT ││ ││ ada0p1 512 KB freebsd-boot ││ ││ ada0p2 928 GB freebsd-ufs / ││ ││ ada0p3 3.5 GB freebsd-swap none ││ ││da0 298 GB GPT ││ ││ da0p1 512 KB freebsd-boot ││ ││ da0p2 298 GB freebsd-ufs /data ││ ││ ││ │└────────────────────────────────────────────────────┘│ ├──────────────────────────────────────────────────────┤ │<Create> <Delete> <Modify> <Revert> < Auto > <Finish> │ └──────────────────────────────────────────────────────┘

FreeBSD offers different ways to address a partition: by device name and partition number (like /dev/da0p2), by GPT id (this comes from the partitioning manager): /dev/gptid/......., and by label (you have to label the partition with " gpart modify -l NAME da0p2"): /dev/gpt/NAME. There is also DISK-id, which come handy with FAT 16 etc.
It is important to understand that once you mount a device with one method, the other methods become unavailable for the same device (you cannot mount a partition by device name AND by label at the same time).
And this is the source of your problem: somehow the device got mounted by GPT uuid and you cannot mount it by device name anymore.
Sometime it can happen on boot time, depending if your system was configured to do so.

There are loader parameters that can disable one or more of the methods for addressing devices described above. For example:

Code:

# Disable gpt/gptid labels
kern.geom.label.gptid.enable=0
kern.geom.label.gpt.enable=0

I learned that from this book: https://www.amazon.com/dp/1642350095/ref=cm_sw_em_r_mt_dp_U_u1JLDbMEYWVE5

T-Daemon · Oct 3, 2019

Is there a particular reason you have installed the i386 platform instead of amd64? The Intel Core i3-8100 CPU you have is perfectly capabil running on amd64. Don't let yourself be deceived by the naming, all Intel Core i range of processors are supported by the amd64 platform. With i386 you are not taking advantage of the full potential of the CPU, and give away valuable resources (from your dmesg):

Code:

real memory  = 8589934592 (8192 MB)
avail memory = 2232438784 (2129 MB)

More on this topic:
FreeBSD FAQ, 4.1.3. Why does FreeBSD report less than 4 GB memory when installed on an i386™ machine?

I suggest you download a amd64 installer image, RELEASE 11.3 or 12.0, install the base system (with the external drives unplugged), update the base system, add your external device(s) after the installation is completed, install all other programs.

After you have installed the base system and rebooted run freebsd-update(8):
freebsd-update fetch
freebsd-update install

Plug in the external drive, don't use sade(8), use gpart(8), make sure you choose the right disk:

gpart show da0
gpart destroy -F da0
gpart create -s gpt da0
gpart add -t freebsd-ufs -l exdatafs -a 1M da0
Check the partition table:
gpart show -p da0
newfs -jU /dev/da0p1
mkdir /data
mount /dev/da0p1 /data

ls /data will show .snap .sujournal
Edit /etc/fstab accordingly, install packages.

ralphbsz · Oct 4, 2019

roccobaroccoSC said:
...
It is important to understand that once you mount a device with one method, the other methods become unavailable for the same device ...

Thank you for explaining this, again.

dalpets · Oct 4, 2019

T-Daemon said:
Is there a particular reason you have installed the i386 platform instead of amd64? The Intel Core i3-8100 CPU you have is perfectly capabil running on amd64. Don't let yourself be deceived by the naming, all Intel Core i range of processors are supported by the amd64 platform. With i386 you are not taking advantage of the full potential of the CPU, and give away valuable resources (from your dmesg):

Code:

real memory = 8589934592 (8192 MB) avail memory = 2232438784 (2129 MB)

More on this topic:
FreeBSD FAQ, 4.1.3. Why does FreeBSD report less than 4 GB memory when installed on an i386™ machine?

I suggest you download a amd64 installer image, RELEASE 11.3 or 12.0, install the base system (with the external drives unplugged), update the base system, add your external device(s) after the installation is completed, install all other programs.

After you have installed the base system and rebooted run freebsd-update(8):
freebsd-update fetch
freebsd-update install

Plug in the external drive, don't use sade(8), use gpart(8), make sure you choose the right disk:

gpart show da0
gpart destroy -F da0
gpart create -s gpt da0
gpart add -t freebsd-ufs -l exdatafs -a 1M da0
Check the partition table:
gpart show -p da0
newfs -jU /dev/da0p1
mkdir /data
mount /dev/da0p1 /data

ls /data will show .snap .sujournal
Edit /etc/fstab accordingly, install packages.

You are the man! Thank you very much for your time & help, it is very much appreciated.
The commands you gave me worked without a hitch, including the journalling, however, when I opened Kbackup to do a full system backup it warned me that "The file '/data/backup xxxx.tar cannot be opened for writing. Is this because tar is only meant to be accessible in linux. Also, when I open the data folder properties the permissions show access on all counts, but says I can't change them anyhow, because I am not the owner. I presume this means I would need to write a root command if I needed to change them. I have given dev/da0p1 /data mount privileges at root in /etc/fstab.
A bit more help would be appreciated on this problem.
Thank You.

T-Daemon · Oct 5, 2019

dalpets said:
when I opened Kbackup to do a full system backup it warned me that "The file '/data/backup xxxx.tar cannot be opened for writing

Execute as root chmod 777 /data to give read, write, execute permissons to the folder.

dalpets said:
I have given dev/da0p1 /data mount privileges at root in /etc/fstab.

Let us see. Please post /etc/fstab.

dalpets · Oct 5, 2019

T-Daemon said:
Execute as root chmod 777 /data to give read, write, execute permissons to the folder.

done.

Let us see. Please post /etc/fstab.

Code:

Device        Mountpoint      FStype  Options Dump    Pass#
/dev/ada0p2     /               ufs     rw      1       1
/dev/ada0p3     none            swap    sw      0       0
proc            /proc           procfs  rw      0       0
/dev/da0p1     /data            ufs     rw      2       2

I do wonder if my later manual addition (the last entry 2/2 above) is conflicting with your earlier mount /dev/da0p1 /data command in post (20).
Another thing that is worrying is that not at any time with this backup saga have I been able to see the external drive source directory at all. So, in luckybackup I get the message "You have declared a destination (/data) that is part of the source directory". I think if this can be solved the problem might be resolved. Why is the /data directory not showing up in relation to the external drive, but is appearing only in the boot drive directory?

T-Daemon · Oct 6, 2019

dalpets said:
I do wonder if my later manual addition (the last entry 2/2 above) is conflicting with your earlier mount /dev/da0p1 /data command in post (20).

That is not possible. The mount(8) command after the disk initialisation in post #20 has ended after it's execution and the mount did not survive a shutdown(8) or reboot(8). What makes /data persistend mount is the fstab entry, no other mount process is interfearing, unless you initiate one.

dalpets said:
Another thing that is worrying is that not at any time with this backup saga have I been able to see the external drive source directory at all.

Why is the /data directory not showing up in relation to the external drive, but is appearing only in the boot drive directory?

Can you be more specific, I don't understand what you mean.

dalpets said:
luckybackup I get the message "You have declared a destination (/data) that is part of the source directory".

luckybackup/rsync(1) syncronizes files between a source and a destination. You have chosen a source (probably / ) which includes the destination (/data). That is not possible. You may haven't noticed the continuation of the error message.

Code:

Do not forget to define a directory at the 'exclude'
groupbox that will contain the destination

There is a exclude option under "Advanced" options in "Task properties". Hit "modify" button for existing tasks.

Also you should backup only important data, not the whole system, like the /usr/home directory, or if you have made modifications to the systems configuration files, /etc, or installed programs configuration files, /usr/local/etc.

If the installed system is messed up, it is easier, faster to reinstall than restoring from a backup. To reinstall a complete base system takes only minutes.

UFS Why can't I mount volume for external local backup disk?

Administrator