Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No, it's not. I guess you can use ext4 even if the kernel is not of the 3.X.Y series. I may have been too pessimistic about ext4 stability (first introduced in kernel version 2.6.28)
No, it's not. I guess you can use ext4 even if the kernel is not of the 3.X.Y series. I may have been too pessimistic about ext4 stability (first introduced in kernel version 2.6.28)
Ok more errors lol
I tryed
Code:
mkfs.ext4 /dev/sda1
and got this
Code:
# mkfs.ext4 /dev/sda1
mke2fs 1.41.12 (17-May-2010)
/dev/sda1 is apparently in use by the system; will not make a filesystem here!
Is it mounted? Check it using the mount command.
If not, maybe you need to restart the system to get the partition table written to the disk.
got this back mate
Code:
/dev/sdc1 on / type ext3 (rw,grpquota,errors=remount-ro,usrquota)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
Then if you've chosen to write the new partitions to the devices with cfdisk, try rebooting the system before formatting.
hmm odd after rebooting I get this
Code:
root@debian:~# mkfs.ext4 /dev/sda1
mke2fs 1.41.12 (17-May-2010)
Could not stat /dev/sda1 --- No such file or directory
The device apparently does not exist; did you specify it correctly?
Then you need to install it via the package manager:
Code:
apt-get install parted
Once installed, retry.
Yay! looks like it worked this time
Code:
root@debian:~# mkfs.ext4 /dev/sda1
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
122101760 inodes, 488378000 blocks
24418900 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
14905 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
root@debian:~# mkfs.ext4 /dev/sdb1
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
122101760 inodes, 488378000 blocks
24418900 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
14905 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
root@debian:~#
While there's nothing preventing you to just mount them inside any empty folder you like, there are some conventions regarding Linux filesystem (you can find more info searching for Linux FHS) and one of these is to reserve /etc as a central place for configuration files.
If you'd like to adhere to current conventions, I suggest you create two new directories under /media or /mnt or at the root level (/).
Given that Linux filesystems are case sensitive, I suggest to use lowercase names without whitespaces in beetween, 'cause they're often a pain in the @## when found in a path name.
When you decided the location for these two new mounts, try mounting them as said in a previous post.
root@debian:~# mount
/dev/sdc1 on / type ext3 (rw,grpquota,errors=remount-ro,usrquota)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sda1 on /2tb_A type ext4 (rw)
/dev/sdb1 on /2tb_B type ext4 (rw)
Looks good to me
In order to write in those two new directories as a normal user, we need to change those directories permissions.
If you issue a
Code:
ls -l /2tb*
command, you should see that those directories are owned by root:root (4th and 5th column of the output). Let's change that to root:users with
Code:
chown -R root:users /2tb*
You should test the ability to write on those mount points as a normal user temporarily switching to the unprivileged user you use on that machine (I'll call it user) with
Code:
su user
touch /2tb_A/testA
touch /2tb_B/testB
exit
If no errors appeared (such as cannot write to XYZ: permission denied) then we're good to go with /etc/fstab.
I don't know if you're comfortable with a shell text editor such as nano/vi/vim/emacs etc. If so, you need to append these two lines to the /etc/fstab file:
If you're not comfortable with any shell text editors, you can append those lines via a echo command on the command line.
Just copy and paste these commands in your shell and it's all done. BIG FAT WARNING: make sure you use double > (>>) as it means "append to the file". If you mistakenly use a single > then you'll overwrite the /etc/fstab file losing all the information currently contained therein.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
