Hi! Sorry for the late reply - I have been busy at work and this had to wait.
The system has been powered off since my last post.
The computer is new - built it to use as file server at home. I have not seen
any strange behaviour (other than this). All parts are brand new (except for
the
On Jun 12, 2010, at 3:45 AM, Jan Hellevik wrote:
Hi! Sorry for the late reply - I have been busy at work and this had to wait.
The system has been powered off since my last post.
The computer is new - built it to use as file server at home. I have not seen
any strange behaviour (other
Thanks for the reply. The thread on FreeBSD mentions creating symlinks for the
fdisk partitions. So did you earlier in this thread. I tried that but it did
not help - you can see the result in my earlier reply to your previous message
in this thread.
Is this the way to go? Should I try again
On Jun 12, 2010, at 12:43 PM, Jan Hellevik wrote:
Thanks for the reply. The thread on FreeBSD mentions creating symlinks for
the fdisk partitions. So did you earlier in this thread. I tried that but it
did not help - you can see the result in my earlier reply to your previous
message in
I am making a second backup of my other pool - then I'll use those disks and
recreate the problem pool. The only difference will be the SSD - only have one
of those. I'll use a disk in the same slot, so it will be close.
Backup will be finished in 2 hours time
--
This message posted from
Ok - this is really strange. I did a test. Wiped my second pool (4 disks like
the other pool), and used them to create a pool similar to the one I have
problems with.
Then i powered off, moved the disks and powered on. Same error message as
before. Moved the disks back to the original
I don't really have an explanation. Perhaps flaky second controller
hardware that only works sometimes and can corrupt pools? Have you seen
any other strangeness/instability on this computer?
Did you use zpool export before moving the disks the first time to the
second controller, or did
Thanks for the help, but I cannot get it to work.
j...@opensolaris:~# zpool import
pool: vault
id: 8738898173956136656
state: UNAVAIL
status: One or more devices are missing from the system.
action: The pool cannot be imported. Attach the missing
devices and try again.
see:
I cannot import - that is the problem. :-(
I have read the discussions you referred to (and quite a few more), and also
about the logfix program. I also found a discussion where 'zpool import -FX'
solved a similar problem so I tried that but no luck.
Now I have read so many discussions and
I don't think that is the problem (but I am not sure). It seems like te problem
is that the ZIL is missing. It is there, but not recognized.
I used fdisk to create a 4GB partition of a SSD, and then added it to the pool
with the command 'zpool add vault log /dev/dsk/c10d0p1'.
When I try to
- Jan Hellevik opensola...@janhellevik.com skrev:
I don't think that is the problem (but I am not sure). It seems like
te problem is that the ZIL is missing. It is there, but not
recognized.
I used fdisk to create a 4GB partition of a SSD, and then added it to
the pool with the command
svn_133 and zfs 22. At least my rpool is 22.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On May 15, 2010, at 2:53 AM, Jan Hellevik wrote:
I don't think that is the problem (but I am not sure). It seems like te
problem is that the ZIL is missing. It is there, but not recognized.
I used fdisk to create a 4GB partition of a SSD, and then added it to the
pool with the command
Thanks! Not home right now, but I will try that as soon as I get home.
Message was edited by: janh
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
- Richard Elling richard.ell...@gmail.com skrev:
On May 15, 2010, at 2:53 AM, Jan Hellevik wrote:
I don't think that is the problem (but I am not sure). It seems like
te problem is that the ZIL is missing. It is there, but not
recognized.
I used fdisk to create a 4GB partition of
It did not work. I did not find labels on p1, but on p0.
j...@opensolaris:~# zdb -l /dev/dsk/c10d0p1
LABEL 0
failed to unpack label 0
LABEL 1
Can you recreate the problem with a second pool on a second set of
drives, like I described in my earlier post? Right now it seems like
your problem is mostly due to the missing log device. I'm wondering if
that missing log device is what messed up the initial move to the other
controller,
Yes, I can try to do that. I do not have any more of this brand of disk, but I
guess that does not matter. It will have to wait until tomorrow (I have an
appointment in a few minutes, and it is getting late here in Norway), but I
will try first thing tomorrow. I guess a pool on a single drive
Jan Hellevik wrote:
Yes, I can try to do that. I do not have any more of this brand of disk, but I
guess that does not matter. It will have to wait until tomorrow (I have an
appointment in a few minutes, and it is getting late here in Norway), but I
will try first thing tomorrow. I guess a
j...@opensolaris:~$ zpool clear vault
cannot open 'vault': no such pool
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Yes, I turned the system off before I connected the disks to the other
controller. And I turned the system off beore moving them back to the original
controller.
Now it seems like the system does not see the pool at all.
The disks are there, and they have not been used so I do not understand
Now that you've re-imported, it seems like zpool clear may be the
command you need, based on discussion in these links about missing and
broken zfs logs:
http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg37554.html
http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg30469.html
Is there any chance that the second controller wrote something onto the
disks when it saw the disks attached to it, thus corrupting the ZFS
drive signatures or more?
I've heard that some controllers require drives to be initialized by
them and/or signatures written to drives by them. Maybe
You may or may not need to add the log device back.
zfs clear should bring the pool online.
either way shouldn't affect the data.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
Hi!
I feel panic is close...
Short version: I moved the disks of a pool to a new controller without
exporting it first. Then I moved them back to the original controller, but I
still cannot import the pool.
I am new to Opensolaris and ZFS - have set up a box to keep my images and
videos.
When I boot up without the disks in the slots. I manually bring the pool on
line with
zpool clear poolname
I believe that was what you were missing from your command. However I did not
try to change controller.
Hopefully you only been unplug disks while the system is turn off. If that's
26 matches
Mail list logo
