01-18-2019
You don't need to wait for it to finish syncing, no.
The device changing number may have been due to a reboot, i.e. one boot was a device you made, the next reboot was auto-assembled and the device number chosen automatically.
By running mkfs on it again you wiped out whatever was on it before.
8 More Discussions You Might Find Interesting
1. Solaris
Hi,
I set up a RAID 5 configuration and for some reason the volumes won't mount when the system boots. I have to manually mount them from the command line and all is fine.
Here's the vfstab entries:
#device device mount FS fsck mount mount
#to mount ... (2 Replies)
Discussion started by: rpollard001
2 Replies
2. UNIX for Advanced & Expert Users
Hello All,
(RHEL4)
Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array.
I somehow managed to up the system with working raid1 array.
But the main problem persisted..
i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies
3. UNIX for Dummies Questions & Answers
Hi.
I'm trying to copy multiple folders from the remote machine to the local machine. I wrote a batch file to run an ftp window.
The problem I am having is that the only command to copy files is mget *, and this copies only files, not folders.
For example, ftp ts555
cd ts555/test
' test... (5 Replies)
Discussion started by: leenyburger
5 Replies
4. UNIX for Dummies Questions & Answers
Hi
Can someone tell me what are the differences between software and hardware raid ?
thx for help. (2 Replies)
Discussion started by: presul
2 Replies
5. Linux
hello
my centOS newly installed system loading dmraid modules on startup
I did remove all LVM/raid things from system installation menus and after installation too but dmraid is still there
and he says: no raid disks found
also I did modprobe -r dm_raid45 and it do remove it but only until... (7 Replies)
Discussion started by: tip78
7 Replies
6. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
7. Solaris
Server Model: T5120 with 146G x4 disks.
OS: Solaris 10 - installed on c1t0d0.
Plan to use software raid (veritas volume mgr) on c1t2d0 disk.
After format and label the disk, still not able to detect using vxdiskadm.
Question:
Should I remove the hardware raid on c1t2d0 first?
My... (4 Replies)
Discussion started by: KhawHL
4 Replies
8. Red Hat
Hello,
I want to delete a RAID configuration an old server has.
Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton?
I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies
LEARN ABOUT REDHAT
mkfs.minix
MKFS.MINIX(8) System Administration MKFS.MINIX(8)
NAME
mkfs.minix - make a Minix filesystem
SYNOPSIS
mkfs.minix [options] device [size-in-blocks]
DESCRIPTION
mkfs.minix creates a Linux MINIX filesystem on a device (usually a disk partition).
The device is usually of the following form:
/dev/hda[1-8] (IDE disk 1)
/dev/hdb[1-8] (IDE disk 2)
/dev/sda[1-8] (SCSI disk 1)
/dev/sdb[1-8] (SCSI disk 2)
The device may be a block device or a image file of one, but this is not enforced. Expect not much fun on a character device :-).
The size-in-blocks parameter is the desired size of the file system, in blocks. It is present only for backwards compatibility. If omit-
ted the size will be determined automatically. Only block counts strictly greater than 10 and strictly less than 65536 are allowed.
OPTIONS
-c, --check
Check the device for bad blocks before creating the filesystem. If any are found, the count is printed.
-n, --namelength length
Specify the maximum length of filenames. Currently, the only allowable values are 14 and 30 for file system versions 1 and 2. Ver-
sion 3 allows only value 60. The default is 30.
-i, --inodes number
Specify the number of inodes for the filesystem.
-l, --badblocks filename
Read the list of bad blocks from filename. The file has one bad-block number per line. The count of bad blocks read is printed.
-1 Make a Minix version 1 filesystem. This is the default.
-2, -v Make a Minix version 2 filesystem.
-3 Make a Minix version 3 filesystem.
-V, --version
Display version information and exit. The long option cannot be combined with other options.
-h, --help
Display help text and exit.
EXIT CODES
The exit code returned by mkfs.minix is one of the following:
0 No errors
8 Operational error
16 Usage or syntax error
SEE ALSO
fsck(8), mkfs(8), reboot(8)
AVAILABILITY
The mkfs.minix command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.
util-linux June 2015 MKFS.MINIX(8)