Other Problems with Drive Mounts

Alita · May 7, 2020

I was doing fine for a while now remember I am new to this so I am not as sharp for most of you to be.

Code:

camcontrol devlist

<HITACHI HUA723030ALA640 MKAONS01>  at scbus3 target 0 lun 0 (pass0,ada0)
<Hitachi HDS723030ALA640 MKAOA3B0>  at scbus4 target 0 lun 0 (pass1,ada1)
<TOSHIBA DT01ACA200 MX4OABB0>      at scbus5 target 0 lun 0 (pass2,ada2)
<Hitachi HUA722020ALA331 JKAOA3NH>  at scbus6 target 0 lun 0 (pass3,ada3)
<HITACHI HUA723030ALA640 MKAONS01>  at scbus7 target 0 lun 0 (pass4,ada4)
<Generic STORAGE DEVICE 9451>      at scbus8 target 0 lun 0 (da0,pass5)

Most of my drives I mount manually I was able to have working good eg:
ntfs-3g /dev/ada3p1 /media/X:
ntfs-3g /dev/ada1p1 /media/Y:

Where is W and X on my drives here?
I can not to find them for mounting

Those 2 drives X and Y are mounted but not Z and W Drive

But when I do
ntfs-3g /dev/ada4p2 /media/W: , it says to me, No such file or directory

ntfs-3g /dev/ada1s1 /media/Z:
I get

Code:

gpart show ada0
=>        63  4294967232  ada0  MBR  (2.7T)
          63        1985        - free -  (993K)
        2048  4294963200     1  ntfs  (2.0T)
  4294965248        2047        - free -  (1.0M)

Code:

Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
Options:  ro (read-only mount), windows_names, uid=, gid=,
          umask=, fmask=, dmask=
Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
Options:  ro (read-only mount), windows_names, uid=, gid=,
          umask=, fmask=, dmask=, streams_interface=.
          Please see the details in the manual (type: man ntfs-3g).
Example: ntfs-3g /dev/sda1 /mnt/windows
, streams_interface=.
          Please see the details in the manual (type: man ntfs-3g).
Example: ntfs-3g /dev/sda1 /mnt/windows

Code:

gpart show

=>        63  4294967232  ada0  MBR  (2.7T)
          63        1985        - free -  (993K)
        2048  4294963200     1  ntfs  (2.0T)
  4294965248        2047        - free -  (1.0M)

=>        63  4294967232  diskid/DISK-YXGDW2UK  MBR  (2.7T)
          63        1985                        - free -  (993K)
        2048  4294963200                     1  ntfs  (2.0T)
  4294965248        2047                        - free -  (1.0M)

=>        34  5860533101  ada1  GPT  (2.7T)
          34          94        - free -  (47K)
         128  5860533007     1  ms-basic-data  (2.7T)

=>        40  3907029088  ada2  GPT  (1.8T)
          40         512     1  freebsd-boot  (256K)
         552  3901784064     2  freebsd-ufs  (1.8T)
  3901784616     5234688     3  freebsd-swap  (2.5G)
  3907019304        9824        - free -  (4.8M)

=>        34  3907029101  ada3  GPT  (1.8T)
          34      264158        - free -  (129M)
      264192  3906764800     1  ms-basic-data  (1.8T)
  3907028992         143        - free -  (72K)

=>        34  5860533101  ada4  GPT  (2.7T)
          34      262144     1  ms-reserved  (128M)
      262178        2014        - free -  (1.0M)
      264192  5860268032     2  ms-basic-data  (2.7T)
  5860532224         911        - free -  (456K)

I only want to mount 4 drives I know one of them is MBR but also I have to keep changing the letter each boot up it does not remember how. Unless you can show me to put in /etc/fstab correctly to always boot the same drives.

ralphbsz · May 7, 2020

Alita said:
i only want to mount 4 Drives i know one of them is MBR but also i have to keep changing the letter each boot up it does not remember how. unless You can show me to put in /etc/fstab correctly to always boot the same drives

Classic problem. For GPT partitioned drives, you can give explicit names to the partitions, and then use those names in your mount commands or in your fstab. Let's see ... my log files say to use "gpart ... -l <name>" where ... is either add or modify. Then in your fstab, you can mount them with the device name being /dev/gpt/<name>. There are a lot more details in the handbook. Since you obviously did read the handbook before using FreeBSD (you did, right?), you'll easily be able to find the correct section (hint: a quick web search says: section 18.7). I know there are other ways to do it, for example glabel (which has interesting problems, it modifies the CONTENT of the partition, while gpart -l labels do not), and for FreeBSD UFS partition, you can also use tunefs.

Once you have labelled everything that can be labeled, there is still the problem of the one MBR disk that has a file system that can't be labelled. That's just going to be a pain. Any way you can move the data to have a GPT label? Failing that, you may have to write a script that finds that disk by exclusion, which is going to be painful.

Alita · May 7, 2020

ralphbsz said:
Classic problem. For GPT partitioned drives, you can give explicit names to the partitions, and then use those names in your mount commands or in your fstab. Let's see ... my log files say to use "gpart ... -l <name>" where ... is either add or modify. Then in your fstab, you can mount them with the device name being /dev/gpt/<name>. There are a lot more details in the handbook. Since you obviously did read the handbook before using FreeBSD (you did, right?), you'll easily be able to find the correct section (hint: a quick web search says: section 18.7). I know there are other ways to do it, for example glabel (which has interesting problems, it modifies the CONTENT of the partition, while gpart -l labels do not), and for FreeBSD UFS partition, you can also use tunefs.

maybe i read just a little in the handbook, but that was for small things such as file editing . i was hoping that freeBSD would keep me smiling ad not i do not know what to do, was there an earlier version that was more stable then this or GhostBSD or even Trueos ?

i would use openBSD if i know for sure it will work with all of my needs

Once you have labelled everything that can be labeled, there is still the problem of the one MBR disk that has a file system that can't be labelled. That's just going to be a pain. Any way you can move the data to have a GPT label? Failing that, you may have to write a script that finds that disk by exclusion, which is going to be painful.

i am not to sure as i had lost 2 drives already and have to restore the backups
i do know earlier today i had 3 drives mounted the 3rd one was the MBR

Alita · May 7, 2020

ralphbsz said:
Classic problem. For GPT partitioned drives, you can give explicit names to the partitions, and then use those names in your mount commands or in your fstab. Let's see ... my log files say to use "gpart ... -l <name>" where ... is either add or modify. Then in your fstab, you can mount them with the device name being /dev/gpt/<name>. There are a lot more details in the handbook. Since you obviously did read the handbook before using FreeBSD (you did, right?), you'll easily be able to find the correct section (hint: a quick web search says: section 18.7). I know there are other ways to do it, for example glabel (which has interesting problems, it modifies the CONTENT of the partition, while gpart -l labels do not), and for FreeBSD UFS partition, you can also use tunefs.

Once you have labelled everything that can be labeled, there is still the problem of the one MBR disk that has a file system that can't be labelled. That's just going to be a pain. Any way you can move the data to have a GPT label? Failing that, you may have to write a script that finds that disk by exclusion, which is going to be painful.

well as far as the location not found i rm Z: then recreated Z:
and all drives show up now

Now to find out how i can store these in the /fstab file wit no errors

Thank You