Re: [SOLVED] Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-18 Thread Julien Gabel
>>> do you have your securelevel set in rc.conf to YES and to a higher >>> level (like 3)? >> Yes, this machine had a securevel positionned: it set to '2'. But >> because I can't touch the disk even in Single User Mode, I don't >> think it is related, but... >> >> What is your idea? > Ok. I had

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-13 Thread Julien Gabel
GEOM doesn't let you write to an active device, except if you set kern.geom.debugflags=16 >>> Ok no problem, I changed it this way: >>> # sysctl kern.geom.debugflags=16 >>> kern.geom.debugflags: 1 -> 16 >>> But it seems to change *absolutly nothing*... :( [...] >> Mmmhh... We're doin

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-11 Thread Joan Picanyol i Puig
On Sun, 11 Apr 2004 15:15:18 +0200, Julien Gabel wrote: GEOM doesn't let you write to an active device, except if you set kern.geom.debugflags=16 > >>> Ok no problem, I changed it this way: >>> # sysctl kern.geom.debugflags=16 >>> kern.geom.debugflags: 1 -> 16 >>> But it seems to chan

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-11 Thread Julien Gabel
>>> GEOM doesn't let you write to an active device, except if you set >>> kern.geom.debugflags=16 >> Ok no problem, I changed it this way: >> # sysctl kern.geom.debugflags=16 >> kern.geom.debugflags: 1 -> 16 >> But it seems to change *absolutly nothing*... :( > Mmmhh... We're doing something wr

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-11 Thread Joan Picanyol i Puig
On Sun, 11 Apr 2004 10:31:22 +0200, Julien Gabel wrote: >> GEOM doesn't let you write to an active device, except if you set >> kern.geom.debugflags=16 > > Ok no problem, I changed it this way : > # sysctl kern.geom.debugflags=16 > kern.geom.debugflags: 1 -> 16 > > But it seems to change *abso

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-11 Thread Julien Gabel
>>> do you have your securelevel set in rc.conf to YES and to a higher >>> level (like 3)? >> Yes, this machine had a securevel positionned: it set to '2'. But >> because I can't touch the disk even in Single User Mode, I don't >> think it is related, but... >> >> What is your idea? > Ok. I had

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-11 Thread Chad Leigh -- Shire.Net LLC
On Apr 11, 2004, at 1:50 AM, Julien Gabel wrote: do you have your securelevel set in rc.conf to YES and to a higher level (like 3)? Yes, this machine had a securevel positionned: it set to '2'. But because I can't touch the disk even in Single User Mode, I don't think it is related, but... What i

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-11 Thread Julien Gabel
> do you have your securelevel set in rc.conf to YES and to a higher > level (like 3)? Yes, this machine had a securevel positionned: it set to '2'. But because I can't touch the disk even in Single User Mode, I don't think it is related, but... What is your idea? -- -jpeg. _

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-11 Thread Chad Leigh -- Shire.Net LLC
do you have your securelevel set in rc.conf to YES and to a higher level (like 3)? Chad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-11 Thread Julien Gabel
>> I want to say that it is a mirror created with a hardware HighPoint >> HPT374 (channel 2+3) UDMA133 controller ; not created using software, >> like vinum for example. - But when I tried to create a slice on it, I get: # fdisk -BI ad10 *** Working on device /dev/ad10

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-11 Thread Julien Gabel
> GEOM doesn't let you write to an active device, except if you set > kern.geom.debugflags=16 Ok no problem, I changed it this way : # sysctl kern.geom.debugflags=16 kern.geom.debugflags: 1 -> 16 But it seems to change *absolutly nothing*... :( >> # mount >> /dev/ar0s1a on / (ufs, local) >>

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-10 Thread Malcolm Kay
On Sunday 11 April 2004 07:15, Julien Gabel wrote: > I want to say that it is a mirror created with a hardware HighPoint HPT374 > (channel 2+3) UDMA133 controller ; not created using software, like vinum > for example. > > >> - But when I tried to create a slice on it, I get: > >> # fdisk -BI ad

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-10 Thread Joan Picanyol i Puig
On Sun, 11 Apr 2004 00:45:14 +0200, Julien Gabel wrote: >> GEOM doesn't let you touch the disk if some partition is mounted off it. >> Try setting kern.geom.debugflags to 1 I suck. This should have said: GEOM doesn't let you write to an active device, except if you set kern.geom.debugflags=16 >

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-10 Thread Julien Gabel
>> Here is my problem. I had a hard disk for one year now, working together >> with an other identical disk in a _hard_ mirror. > What's a '_hard_ mirror'? How did you set it up? I want to say that it is a mirror created with a hardware HighPoint HPT374 (channel 2+3) UDMA133 controller ; not crea

Re: Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-10 Thread Joan Picanyol i Puig
On Sat, 10 Apr 2004 15:22:16 +0200, Julien Gabel wrote: > Hello, > > Here is my problem. I had a hard disk for one year now, working together > with an other identical disk in a _hard_ mirror. What's a '_hard_ mirror'? How did you set it up? > - But when I tried to create a slice on it, I get: >

Can't *write* to a hard disk, not even a slice using fdisk(8).

2004-04-10 Thread Julien Gabel
Hello, Here is my problem. I had a hard disk for one year now, working together with an other identical disk in a _hard_ mirror. One month ago, I noticed the mirror was not active, found that the second part of the mirror was not responding and decided to recreate completely the mirror after makin