Hi, After 2 weeks of successful using of NILFS on my pendrive I encountered this error:
mi...@computer:~$ sudo mount /media/pendrive/ [sudo] password for user: mount.nilfs2: Error while mounting /dev/sdb on /media/pendrive: Invalid argument First, I thought there was something wrong with /etc/fstab entry, which looks like this: /dev/sdb /media/pendrive nilfs2 noauto,user,rw 0 0 But it looked the same when drive was working fine, I also tried different parameters but it did not help. The last two lines from dmesg output made me even more worry: [ 759.733075] usb 7-3: new high speed USB device using ehci_hcd and address 5 [ 763.362043] usb 7-3: configuration #1 chosen from 1 choice [ 763.713991] usbcore: registered new interface driver libusual [ 763.730554] Initializing USB Mass Storage driver... [ 763.730704] scsi5 : SCSI emulation for USB Mass Storage devices [ 763.732474] usbcore: registered new interface driver usb-storage [ 763.732480] USB Mass Storage support registered. [ 763.732647] usb-storage: device found at 5 [ 763.732649] usb-storage: waiting for device to settle before scanning [ 768.732513] usb-storage: device scan complete [ 768.733715] scsi 5:0:0:0: Direct-Access USB 2.0 Flash Disk 1100 PQ: 0 ANSI: 0 CCS [ 768.747539] sd 5:0:0:0: [sdb] 62652416 512-byte hardware sectors (32078 MB) [ 768.748544] sd 5:0:0:0: [sdb] Write Protect is off [ 768.748552] sd 5:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 768.748557] sd 5:0:0:0: [sdb] Assuming drive cache: write through [ 768.752786] sd 5:0:0:0: [sdb] 62652416 512-byte hardware sectors (32078 MB) [ 768.753780] sd 5:0:0:0: [sdb] Write Protect is off [ 768.753787] sd 5:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 768.753792] sd 5:0:0:0: [sdb] Assuming drive cache: write through [ 768.753803] sdb: sdb1 [ 768.857613] sd 5:0:0:0: [sdb] Attached SCSI removable disk [ 768.857786] sd 5:0:0:0: Attached scsi generic sg2 type 0 [ 1130.248957] NILFS warning: Segment magic number invalid [ 1130.248965] NILFS: error searching super root. I'm using nilfs2-tools 2.0.3-1 on kernel 2.6.27-10, the error also occurs after upgrade to nilfs2-utils and nilfs kernel module 2.0.6. How can I recover this drive? I didn't create any checkpoints, afair the only thing I have done was to create the new filesystem using mkfs.nilfs2 command.
_______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
