Re: Formatting a 4k disk on FreeBSD with ext2
That looks like its trying to do an erase of the sectors, which is likely failing due to the device being a HW RAID, have you tried with nodiscard set? On 08/05/2017 16:42, HSR Hackspace wrote: Hi folks; I'm trying to format a 300 GB partition on x86_64 box running running BSD 10.1 with HW RAID configuration. All my attempt so far have failed. Below are the logs for same. Logs: 1. pod1208-wsa07:rtestuser 106] ./mkfs.ext3 /dev/da0p7 mke2fs 1.43.4 (31-Jan-2017) Warning: could not erase sector 2: Invalid argument-> Creating filesystem with 78643200 4k blocks and 19660800 inodes Filesystem UUID: c31fab56-f690-4313-a09c-9a585224caea Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616 Allocating group tables: done Warning: could not read block 0: Invalid argument ---> Warning: could not erase sector 0: Invalid argument Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information:0/2400 Warning, had trouble writing out superblocks. pod1208-wsa07:rtestuser 107] 2. pod1208-wsa07:rtestuser 32] ./fsck.ext2 -v -b 4096 /dev/da0p7 e2fsck 1.43.4 (31-Jan-2017) ./fsck.ext2: Invalid argument while trying to open /dev/da0p7 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 or e2fsck -b 32768 pod1208-wsa07:rtestuser 33] +++ 3. pod1208-wsa07:rtestuser 43] ./dumpe2fs /dev/da0p7 dumpe2fs 1.43.4 (31-Jan-2017) ./dumpe2fs: Invalid argument while trying to open /dev/da0p7 Couldn't find valid filesystem superblock. pod1208-wsa07:rtestuser 44] +++ 4. +++ pod1208-wsa07:rtestuser 29] ./mkfs.ext2 -b 4096 /dev/da0p7 mke2fs 1.43.4 (31-Jan-2017) Warning: could not erase sector 2: Invalid argument Creating filesystem with 78643200 4k blocks and 19660800 inodes Filesystem UUID: 015a85a4-7db9-4767-869c-7bab11c9074e Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616 Allocating group tables: done Warning: could not read block 0: Invalid argument Warning: could not erase sector 0: Invalid argument Writing inode tables: done Writing superblocks and filesystem accounting information:0/2400 Warning, had trouble writing out superblocks. pod1208-wsa07:rtestuser 30] 5. pod1208-wsa07:rtestuser 31] camcontrol identify da0 camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed pod1208-wsa07:rtestuser 32] 6. pod1208-wsa07:rtestuser 24] diskinfo -c da0 da0 4096# sectorsize 1197995982848 # mediasize in bytes (1.1T) 292479488 # mediasize in sectors 0 # stripesize 0 # stripeoffset 18206 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. 00ff273941fd086a1ec0fbb015e7a68d# Disk ident. I/O command overhead: ^[OAtime to read 10MB block 0.004811 sec =0.000 msec/sector time to read 20480 sectors 0.491882 sec =0.024 msec/sector calculated command overhead =0.024 msec/sector pod1208-wsa07:rtestuser 25] diskinfo -c da0p7 da0p7 4096# sectorsize 322122547200# mediasize in bytes (300G) 78643200# mediasize in sectors 0 # stripesize 1493762048 # stripeoffset 4895# Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. 00ff273941fd086a1ec0fbb015e7a68d# Disk ident. I/O command overhead: time to read 10MB block 0.004860 sec =0.000 msec/sector time to read 20480 sectors 0.495921 sec =0.024 msec/sector calculated command overhead =0.024 msec/sector 7. pod1208-wsa07:rtestuser 21] gpart show -l 6 292479477 da0 GPT (1.1T) 6 10 - free - (40K) 161281 (null) (512K) 144 2621442 efi (1.0G) 26228810485763 rootfs (4.0G) 131086420971524 swap (8.0G) 340801610485765 nextroot (4.0G) 4456592 1024006 var (400M) 4558992 786432007 raw
Formatting a 4k disk on FreeBSD with ext2
Hi folks; I'm trying to format a 300 GB partition on x86_64 box running running BSD 10.1 with HW RAID configuration. All my attempt so far have failed. Below are the logs for same. Logs: 1. pod1208-wsa07:rtestuser 106] ./mkfs.ext3 /dev/da0p7 mke2fs 1.43.4 (31-Jan-2017) Warning: could not erase sector 2: Invalid argument-> Creating filesystem with 78643200 4k blocks and 19660800 inodes Filesystem UUID: c31fab56-f690-4313-a09c-9a585224caea Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616 Allocating group tables: done Warning: could not read block 0: Invalid argument ---> Warning: could not erase sector 0: Invalid argument Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information:0/2400 Warning, had trouble writing out superblocks. pod1208-wsa07:rtestuser 107] 2. pod1208-wsa07:rtestuser 32] ./fsck.ext2 -v -b 4096 /dev/da0p7 e2fsck 1.43.4 (31-Jan-2017) ./fsck.ext2: Invalid argument while trying to open /dev/da0p7 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 or e2fsck -b 32768 pod1208-wsa07:rtestuser 33] +++ 3. pod1208-wsa07:rtestuser 43] ./dumpe2fs /dev/da0p7 dumpe2fs 1.43.4 (31-Jan-2017) ./dumpe2fs: Invalid argument while trying to open /dev/da0p7 Couldn't find valid filesystem superblock. pod1208-wsa07:rtestuser 44] +++ 4. +++ pod1208-wsa07:rtestuser 29] ./mkfs.ext2 -b 4096 /dev/da0p7 mke2fs 1.43.4 (31-Jan-2017) Warning: could not erase sector 2: Invalid argument Creating filesystem with 78643200 4k blocks and 19660800 inodes Filesystem UUID: 015a85a4-7db9-4767-869c-7bab11c9074e Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616 Allocating group tables: done Warning: could not read block 0: Invalid argument Warning: could not erase sector 0: Invalid argument Writing inode tables: done Writing superblocks and filesystem accounting information:0/2400 Warning, had trouble writing out superblocks. pod1208-wsa07:rtestuser 30] 5. pod1208-wsa07:rtestuser 31] camcontrol identify da0 camcontrol: ATA ATAPI_IDENTIFY via pass_16 failed pod1208-wsa07:rtestuser 32] 6. pod1208-wsa07:rtestuser 24] diskinfo -c da0 da0 4096# sectorsize 1197995982848 # mediasize in bytes (1.1T) 292479488 # mediasize in sectors 0 # stripesize 0 # stripeoffset 18206 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. 00ff273941fd086a1ec0fbb015e7a68d# Disk ident. I/O command overhead: ^[OAtime to read 10MB block 0.004811 sec =0.000 msec/sector time to read 20480 sectors 0.491882 sec =0.024 msec/sector calculated command overhead =0.024 msec/sector pod1208-wsa07:rtestuser 25] diskinfo -c da0p7 da0p7 4096# sectorsize 322122547200# mediasize in bytes (300G) 78643200# mediasize in sectors 0 # stripesize 1493762048 # stripeoffset 4895# Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. 00ff273941fd086a1ec0fbb015e7a68d# Disk ident. I/O command overhead: time to read 10MB block 0.004860 sec =0.000 msec/sector time to read 20480 sectors 0.495921 sec =0.024 msec/sector calculated command overhead =0.024 msec/sector 7. pod1208-wsa07:rtestuser 21] gpart show -l 6 292479477 da0 GPT (1.1T) 6 10 - free - (40K) 161281 (null) (512K) 144 2621442 efi (1.0G) 26228810485763 rootfs (4.0G) 131086420971524 swap (8.0G) 340801610485765 nextroot (4.0G) 4456592 1024006 var (400M) 4558992 786432007 raw (300G) 83202192 5242888 godspeed (2.0G) 83726480 2087529929 data (796G) 292479472 11 - free - (44K) Let me know if anyone have formatted 4k drive with ext2 recently. If yes from where should I start
new 'make installworld' warnings
I buildworld / installworld a few times per week. I don't think I've ever seen these messages before: make[1]: "/usr/obj/usr/src/compiler-metadata.mk" line 1: Using cached compiler metadata from build at cow.example.com on Sun May 7 09:13:52 CDT 2017 make[3]: "/usr/obj/usr/src/compiler-metadata.mk" line 1: Using cached compiler metadata from build at cow.example.com on Sun May 7 09:13:52 CDT 2017 Possibly due to a significant enough deley between the run of buildworld and installworld? Build and install were otherwise successful. This happened when transitioning between 317440-stable -> 317906-stable Dan ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
