FreeBSD can't mount fdesc?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















I recently had a bad UPS lead to a sudden crash of several machines. One of them (running FreeBSD) didn't come back up until I replaced the power supply, but it's still not fully back. Both the BIOS and the OS complain about a disk being missing; swapping around power cables and data cables and such has convinced me that the problem is the disk itself. FreeBSD won't fully start up due to a problem mounting something from /etc/fstab:



Mounting local file systems: mount: /fdesc: No such file or directory


If I comment out the fdesc line in fstab, everything seems to come up OK. But... that can't be good, can it? I don't know anything about fdesc besides what I've read in the past few minutes, but it seems like a low-level thing dealing with stuff like stdin and stdout, which seem important to me.



There does exist /dev/fd, which does contain /dev/fd/0, /dev/fd/1, and /dev/fd/2, and brief piping experiments at the command line seem to indicate that stdin, stdout, and stderr are all working OK.



What might be the cause of it being unable to mount /fdesc? And what horrible things will happen if I just continue to run without mounting it? How might I be able to get /fdesc back?



The contents of /etc/fstab, after I commented out the fdesc line:



#Device Mountpoint FSType Options Dump Pass#
/dev/ada0p2 / ufs rw 1 1
/dev/ada0p3 none swap sw 0 0
#/dev/fd fdesc fdesc rw 0 0


Plus a couple Samba mounts which seem to be working fine.










share|improve this question






















  • It's only needed for things like bash, which need the full /dev/fd behavior to do process substitution. Which release of FreeBSD is this? On 10.0, the fstype is fdescfs and the mount point is /dev/fd. I can check older releases for you.

    – Mark Plotnick
    Feb 24 '15 at 17:30












  • Thanks. It's 10.0-RELEASE. After reading your comment, I tried bash, and piping with stdin, stdout, and stderr seem to work OK there too? And there is a /dev/fd. Not sure what you mean by "to do process substitution"? Thanks again.

    – Bob Vesterman
    Feb 24 '15 at 17:43











  • There's always a /dev/fd/0, 1, and 2 - the filesystem mounted at /dev handles them. But if you run join -t: <(sort /etc/passwd) <(sort /etc/group) in bash, you'll get an error join: /dev/fd/63: No such file or directory. But if you run mount -t fdescfs fdescfs /dev/fd, then that join command will work.

    – Mark Plotnick
    Feb 24 '15 at 17:52












  • Thanks - exactly what you describe happens with the join. But this leads me to wonder why fdesc can't be mounted from fstab, given that I can mount it from the command line.

    – Bob Vesterman
    Feb 24 '15 at 18:26











  • I think the proper fstab line is fdescfs /dev/fd fdescfs rw 0 0. It's a mystery to me how your existing fstab line once did work.

    – Mark Plotnick
    Feb 24 '15 at 18:32
















1















I recently had a bad UPS lead to a sudden crash of several machines. One of them (running FreeBSD) didn't come back up until I replaced the power supply, but it's still not fully back. Both the BIOS and the OS complain about a disk being missing; swapping around power cables and data cables and such has convinced me that the problem is the disk itself. FreeBSD won't fully start up due to a problem mounting something from /etc/fstab:



Mounting local file systems: mount: /fdesc: No such file or directory


If I comment out the fdesc line in fstab, everything seems to come up OK. But... that can't be good, can it? I don't know anything about fdesc besides what I've read in the past few minutes, but it seems like a low-level thing dealing with stuff like stdin and stdout, which seem important to me.



There does exist /dev/fd, which does contain /dev/fd/0, /dev/fd/1, and /dev/fd/2, and brief piping experiments at the command line seem to indicate that stdin, stdout, and stderr are all working OK.



What might be the cause of it being unable to mount /fdesc? And what horrible things will happen if I just continue to run without mounting it? How might I be able to get /fdesc back?



The contents of /etc/fstab, after I commented out the fdesc line:



#Device Mountpoint FSType Options Dump Pass#
/dev/ada0p2 / ufs rw 1 1
/dev/ada0p3 none swap sw 0 0
#/dev/fd fdesc fdesc rw 0 0


Plus a couple Samba mounts which seem to be working fine.










share|improve this question






















  • It's only needed for things like bash, which need the full /dev/fd behavior to do process substitution. Which release of FreeBSD is this? On 10.0, the fstype is fdescfs and the mount point is /dev/fd. I can check older releases for you.

    – Mark Plotnick
    Feb 24 '15 at 17:30












  • Thanks. It's 10.0-RELEASE. After reading your comment, I tried bash, and piping with stdin, stdout, and stderr seem to work OK there too? And there is a /dev/fd. Not sure what you mean by "to do process substitution"? Thanks again.

    – Bob Vesterman
    Feb 24 '15 at 17:43











  • There's always a /dev/fd/0, 1, and 2 - the filesystem mounted at /dev handles them. But if you run join -t: <(sort /etc/passwd) <(sort /etc/group) in bash, you'll get an error join: /dev/fd/63: No such file or directory. But if you run mount -t fdescfs fdescfs /dev/fd, then that join command will work.

    – Mark Plotnick
    Feb 24 '15 at 17:52












  • Thanks - exactly what you describe happens with the join. But this leads me to wonder why fdesc can't be mounted from fstab, given that I can mount it from the command line.

    – Bob Vesterman
    Feb 24 '15 at 18:26











  • I think the proper fstab line is fdescfs /dev/fd fdescfs rw 0 0. It's a mystery to me how your existing fstab line once did work.

    – Mark Plotnick
    Feb 24 '15 at 18:32














1












1








1








I recently had a bad UPS lead to a sudden crash of several machines. One of them (running FreeBSD) didn't come back up until I replaced the power supply, but it's still not fully back. Both the BIOS and the OS complain about a disk being missing; swapping around power cables and data cables and such has convinced me that the problem is the disk itself. FreeBSD won't fully start up due to a problem mounting something from /etc/fstab:



Mounting local file systems: mount: /fdesc: No such file or directory


If I comment out the fdesc line in fstab, everything seems to come up OK. But... that can't be good, can it? I don't know anything about fdesc besides what I've read in the past few minutes, but it seems like a low-level thing dealing with stuff like stdin and stdout, which seem important to me.



There does exist /dev/fd, which does contain /dev/fd/0, /dev/fd/1, and /dev/fd/2, and brief piping experiments at the command line seem to indicate that stdin, stdout, and stderr are all working OK.



What might be the cause of it being unable to mount /fdesc? And what horrible things will happen if I just continue to run without mounting it? How might I be able to get /fdesc back?



The contents of /etc/fstab, after I commented out the fdesc line:



#Device Mountpoint FSType Options Dump Pass#
/dev/ada0p2 / ufs rw 1 1
/dev/ada0p3 none swap sw 0 0
#/dev/fd fdesc fdesc rw 0 0


Plus a couple Samba mounts which seem to be working fine.










share|improve this question














I recently had a bad UPS lead to a sudden crash of several machines. One of them (running FreeBSD) didn't come back up until I replaced the power supply, but it's still not fully back. Both the BIOS and the OS complain about a disk being missing; swapping around power cables and data cables and such has convinced me that the problem is the disk itself. FreeBSD won't fully start up due to a problem mounting something from /etc/fstab:



Mounting local file systems: mount: /fdesc: No such file or directory


If I comment out the fdesc line in fstab, everything seems to come up OK. But... that can't be good, can it? I don't know anything about fdesc besides what I've read in the past few minutes, but it seems like a low-level thing dealing with stuff like stdin and stdout, which seem important to me.



There does exist /dev/fd, which does contain /dev/fd/0, /dev/fd/1, and /dev/fd/2, and brief piping experiments at the command line seem to indicate that stdin, stdout, and stderr are all working OK.



What might be the cause of it being unable to mount /fdesc? And what horrible things will happen if I just continue to run without mounting it? How might I be able to get /fdesc back?



The contents of /etc/fstab, after I commented out the fdesc line:



#Device Mountpoint FSType Options Dump Pass#
/dev/ada0p2 / ufs rw 1 1
/dev/ada0p3 none swap sw 0 0
#/dev/fd fdesc fdesc rw 0 0


Plus a couple Samba mounts which seem to be working fine.







mount freebsd fstab






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 24 '15 at 17:07









Bob VestermanBob Vesterman

15810




15810












  • It's only needed for things like bash, which need the full /dev/fd behavior to do process substitution. Which release of FreeBSD is this? On 10.0, the fstype is fdescfs and the mount point is /dev/fd. I can check older releases for you.

    – Mark Plotnick
    Feb 24 '15 at 17:30












  • Thanks. It's 10.0-RELEASE. After reading your comment, I tried bash, and piping with stdin, stdout, and stderr seem to work OK there too? And there is a /dev/fd. Not sure what you mean by "to do process substitution"? Thanks again.

    – Bob Vesterman
    Feb 24 '15 at 17:43











  • There's always a /dev/fd/0, 1, and 2 - the filesystem mounted at /dev handles them. But if you run join -t: <(sort /etc/passwd) <(sort /etc/group) in bash, you'll get an error join: /dev/fd/63: No such file or directory. But if you run mount -t fdescfs fdescfs /dev/fd, then that join command will work.

    – Mark Plotnick
    Feb 24 '15 at 17:52












  • Thanks - exactly what you describe happens with the join. But this leads me to wonder why fdesc can't be mounted from fstab, given that I can mount it from the command line.

    – Bob Vesterman
    Feb 24 '15 at 18:26











  • I think the proper fstab line is fdescfs /dev/fd fdescfs rw 0 0. It's a mystery to me how your existing fstab line once did work.

    – Mark Plotnick
    Feb 24 '15 at 18:32


















  • It's only needed for things like bash, which need the full /dev/fd behavior to do process substitution. Which release of FreeBSD is this? On 10.0, the fstype is fdescfs and the mount point is /dev/fd. I can check older releases for you.

    – Mark Plotnick
    Feb 24 '15 at 17:30












  • Thanks. It's 10.0-RELEASE. After reading your comment, I tried bash, and piping with stdin, stdout, and stderr seem to work OK there too? And there is a /dev/fd. Not sure what you mean by "to do process substitution"? Thanks again.

    – Bob Vesterman
    Feb 24 '15 at 17:43











  • There's always a /dev/fd/0, 1, and 2 - the filesystem mounted at /dev handles them. But if you run join -t: <(sort /etc/passwd) <(sort /etc/group) in bash, you'll get an error join: /dev/fd/63: No such file or directory. But if you run mount -t fdescfs fdescfs /dev/fd, then that join command will work.

    – Mark Plotnick
    Feb 24 '15 at 17:52












  • Thanks - exactly what you describe happens with the join. But this leads me to wonder why fdesc can't be mounted from fstab, given that I can mount it from the command line.

    – Bob Vesterman
    Feb 24 '15 at 18:26











  • I think the proper fstab line is fdescfs /dev/fd fdescfs rw 0 0. It's a mystery to me how your existing fstab line once did work.

    – Mark Plotnick
    Feb 24 '15 at 18:32

















It's only needed for things like bash, which need the full /dev/fd behavior to do process substitution. Which release of FreeBSD is this? On 10.0, the fstype is fdescfs and the mount point is /dev/fd. I can check older releases for you.

– Mark Plotnick
Feb 24 '15 at 17:30






It's only needed for things like bash, which need the full /dev/fd behavior to do process substitution. Which release of FreeBSD is this? On 10.0, the fstype is fdescfs and the mount point is /dev/fd. I can check older releases for you.

– Mark Plotnick
Feb 24 '15 at 17:30














Thanks. It's 10.0-RELEASE. After reading your comment, I tried bash, and piping with stdin, stdout, and stderr seem to work OK there too? And there is a /dev/fd. Not sure what you mean by "to do process substitution"? Thanks again.

– Bob Vesterman
Feb 24 '15 at 17:43





Thanks. It's 10.0-RELEASE. After reading your comment, I tried bash, and piping with stdin, stdout, and stderr seem to work OK there too? And there is a /dev/fd. Not sure what you mean by "to do process substitution"? Thanks again.

– Bob Vesterman
Feb 24 '15 at 17:43













There's always a /dev/fd/0, 1, and 2 - the filesystem mounted at /dev handles them. But if you run join -t: <(sort /etc/passwd) <(sort /etc/group) in bash, you'll get an error join: /dev/fd/63: No such file or directory. But if you run mount -t fdescfs fdescfs /dev/fd, then that join command will work.

– Mark Plotnick
Feb 24 '15 at 17:52






There's always a /dev/fd/0, 1, and 2 - the filesystem mounted at /dev handles them. But if you run join -t: <(sort /etc/passwd) <(sort /etc/group) in bash, you'll get an error join: /dev/fd/63: No such file or directory. But if you run mount -t fdescfs fdescfs /dev/fd, then that join command will work.

– Mark Plotnick
Feb 24 '15 at 17:52














Thanks - exactly what you describe happens with the join. But this leads me to wonder why fdesc can't be mounted from fstab, given that I can mount it from the command line.

– Bob Vesterman
Feb 24 '15 at 18:26





Thanks - exactly what you describe happens with the join. But this leads me to wonder why fdesc can't be mounted from fstab, given that I can mount it from the command line.

– Bob Vesterman
Feb 24 '15 at 18:26













I think the proper fstab line is fdescfs /dev/fd fdescfs rw 0 0. It's a mystery to me how your existing fstab line once did work.

– Mark Plotnick
Feb 24 '15 at 18:32






I think the proper fstab line is fdescfs /dev/fd fdescfs rw 0 0. It's a mystery to me how your existing fstab line once did work.

– Mark Plotnick
Feb 24 '15 at 18:32











1 Answer
1






active

oldest

votes


















1














Your fdesc line in fstab appears be mislocated, it should be




fdesc /dev/fd fdescfs rw 0 0




As the first comment noted, the first colum is device name, which is ignored by fdescfs(5), then the mount point, which should be /dev/fd to make it useful.
Also the file system type is fdescfs, not fdesc



See the man page fdescfs(5) for more information.






share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f186634%2ffreebsd-cant-mount-fdesc%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Your fdesc line in fstab appears be mislocated, it should be




    fdesc /dev/fd fdescfs rw 0 0




    As the first comment noted, the first colum is device name, which is ignored by fdescfs(5), then the mount point, which should be /dev/fd to make it useful.
    Also the file system type is fdescfs, not fdesc



    See the man page fdescfs(5) for more information.






    share|improve this answer



























      1














      Your fdesc line in fstab appears be mislocated, it should be




      fdesc /dev/fd fdescfs rw 0 0




      As the first comment noted, the first colum is device name, which is ignored by fdescfs(5), then the mount point, which should be /dev/fd to make it useful.
      Also the file system type is fdescfs, not fdesc



      See the man page fdescfs(5) for more information.






      share|improve this answer

























        1












        1








        1







        Your fdesc line in fstab appears be mislocated, it should be




        fdesc /dev/fd fdescfs rw 0 0




        As the first comment noted, the first colum is device name, which is ignored by fdescfs(5), then the mount point, which should be /dev/fd to make it useful.
        Also the file system type is fdescfs, not fdesc



        See the man page fdescfs(5) for more information.






        share|improve this answer













        Your fdesc line in fstab appears be mislocated, it should be




        fdesc /dev/fd fdescfs rw 0 0




        As the first comment noted, the first colum is device name, which is ignored by fdescfs(5), then the mount point, which should be /dev/fd to make it useful.
        Also the file system type is fdescfs, not fdesc



        See the man page fdescfs(5) for more information.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 4 at 10:13









        Low powerLow power

        714




        714



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f186634%2ffreebsd-cant-mount-fdesc%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown






            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?