This article explains the steps to be taken when we face error when running fsck command

When we run "fsck" command using any non-root user, then we see the below error:

{master:0}

labroot@EX4600> start shell

labroot@EX4600:0% fsck

Can't open /dev/ad0s1a: Permission denied

Can't open /dev/ad2s1e: Permission denied

Can't open /dev/ad1s1f: Permission denied

Can't open /dev/ad1s1d: Permission denied

Can't open /dev/ad1s1a: Permission denied

Can't open /dev/ad1s1e: Permission denied

fsck: exec fsck_msdos for /dev/ad3s2: No such file or directory

We will be able to run the command using root user:

{master:0}

labroot@EX4600> start shell user root

Password:

labroot@EX4600:0% fsck

** /dev/ad0s1a (NO WRITE)

** Last Mounted on /

** Root file system

** Phase 1 - Check Blocks and Sizes

** Phase 2 - Check Pathnames

** Phase 3 - Check Connectivity

** Phase 4 - Check Reference Counts

** Phase 5 - Check Cyl groups

5366 files, 711296 used, 142059 free (7 frags, 35513 blocks, 0.0% fragmentation)

** /dev/ad2s1e (NO WRITE)

** Last Mounted on /config

** Phase 1 - Check Blocks and Sizes

** Phase 2 - Check Pathnames

** Phase 3 - Check Connectivity

** Phase 4 - Check Reference Counts

** Phase 5 - Check Cyl groups

117 files, 123 used, 257768 free (32 frags, 32217 blocks, 0.0% fragmentation)

** /dev/ad1s1f (NO WRITE)

** Last Mounted on /var

** Phase 1 - Check Blocks and Sizes

** Phase 2 - Check Pathnames

** Phase 3 - Check Connectivity

** Phase 4 - Check Reference Counts

** Phase 5 - Check Cyl groups

513 files, 43841 used, 203804 free (172 frags, 25454 blocks, 0.1% fragmentation)

** /dev/ad1s1d (NO WRITE)

** Last Mounted on /var/tmp

** Phase 1 - Check Blocks and Sizes

** Phase 2 - Check Pathnames

** Phase 3 - Check Connectivity

** Phase 4 - Check Reference Counts

** Phase 5 - Check Cyl groups

13 files, 10 used, 1011208 free (48 frags, 126395 blocks, 0.0% fragmentation)

FSCK command can only be run using the root user. Any other super-user class also gives the permission denied error.