Opened 16 years ago
Closed 15 years ago
#3734 closed bug (fixed)
BFS formatted USB memory stick not found
Reported by: | haiqu | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
Formatted a 2Gb Toshiba memory stick and copied the sources to it. On the next boot, I could not mount the drive as it does not appear in the mount menu.
The device seems to be present, but not recognised with this formatting. A stick with FAT format inserted into the same slot is mounted immediately and automatically.
Change History (8)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Status: | new → assigned |
---|
Can you please provide a syslog? If the stick worked at first and then doesn't after a reboot then it's most probably not a USB problem. In that case the filesystem probably got corrupted.
comment:3 by , 16 years ago
Sure, no problem. I just took my 2Gb stick and did the following:
- Formatted it to FAT32 under WinXP
- Booted Haiku and inserted it into the onboard USB slots, and into the slots on a USB card I have in my development computer, and ensured that it mounted on both.
- Initialized the stick to BFS.
- Rebooted. NO STICK.
~> tail /var/log/syslog KERN: loaded driver /boot/home/config/add-ons/kernel/drivers/dev/oss/oss_loader KERN: bfs: bfs_create_index:1981: File or Directory already exists Last message repeated 1 time KERN: oss_contig_malloc: area 4192 @ va 0x8567c000, pa 0x00264000, sz 32768 KERN: oss_contig_malloc: area 4193 @ va 0x8567c000, pa 0x00264000, sz 32768 KERN: bfs: mounted "BeOS 5.0.3 Pro" (root node at 131072, device = /dev/disk/ata/0/master/0) KERN: bfs: mounted "Image" (root node at 131072, device = /dev/disk/ata/1/slave/0) KERN: bfs: bfs_create_index:1981: File or Directory already exists KERN: bfs: bfs_open:1178: Read-only file system KERN: bfs: bfs_create_index:1981: File or Directory already exists ~>
follow-up: 5 comment:4 by , 16 years ago
Taking it out and reinserting to the other bus gives me this:
~> tail -n20 /var/log/syslog KERN: trying: file_systems/rootfs/v1 KERN: returned: -1 KERN: trying: partitioning_systems/session/v1 KERN: returned: -1 KERN: trying: file_systems/attribute_overlay/v1 KERN: returned: -1 KERN: trying: file_systems/cdda/v1 KERN: usb_disk: unhandled ioctl 10102 KERN: returned: -1 KERN: trying: file_systems/ext2/v1 KERN: returned: -2147483648 KERN: trying: file_systems/fat/v1 KERN: returned: -1 KERN: trying: file_systems/iso9660/v1 KERN: identify(11, 0x80fde940) KERN: returned: -1 KERN: trying: file_systems/nfs/v1 KERN: returned: -1 KERN: trying: file_systems/write_overlay/v1 KERN: returned: -1 ~>
Seems like it's trying everything except BFS.
comment:5 by , 16 years ago
Component: | Drivers/USB → - General |
---|
Replying to haiqu:
Taking it out and reinserting to the other bus gives me this: Seems like it's trying everything except BFS.
Because 20 lines are most probably not enough. Please just attach full syslogs as they do contain all the information where someone can then read out the relevant stuff. This is easier than explaining what parts to capture every time. In any case this is not a USB problem as the stick obviously works. USB only provides the data transport and does not affect the filesystem operations that seem to go wrong here.
comment:7 by , 16 years ago
It's better. I can mount, copy to and extract data from a BFS formatted USB stick now. Unmounting causes a kernel page fault.
comment:8 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Sounds like this has been fixed.
Correction, it was initialized with BFS, not formatted.