search for: 00001b0

...against /dev/sdj3 What's odd is that I also have 4*1Tbyte disks in another raid array but these are partitioned with standard MBR partitions, and these are not reporting this problem. % dd if=/dev/sdd count=1 2> /dev/null | hexdump 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 00001b0 0000 0000 0000 0000 0000 0000 0000 0100 00001c0 0001 fefd ffff 003f 0000 5982 7470 0000 00001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55 0000200 % mdadm --examine /dev/sdd /dev/sdd: MBR Magic : aa55 Partition[0] : 1953520002...

Hello everyone, recently I've found something I consider a bug. Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A. Imagine my surprise when I saw that all messages that are being output on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are terminated with 0x0D, 0x0A. Maybe that's standard behaviour of all stderr messages in all Linux

...fff ffff ffff ................ 0000170: ffff ffff ffff ffff ffff ffff ffff ffff ................ 0000180: ffff ffff ffff ffff ffff ffff ffff ffff ................ 0000190: ffff ffff ffff ffff ffff ffff ffff ffff ................ 00001a0: ffff ffff ffff ffff ffff ffff ffff ffff ................ 00001b0: ffff ffff ffff ffff ffff ffff ffff ffff ................ 00001c0: ffff ffff ffff ffff ffff ffff ffff ffff ................ 00001d0: ffff ffff ffff ffff ffff ffff ffff ffff ................ 00001e0: ffff ffff ffff ffff ffff ffff ffff ffff ................ 00001f0: ffff ffff ffff ffff ffff ffff...

This past Tuesday (2/22/07) my flash drive started acting really strange - it only worked intermittently and would disappear right after an access or two. Yesterday it stopped working altogether - I couldn't even access it through my WinXP-on-VMWare. I rebooted my machine, and it worked fine after that. Is there some time limit on how long a USB flash drive will work in CentOS or is this a