Date: Sun, 24 Jul 2016 20:13:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211028] [GEOM][Hyper-V] gpart can't detect the new free space after the disk capacity changes Message-ID: <bug-211028-8-PcDBK3B3nc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211028-8@https.bugs.freebsd.org/bugzilla/> References: <bug-211028-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211028 --- Comment #31 from Peter Wemm <peter@FreeBSD.org> --- The first few boot attempts looked like this: ... (da0:mpt0:0:0:0): UNMAPPED (da1:mpt0:0:1:0): da0 at mpt0 bus 0 scbus0 target 0 lun 0 da0: <FUJITSU MAS3735NC 5B08> Fixed Direct Access SCSI-3 device da0: Serial Number A107P49025GU da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da0: Command Queueing enabled da0: 70007MB (143374650 512 byte sectors) da0: Delete methods: <NONE(*),ZERO> ses0: Nfans 0 Npwr 0 Nslots 6 Lck 0 Ntherm 0 Nspkrs 0 Ntstats 0 UNMAPPED (da2:mpt0:0:2:0): UNMAPPED (da3:mpt0:0:3:0): UNMAPPED (da4:mpt0:0:4:0): UNMAPPED (da5:mpt0:0:5:GEOM: new disk da0 (73407820800 bytes) GEOM: new disk da1 (0 bytes) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ GEOM: new disk da2 (0 bytes) da3 at mpt0 bus 0 scbus0 target 3 lun 0 da3: <FUJITSU MAS3735NC 5B08> Fixed Direct Access SCSI-3 device da3: Serial Number A107P49025H7 da3: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da3: Command Queueing enabled da3: 70007MB (143374650 512 byte sectors) da3: Delete methods: <NONE(*),ZERO> da2 at mpt0 bus 0 scbus0 target 2 lun 0 da2: <FUJITSU MAS3735NC 5B08> Fixed Direct Access SCSI-3 device da2: Serial Number A107P49025GB da2: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da2: Command Queueing enabled da2: 70007MB (143374650 512 byte sectors) da2: Delete methods: <NONE(*),ZERO> da1 at mpt0 bus 0 scbus0 target 1 lun 0 da1: <FUJITSU MAS3735NC 5B08> Fixed Direct Access SCSI-3 device da1: Serial Number A107P49025H2 da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da1: Command Queueing enabled da1: 70007MB (143374650 512 byte sectors) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ da1: Delete methods: <NONE(*),ZERO> da4 at mpt0 bus 0 scbus0 target 4 lun 0 da4: <MAXTOR ATLAS15K_73SCA DT60> Fixed Direct Access SCSI-3 device da4: Serial Number C80666ZK da4: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da4: Command Queueing enabled da4: 70007MB (143374650 512 byte sectors) da4: Delete methods: <NONE(*),ZERO> GEOM: new disk da3 (73407820800 bytes) GEOM: new disk da4 (73407820800 bytes) 0): UNMAPPED pass0 at mpt0 bus 0 scbus0 target 0 lun 0 da5 at mpt0 bus 0 scbus0 target 5 lun 0 da5: <FUJITSU MAS3735NC 5B08> Fixed Direct Access SCSI-3 device da5: Serial Number A107P49025GP da5: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da5: Command Queueing enabled da5: 70007MB (143374650 512 byte sectors) da5: Delete methods: <NONE(*),ZERO> ... Note the "GEOM new disk, 0 bytes" happens before the probe messages.=20 Presumably the nature of the original panic we were seeing was that was try= ing to resize an uninitialized disk. It no longer detects the corrupt GPT but no longer panics either. The machine in question is slow to boot, but I'll try a few more iterations. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211028-8-PcDBK3B3nc>