similar to: vinum drive referenced / disklabel inconsistency

Well, colleagues, I'm stuck a bit. I tried many different ways to setup system with vinum root (the only reference I found yet besides old "bootstrapping vinum" article is Joerg's commit message: http://freebsd.rambler.ru/bsdmail/cvs-all_2003/msg01225.html I failed. I have 4-stable system set up at ad0, and tried to set up pair of drives for new system at ad2 and ad3 (actually,

I made an array out of 3 IBM 20 gigs and 3 Maxtor 20 gigs I used striping to make one big drive A couple of days ago I was copying a movie onto to it and the computer decided to reboot when it came back up I was greeted with this message Can someone please tell me if I can recover some how? or should I just rebuild the array? or is one of my disks physically bad? Detects all 7 drives (1 10gig

Dear colleagues, [I'm under 4-STABLE] What is the correct sequence to delete existing vinum module (for example, raid10) and do *not* use -f flags for vinum? in my case t is raid10 vovume: vinum -> l -r t V t State: up Plexes: 2 Size: 8191 MB P t.p0 S State: up Subdisks: 2 Size: 8191 MB P t.p1 S State:

Hi, I'm not sure this is supposed to happen (my computer rebooted halfway through adding an other drive to a volume): [long lines needed] (02:44:50 <~>) 0 $ sudo vinum ld D storage State: up Device /dev/ad0d Avail: 38166/381 66 MB (100%) D worthless State: up Device /dev/ad2d Avail: 38038/380 38 MB (100%) D barracuda

Dear colleagues, experimenting with vinum stripes and mirrors, I'd stuck myself with the following: panic: throw_rude_remark: called without config lock (from vinumconfig.c:throw_rude_remark:103) The system before this panic has two 160G drives with two vinum partitions on each (one for mirrored root and one for the rest with swap between); these were ad0 and ad2. For the experiments,

Hi All, I'm about to clean and re-initialize a Maxtor 160GB disk that shows a weird problem but I think I've found a bug in RELENG_4_7 somewhere so if preserving my disk can help conquer one more bug I'm happy to wait a couple of days and help solve that bug. Here's the story: While upgrading from 4.3-STABLE to 4.7p4 and at the same time reorganizing my vinum volumes I copied

Hi, I had a power failure, and the on-disk configuration for vinum went bizarre. The logs read from disks are at http://biaix.org/pk/debug/ (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead drive? Can I force vinum to use the other's drive configuration? What's the less traumatic

Hi, Somehow[TM] an installation of 4.11 to ad0s3 managed to wipe out my existing disklabel for 7.0 on ad0s4. I now need to recover the disklabel to get my system to boot! There were three labels - ad0s4a: UFS, exact size unknown. Is it possible to infer this from the UFS partition size? I can mount this already, as I simply wrote an 'a' label of maximum size to the disklabel - ad0s4b:

Hi all, I got a machine with 8GB of RAM and plenty of disk space. I need gvinum to manage big number of file systems but PAE enabled kernel does not compile modules. I couldn't figure out how to get vinum statically compiled in the kernel if that is the way to go. I am running 6-STABLE. Please advise on how to get PAE kernel and gvinum working together! TIA, Stoyan

Dear All, At some point after release of CentOS 7 (though this thing might have started before, it is just when _I_ noticed it) I discovered that if I stick into machine drive without disk label, and then do kickstart installation, the command in kickstart file clearpart --initlabel does not work. Even worse: if I just use GUI installer the drive is not listed between available disks. If I

I have a GPT formatted disk where I recently expanded the size of a partition. I used "gpart resize -i 6 ada1" first to expand the partition to use the remaining free space and then growfs to modify the FFS file system to use the full partition. This was all done in single-user mode, of course, but when I enter "exit" to bring the system up, it failed to mount /usr. This was

Hello. I'm having a 4.7Rp9 server which is since months quite unstable, so I've compiled a debug kernel and got a crash dump. I'm a programmer and I know a little how to use gdb, I'm not so expert about FreeBSD kernel insides however, so I can't get much from it. Any kind of help is appreciated. This is the crash message: IdlePTD at phsyical address 0x0032f000 initial pcb

Hello freebsd-stable, I have 5.5-PRERELEASE server in production, booting from ad0s1: # BLOCKSIZE=512 swapinfo Device 512-blocks Used Avail Capacity /dev/ad0s1b 2097152 52872 2044280 3% /dev/ad1s1b 2097152 51952 2045200 2% Total 4194304 104824 4089480 2% # bsdlabel ad0s1 | fgrep b: b: 2097152 0 swap

LGTM Another thing concerning the disklabel partitions is that list_filesystems() will print both /dev/sda1 and /dev/sda5 as ufs file systems. I don't know if you care to change this. The fact is that both are mountable. P.S. I wish the kernel folks would stop treating the disklabel partitions as logical partitions. Logical partitions are sequential, there are no gaps in the numbering. On

Hi everyone, I extracted this from the grub sourcecode: /* possible values for the *BSD-style partition type */ . . . #define FS_EXT2FS 17 /* Linux Extended 2 file system */ It would actually meet my partitioning requirements to register a partition inside one of my slices as ext2 (I currently mask the partition type as ISO9660(!) and use a *patched* grub, so you see this situation

Hi. I am looking for an IPv6 capable CVSUP mirror. I found a discussion from one year ago where it was stated that CVSUP was not IPv6-capable. Does anyone know if this has changed? Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam

I've just had a 4.9p1 system partially deadlock for about 30 minutes and then spontaneously(?) recover. The "ps" results point at vinum. I've never seen this before and don't recall anything like this being mentioned here before. At the time, I had two find's running in a large NFS mounted filesystem and was doing a "cvs -d /usr/ncvs -R checkout -P ports" from

Hello Everyone, I have a CentOS 6.3 host running a few KVMs. One of them is a CentOS 6.3 KVM that I want to use for making backups with BackupPC. What I'm having a problem with is assigning the KVM an external drive. I used to run BackupPC on an Ubuntu box. The backups went to an external eSATA 1.5TB, ext4 format, single partition drive (regular 3.5" in an enclosure). I want to now

On 06/30/16 14:19, Ady Ady via Syslinux wrote: > > BTW, any suggestions for an alternative name for this option, instead > of "dlabel"? > "disklabel" -hpa

Hi, My problem is I have a particular system which has Linux (LFS) and Windows XP on one drive and Windows 10 on a second drive. I use extlinux to boot my systems and all three systems boot as expected, however in use I have found unsatisfactory interactions between the Windows XP and the Windows 10 systems. My question is: Is it possible on booting one of the Windows systems to hide