Search results

  1. S

    Unstoppable resilver

    I've rebooted the machine and the resilver started again :(
  2. S

    Unstoppable resilver

    Looks like it's not finished... I've upgraded the pool to version 28, scrubbed again and cleared the errors but the metadata error is still here: [root@pr0nserv ~]# zpool status -v pool: pr0nserv state: ONLINE status: One or more devices has experienced an error resulting in data...
  3. S

    Unstoppable resilver

    Looks like I've solved with a zpool detach pr0nserv 6530854401941125969 Now I'm scrubbing to see if that fixes the metadata error.
  4. S

    Unstoppable resilver

    Hi, I've a problem with my ZFS pool on FreeBSD 8.3-RELEASE. The pool is version 15, composed by four disks, two mirror. This was the situation: I had a faulty disk in the second mirror and before I was able to replace it the other one started having problems ("Already active DMA on this...
  5. S

    upgrade from 8.2 to 8.3 error: cannot mount root

    Yes, sorry, I was meaning da0 and da1. The disk is connected via USB. If I start with the disk, it read the MBR and the FreeBSD boot manager works but later it can't mount root and if I type ? it doesn't find any disk. I tried changing the USB slot of the disk, nothing. I tried changing the...
  6. S

    upgrade from 8.2 to 8.3 error: cannot mount root

    I think it's changed, yeah. The problem is that I don't know what to put there. If I boot with the memstick I can see it as ad1 (since ad0 is the memstick), but when I need to boot from it it doesn't work. I tried with ad1s1a and ad0s1a in /etc/fstab, nothing.
  7. S

    upgrade from 8.2 to 8.3 error: cannot mount root

    Hi, I was upgrading from 8.2-release to 8.3-release, after the first freebsd-update install I've rebooted and now the system doesn't boot anymore, it gives me CANNOT MOUNT ROOT If I try with ? it doesn't return any disk/slice. I think the ID of the disk changed, I've not set any label. I tried...
Back
Top