You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Other Issues » [SOLVED] USB floppy » 2024-03-29 08:58:22
It worked. I just had to replace fd0 with sdb in /etc/mtools.conf.
Thank you again.
#2 Re: Other Issues » [SOLVED] USB floppy » 2024-03-28 17:40:00
Mtools! It rings a bell. I'll give it a try, thanks.
#3 Other Issues » [SOLVED] USB floppy » 2024-03-28 15:40:52
- Fruchtenstein
- Replies: 3
Bought a USB FDD to try to read floppies from my 25 year old archive, but can't mount any of them. The OS finds the new device and names it /dev/sdb:
[1346890.116543] usb 1-2: new full-speed USB device number 76 using xhci_hcd
[1346890.265638] usb 1-2: New USB device found, idVendor=0644, idProduct=0000, bcdDevice= 2.00
[1346890.265654] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[1346890.265660] usb 1-2: Product: TEACV0.0
[1346890.265665] usb 1-2: Manufacturer: TEACV0.0
[1346890.268096] usb-storage 1-2:1.0: USB Mass Storage device detected
[1346890.268830] scsi host1: usb-storage 1-2:1.0
[1346891.327366] scsi 1:0:0:0: Direct-Access TEAC USB UF000x 0.00 PQ: 0 ANSI: 0 CCS
[1346891.327954] sd 1:0:0:0: Attached scsi generic sg1 type 0
[1346891.455180] sd 1:0:0:0: [sdb] Media removed, stopped polling
[1346891.456007] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[1346891.711236] sd 1:0:0:0: ioctl_internal_command return code = 402
[1346891.711249] sd 1:0:0:0: Sense Key : Data Protect [current]
[1346891.711256] sd 1:0:0:0: Add. Sense: Medium not present
[1346892.031314] sd 1:0:0:0: ioctl_internal_command return code = 402
[1346892.031328] sd 1:0:0:0: Sense Key : Data Protect [current]
[1346892.031334] sd 1:0:0:0: Add. Sense: Medium not presentThen I insert a disk and it's not recognized:
[1347187.007668] sd 1:0:0:0: [sdb] 2880 512-byte logical blocks: (1.47 MB/1.41 MiB)
[1347187.135651] sdb: detected capacity change from 0 to 2880
[1347187.647358] sdb:
[1347190.591638] sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[1347190.591654] sd 1:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[1347190.591663] sd 1:0:0:0: [sdb] tag#0 Add. Sense: Cannot read medium - unknown format
[1347190.591670] sd 1:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 08 00 00 00 08 00 00 00
[1347190.591675] I/O error, dev sdb, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2/dev/fd0 doesn't exist and I can't mount /dev/sdb:
# mount /dev/sdb /mnt/hdd/
mount: /mnt/hdd: /dev/sdb already mounted or mount point busy.
dmesg(1) may have more information after failed mount system call.but I can retrieve data using Photorec.
Some of those floppies I can read on a Windows computer, but can't mount under Linux. Chances are that a kernel module is missing, I guess, but I'm not sure.
I'd appreciate any ideas.
#4 Re: Hardware & System Configuration » merged /usr » 2024-02-14 10:31:21
I just had to create `build` and `source` symlinks in `/lib/modules/6.6.13-amd64` to build VirtualBox modules.
#5 Re: Hardware & System Configuration » merged /usr » 2024-01-15 07:22:18
If they are going to do that, why not put a symbolic link from /bin/hostname to /usr/bin/hostname like I have to do manually?
Because the plan is to empty /bin completely and replace it with a symlink to /usr/bin. This article explains it in vague terms: https://www.freedesktop.org/wiki/Softwa … eUsrMerge/
Like for sed, maintainer Clint Adams <clint@debian.org>, the only motivations for those moves are hubris and deliberate intent to cause trouble.
They're just maintainers, they follow the party line: https://lists.debian.org/debian-devel-a … 00003.html
#6 Re: Off-topic » What are you reading/want to read ? » 2024-01-15 07:13:07
Anthropological bestseller Watching The English by Kate Fox.
Crime story from 18 century France L'énigme des Blancs-Manteaux by Jean-François Parot.
#7 Re: Other Issues » [SOLVED] Broken update » 2024-01-14 15:19:55
OlegShtch, I don't use display managers and launch X by running startx from command line. In this case I had so many problems with logging in that I never made it that far 
#8 Re: Other Issues » [SOLVED] Broken update » 2024-01-12 12:55:47
Yes, that's it, for sure. I forgot to mention issues with 'sed', too. And I missed insmod, lsmod and rmmod.
Bootable USB drive is one of those things that I create every once in a while and then never can find it. But now that I can boot to an older kernel, I guess, I may cope without it.
I feel an urge to install usrmerge, but not until I find or make a bootable drive, of course.
Thanks!
#9 Other Issues » [SOLVED] Broken update » 2024-01-12 11:15:42
- Fruchtenstein
- Replies: 5
Hello,
I had problems with the last update on my Excalibur installation. I ran the usual update/upgrade sequence yesterday (Jan 11) and after reboot kernel 6.5.0.5 booted to busybox. 6.5.0.4 did the trick and I managed to find out that the problems were probably related to /usr merge (usrmerge package is not installed). For example, files like /sbin/modprobe, /sbin/modinfo, /sbin/dmsetup were missing. I restored them as symlinks to their /usr/sbin counterparts, but now update-initramfs keeps failing on /usr/share/initramfs-tools/hooks/dmsetup, one of possible reasons being that /usr/lib/udev/rules.d contained only a subset of files in /lib/udev/rules.d. Some other issues with update-initramfs, for example, mdadm errors, I kinda 'solved' by removing mdadm from the system.
What do you think would be the right way of finding and fixing all possible related issues? Right now I still can boot to 6.5.0.4 and keep on working almost as if nothing has happened. Well, except for being unable to run update-initramfs, maybe, and it IS a huge problem for the future.
OTOH, it seems that it may be not the only problem. So, I had to recreate /dev/net/ directory and /dev/net/tun device manually. Still can't find any signs of what went wrong with the upgrade.
Last time I updated the system was on Dec 25 and the whole thing was fine and smooth.
Pages: 1
Board footer
