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 FREEBSD
reboot
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system
SYNOPSIS
halt [-lnpq] [-k kernel]
reboot [-dlnpq] [-k kernel]
fasthalt [-lnpq] [-k kernel]
fastboot [-dlnpq] [-k kernel]
DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database.
The options are as follows:
-d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump
device has previously been specified with dumpon(8).
-k kernel
Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive
boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is
interrupted and a valid kernel booted. This may change in the future.
-l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot
or halt and log this themselves.
-n The file system cache is not flushed. This option should probably not be used.
-p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on
whether halt or reboot was called.
-q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
option is not specified). This option should probably not be used.
The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom and cleanly terminating specific programs.
SEE ALSO
getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8)
HISTORY
A reboot utility appeared in Version 6 AT&T UNIX.
BSD
October 11, 2010 BSD