On 23 Jul 2024 14:49 -0300, from edua...@kalinowski.com.br (Eduardo M
KALINOWSKI):
> As described on the sshfs manpage, by default only the mounting user (root,
> in your case) can access the filesystem.
>
> You can use -o allow_other to allow other users. Or, if it's only eben
> that'll be acces
On 23/07/2024 14:40, Eben King wrote:
And after I issue this command:
root@cerberus:~# sshfs -o default_permissions
sshd@white_mycloud:/mnt/HD/HD_a2/Public /mnt/white_mycloud/
sshd@white_mycloud's password:
By the prompt (and the behavior below) I assume you're mounting as root.
it looks like
On Sun 04 Jun 2023 at 11:59:21 (-0400), ce wrote:
> I have a mountpoint where all files under it have a group `fuse`.
>
> This is strange to me.
>
> As far as I can remember, Ubuntu doesn't do this.
Is this a system that's been around since wheezy? Up until then,
Debian had a system group called
I think you have a partition with filesystem btrfs that uses compression
with lzop.
Perhaps inside of it you have a file that is a compressed filesystem (that
is fuse: *Filesystem in Userspace* )
what can you see when you type in
$ cd /mnt/part2
$ ls -la
El lun, 5 jun 2023 a las 6:32, ce () escr
On 6/5/23 7:23 AM, Greg Wooledge wrote:
>
> You can run the command "mount" with no arguments to see the details of
> each mounted file system. You don't even have to be root. I don't know
> how btrfs subvolumes work, so I don't know whether they appear in the
> output of mount, but you could
On Sun, Jun 04, 2023 at 11:00:18PM -0400, ce wrote:
> On 6/4/23 5:46 PM, Greg Wooledge wrote:
> > What kind of hardware is this file system on?
> >
> > What kind of file system is it?
> >
> > How did you mount it? (Show the command you used, and any output that
> > it produced.)
> >
> > What does
On 6/4/23 5:46 PM, Greg Wooledge wrote:
> On Sun, Jun 04, 2023 at 11:59:21AM -0400, ce wrote:
> > I have a mountpoint where all files under it have a group `fuse`.
>
> You need to provide details, or else nobody can help you with anything.
>
> What kind of hardware is this file system on?
>
> Wh
On Sun, Jun 04, 2023 at 11:59:21AM -0400, ce wrote:
> I have a mountpoint where all files under it have a group `fuse`.
You need to provide details, or else nobody can help you with anything.
What kind of hardware is this file system on?
What kind of file system is it?
How did you mount it? (S
The provider has separated block device service, like what Ceph does.
So I have to buy another 100GB block device as the secondary disk.
Sincerely,
Ken Young
On Mon, Mar 6, 2023 at 6:26 AM Andy Smith wrote:
> Hi,
>
> On Mon, Mar 06, 2023 at 03:11:43AM +0800, Ken Young wrote:
> > Filesystem
Hi,
On Mon, Mar 06, 2023 at 03:11:43AM +0800, Ken Young wrote:
> Filesystem Size Used Avail Use% Mounted on
> /dev/vda1 9.7G 1.5G 7.9G 16% /
> ...
>
> So I want to add a block device /dev/vdb and fdisk/format it and mount it
> as /home dir.
Have you checked your VPS provider's doc
On 2023-03-05 at 14:11, Ken Young wrote:
> Hello
>
> My vps has limited volume for /. You can see it as follows.
>
> root@nxacloud-bloghost:~# lsb_release -cd
>
> Description: Debian GNU/Linux 11 (bullseye)
>
> Codename: bullseye
>
>
> root@nxacloud-bloghost:~# df -h
>
> Filesystem Siz
On Tue, Oct 04, 2022 at 12:04:56PM +0100, tony wrote:
> I can successfully do (pls ignore spurious line break):
>
> mount -t nfs -o _netdev tony-fr:/mnt/sharedfolder
> /mnt/sharedfolder_client
>
> but the user id is incorrect.
What do you mean, "the user id"? As if there's only one?
This isn't
On Wed 02 Feb 2022 at 11:16:18 (+0100), Yvan Masson wrote:
>
> > > > > Slightly off-topic question: using pre-5.15 kernel, how can I
> > > > > mount a
> > > > > partition with kernel driver?
> > > >
> > > > You can't, the NTFS kernel driver first appeared in Linux 5.15.
> > > >
> > > From what
Slightly off-topic question: using pre-5.15 kernel, how can I
mount a
partition with kernel driver?
You can't, the NTFS kernel driver first appeared in Linux 5.15.
From what I understand, there was a read-only driver before 5.15:
- see for example
https://superuser.com/questions/139452/ker
On Tue, 2022-02-01 at 17:56 +0100, Yvan Masson wrote:
>
> Le 01/02/2022 à 14:24, Tixy a écrit :
> > On Tue, 2022-02-01 at 13:39 +0100, Yvan Masson wrote:
> > > Le 31/01/2022 à 18:02, Christian Britz a écrit :
> > > >
> > > >
> > > > On 2022-01-31 11:43 UTC+0100, Yvan Masson wrote:
> > > >
> > >
Le 01/02/2022 à 14:24, Tixy a écrit :
On Tue, 2022-02-01 at 13:39 +0100, Yvan Masson wrote:
Le 31/01/2022 à 18:02, Christian Britz a écrit :
On 2022-01-31 11:43 UTC+0100, Yvan Masson wrote:
Thanks for the links, I missed that NTF3 was already included in the
kernel I use (from Debian testi
On Tue, 2022-02-01 at 13:39 +0100, Yvan Masson wrote:
> Le 31/01/2022 à 18:02, Christian Britz a écrit :
> >
> >
> > On 2022-01-31 11:43 UTC+0100, Yvan Masson wrote:
> >
> > > Thanks for the links, I missed that NTF3 was already included in the
> > > kernel I use (from Debian testing). So in my
Le 31/01/2022 à 18:02, Christian Britz a écrit :
On 2022-01-31 11:43 UTC+0100, Yvan Masson wrote:
Thanks for the links, I missed that NTF3 was already included in the
kernel I use (from Debian testing). So in my case ntfs3g is able to
mount a rescued partition, while NTFS3 is not (thanks And
On 2022-01-31 11:43 UTC+0100, Yvan Masson wrote:
> Thanks for the links, I missed that NTF3 was already included in the
> kernel I use (from Debian testing). So in my case ntfs3g is able to
> mount a rescued partition, while NTFS3 is not (thanks Andrei for
> confirming what I supposed): this
Le 31/01/2022 à 16:19, Michael Stone a écrit :
On Mon, Jan 31, 2022 at 11:43:10AM +0100, Yvan Masson wrote:
Thanks for the links, I missed that NTF3 was already included in the
kernel I use (from Debian testing). So in my case ntfs3g is able to
mount a rescued partition, while NTFS3 is not (th
On Mon, Jan 31, 2022 at 11:43:10AM +0100, Yvan Masson wrote:
Thanks for the links, I missed that NTF3 was already included in the
kernel I use (from Debian testing). So in my case ntfs3g is able to
mount a rescued partition, while NTFS3 is not (thanks Andrei for
confirming what I supposed): thi
Le 28/01/2022 à 17:51, David Wright a écrit :
On Fri 28 Jan 2022 at 11:34:44 (+0100), Yvan Masson wrote:
I had to recover a NTFS partition from a broken drive (I used GNU
ddrescue with a domain log file generated by partclone), so I now have
a file "recovered_partition.img":
$ file recovered_
On Fri 28 Jan 2022 at 11:34:44 (+0100), Yvan Masson wrote:
>
> I had to recover a NTFS partition from a broken drive (I used GNU
> ddrescue with a domain log file generated by partclone), so I now have
> a file "recovered_partition.img":
>
> $ file recovered_partition.img
> recovered_partition.im
On Vi, 28 ian 22, 11:34:44, Yvan Masson wrote:
>
> Could it be because `mount` uses kernel driver and `mount.ntfs` uses
> ntfs-3g, and that the latter has better "quality" even for read-only? (Note
> that this sentence is a complete guess)
Try 'ls -l /sbin/mount.ntfs' ;)
Kind regards,
Andrei
--
Richmond writes:
> When I try to mount Windows 10 partition from Linux it says:
>
> "Windows is hibernated, refused to mount.
> Falling back to read-only mount because the NTFS partition is in an
> unsafe state. Please resume and shutdown Windows fully (no hibernation
> or fast restarting.)
> Cou
You can disable the Hibernate option in Windows (different from fast logon).
On 2021-07-11 6:24 p.m., Richmond wrote:
> Richmond writes:
>
>> When I try to mount Windows 10 partition from Linux it says:
>>
>> "Windows is hibernated, refused to mount.
>> Falling back to read-only mount because t
On Tue, Jul 14, 2020 at 02:00:53PM +0200, Albretch Mueller wrote:
> On 7/9/20, Reco wrote:
> > More or less. The correct sequence is:
> > 1) cryptsetup luksOpen
> > 2) pvscan && vgchange -ay
> > 3) mount "/dev/lbrtchx-vg/home" "/media/abc123"
> >
> > And the unmounting should go in reverse:
> > 1)
On 7/9/20, Reco wrote:
> More or less. The correct sequence is:
> 1) cryptsetup luksOpen
> 2) pvscan && vgchange -ay
> 3) mount "/dev/lbrtchx-vg/home" "/media/abc123"
>
> And the unmounting should go in reverse:
> 1) umount /media/...
> 2) vghcange -an ...
> 3) cryptsetup luksClose
thank you, bu
On Thu, Jul 09, 2020 at 08:28:24AM -0400, Albretch Mueller wrote:
> so, I should go?:
>
> mkdir -p "/media/abc123"
>
> mount "/dev/lbrtchx-vg/home" "/media/abc123"
More or less. The correct sequence is:
1) cryptsetup luksOpen
2) pvscan && vgchange -ay
3) mount "/dev/lbrtchx-vg/home" "/media/a
so, I should go?:
mkdir -p "/media/abc123"
mount "/dev/lbrtchx-vg/home" "/media/abc123"
Hi.
On Thu, Jul 09, 2020 at 06:54:05AM -0400, Albretch Mueller wrote:
> but when I try to mount the device:
>
> _DEV_CR_CRYPTO=$(cryptsetup status "${_CR_CRYPTO}" | head -n 1 | awk
> '{print $1}')
...
> date; time mount --verbose "${_DEV_CR_CRYPTO}" "${_MED_MNT}" -r
> fi
>
> I am gettin
On Mi, 06 mai 20, 01:35:02, Michael Morgan wrote:
>
> Since automount works, and samba will work well if I restart it, my guess is
> that on boot, samba (smbd service) starts before /usb-hdd is mounted. To
> make it working,
> I need make sure the fstab mounting happens before samba starts. Can a
On 06.05.20 08:35, Michael Morgan wrote:
Dear all,
I have an external usb hdd. I would like to automount it on boot and share
it through samba.
1) So I put it in the fstab. It automounts correctly on boot, no problem:
UUID=XXX /usb-hdd ext4 defaults,nofail 0 0
2) I then share t
On 2019-08-10, Dennis Wicks wrote:
>
> If you have some suggestions on what info to gather then let
> me know. Bear in mind that during the boot process my system
> is pretty much unresponsive for the hour or so until the
> window manager is up and everything has settled down.
>
An hour or so.
David Wright wrote on 8/8/19 9:04 AM:
On Thu 08 Aug 2019 at 08:19:22 (-), Curt wrote:
On 2019-08-05, Dennis Wicks wrote:
So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
seemed to finish successfully, but "ls /wa1" indicated that
in fact it had not. Nothing mounted on wa1! Many oth
Curt wrote on 8/8/19 3:41 AM:
On 2019-08-08, Curt wrote:
On 2019-08-05, Dennis Wicks wrote:
So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
seemed to finish successfully, but "ls /wa1" indicated that
in fact it had not. Nothing mounted on wa1! Many other tests
told me the same thin
Curt wrote on 8/8/19 3:19 AM:
On 2019-08-05, Dennis Wicks wrote:
So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
seemed to finish successfully, but "ls /wa1" indicated that
in fact it had not. Nothing mounted on wa1! Many other tests
told me the same thing. "umount /wa1" said "not mo
Hi,
David Wright wrote:
> it appears that any subsequent mount commands have to
> agree explicitly with the earlier choice. Are there other, similar
> factors involved in the OP's case…
Ah yes.
I was similarly confused by my system's behavior on double mount
and the fact that i remember to have
On Fri, Aug 09, 2019 at 11:29:17AM -0500, David Wright wrote:
> Whether I like the ability to mount in this manner, I'm with Greg at the
> moment. Obviously I missed any discussion on the topic ~15 years ago,
> so I haven't seen any benefits spelled out. In any case, perhaps a
> warning in kern.log
Sorry to cause the thread to "wander", but some of us are trying to
replicate aspects of the OP's problem, which necessitates explaining
any differences in the results being obtained.
On Thu 08 Aug 2019 at 14:14:25 (-0400), Michael Stone wrote:
> On Thu, Aug 08, 2019 at 12:09:11PM -0500, David Wri
On Thu, Aug 08, 2019 at 12:09:11PM -0500, David Wright wrote:
On Thu 08 Aug 2019 at 10:56:46 (-0400), Michael Stone wrote:
On Thu, Aug 08, 2019 at 09:04:00AM -0500, David Wright wrote:
> wren 08:50:11 ~# lsblk -f | grep sda7
> ├─sda7 ext4swan07 4a4e352f-2180-4083-92b4-f46e4e01
On Thu, Aug 08, 2019 at 12:09:11PM -0500, David Wright wrote:
> But the 2-1 vote wasn't whether error messages were emitted, but
> whether the system should mount an already-mounted partition onto
> another mount point. I get error messages and the mount fails.
> Others get no error messages (thoug
On Thu 08 Aug 2019 at 10:56:46 (-0400), Michael Stone wrote:
> On Thu, Aug 08, 2019 at 09:04:00AM -0500, David Wright wrote:
> > wren 08:50:11 ~# lsblk -f | grep sda7
> > ├─sda7 ext4swan07 4a4e352f-2180-4083-92b4-f46e4e0104b4
> > /wrenbk
> > wren 08:50:26 ~# mkdir /wa1 /somethin
On Thu, Aug 08, 2019 at 09:04:00AM -0500, David Wright wrote:
wren 08:50:11 ~# lsblk -f | grep sda7
├─sda7 ext4swan07 4a4e352f-2180-4083-92b4-f46e4e0104b4
/wrenbk
wren 08:50:26 ~# mkdir /wa1 /somethingelse
wren 08:50:49 ~# mount /dev/sda7 /somethingelse
mount: /dev/sda7 is alr
On Thu 08 Aug 2019 at 08:19:22 (-), Curt wrote:
> On 2019-08-05, Dennis Wicks wrote:
> > So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
> > seemed to finish successfully, but "ls /wa1" indicated that
> > in fact it had not. Nothing mounted on wa1! Many other tests
> > told me the
On 2019-08-08, Michael Stone wrote:
> On Thu, Aug 08, 2019 at 11:52:41AM +0200, Thomas Schmitt wrote:
>>The central riddle is how mount(8) can fail to make the filesystem
>>available without visibly reporting an error.
>>A question about "mount -v" and its exit value is pending.
>>Maybe one should
On Thu, Aug 08, 2019 at 11:52:41AM +0200, Thomas Schmitt wrote:
The central riddle is how mount(8) can fail to make the filesystem
available without visibly reporting an error.
A question about "mount -v" and its exit value is pending.
Maybe one should also look at dmesg output after such a silen
On 2019-08-08, Thomas Schmitt wrote:
> Hi,
>
> The central riddle is how mount(8) can fail to make the filesystem
> available without visibly reporting an error.
Nothing to do with these swaps spaces (I took a gander at the /etc/fstab)?
/wa1/Swap5 ...
/wa2/Swap6 ...
"I can mou
Hi,
Curt wrote:
> Did you show your /etc/fstab file (cut and paste)? If so, I must've missed
> it.
See https://lists.debian.org/debian-user/2019/08/msg00295.html
where the attachments are kindly attached to the body text.
Results from "mount" without arguments or the contents of /etc/mtab
and /p
On 2019-08-08, Curt wrote:
> On 2019-08-05, Dennis Wicks wrote:
>>
>>
>> So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
>> seemed to finish successfully, but "ls /wa1" indicated that
>> in fact it had not. Nothing mounted on wa1! Many other tests
>> told me the same thing. "umount /w
On 2019-08-05, Dennis Wicks wrote:
>
>
> So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
> seemed to finish successfully, but "ls /wa1" indicated that
> in fact it had not. Nothing mounted on wa1! Many other tests
> told me the same thing. "umount /wa1" said "not mounted"!
Would this
Hi,
i wrote:
> >mount -v /dev/sdc /wa1
> >echo $?
Duh. "/dev/sdb2", not "/dev/sdc".
(Do as i mean, not as i write.)
Dennis Wicks wrote:
> I'll put a note in my fstab so the next time I boot I can find it if the
> mount fails again!
Did i miss the report about some miracle cure beyond t
On Wed 07 Aug 2019 at 12:44:39 (-0500), Dennis Wicks wrote:
> David Wright wrote on 8/6/19 1:48 PM:
> > On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
> > > Thomas Schmitt wrote on 8/6/19 10:30 AM:
> > > > Dennis Wicks wrote:
> > > > > I *cannot* mount *any* partition on /wa1
> > > > >
On Wed, Aug 07, 2019 at 12:44:39PM -0500, Dennis Wicks wrote:
> And the
> system does not object or give an error when you mount the same partition on
> two diff dirs anyway!
Sadly. And *very* surprisingly. You can only wish that it did.
Thomas Schmitt wrote on 8/6/19 1:58 PM:
Hi,
more ideas: exit value, verbous mode.
mount -v /dev/sdc /wa1
echo $?
A nominally successful mount command would yield 0 as "$?".
Maybe -v yields some extra insight.
Have a nice day :)
Thomas
Thanks, Thomas!
I'll put a note in my fstab so
David Wright wrote on 8/6/19 1:48 PM:
On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
Thomas Schmitt wrote on 8/6/19 10:30 AM:
Dennis Wicks wrote:
I *cannot* mount *any* partition on /wa1
but I *can* mount *any* partition on any other mount point.
So what do you get from these sh
Hi,
more ideas: exit value, verbous mode.
mount -v /dev/sdc /wa1
echo $?
A nominally successful mount command would yield 0 as "$?".
Maybe -v yields some extra insight.
Have a nice day :)
Thomas
On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
> Thomas Schmitt wrote on 8/6/19 10:30 AM:
> > Dennis Wicks wrote:
> > > I *cannot* mount *any* partition on /wa1
> > > but I *can* mount *any* partition on any other mount point.
> >
> > So what do you get from these shell commands ?
> I
On 7/08/19 5:51 AM, Dennis Wicks wrote:
> Richard Hector wrote on 8/6/19 12:42 PM:
>> On 7/08/19 5:31 AM, Dennis Wicks wrote:
>>> rhkra...@gmail.com wrote on 8/6/19 10:34 AM:
I didn't fully understand your fstab, but is there a typo -- wa11 vs.
wa1?
>>> No. My current config is;
>>>
>>>
Richard Hector wrote on 8/6/19 12:42 PM:
On 7/08/19 5:31 AM, Dennis Wicks wrote:
rhkra...@gmail.com wrote on 8/6/19 10:34 AM:
I didn't fully understand your fstab, but is there a typo -- wa11 vs.
wa1?
No. My current config is;
/wa1 -> wa11 ( soft link )
/wa11 ( <- /dev/sdb2 )
On 7/08/19 5:31 AM, Dennis Wicks wrote:
> rhkra...@gmail.com wrote on 8/6/19 10:34 AM:
>> I didn't fully understand your fstab, but is there a typo -- wa11 vs.
>> wa1?
> No. My current config is;
>
> /wa1 -> wa11 ( soft link )
> /wa11 ( <- /dev/sdb2 )
>
> with sdb2 mounted on /wa11 s
rhkra...@gmail.com wrote on 8/6/19 10:34 AM:
I didn't fully understand your fstab, but is there a typo -- wa11 vs. wa1?
No. My current config is;
/wa1 -> wa11 ( soft link )
/wa11( <- /dev/sdb2 )
with sdb2 mounted on /wa11 so I don't have to find and
change all the paths that I h
Felix Miata wrote on 8/6/19 10:33 AM:
Dennis Wicks composed on 2019-08-06 10:09 (UTC-0500):
I *cannot* mount *any* partition on /wa1
What is output from ls -ld /wa*/ ?
wix@dgwicks:/$ ls -ld /wa*/
drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa1/
drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa11/
Thomas Schmitt wrote on 8/6/19 10:30 AM:
Hi,
Dennis Wicks wrote:
I *cannot* mount *any* partition on /wa1
but I *can* mount *any* partition on any other mount point.
So what do you get from these shell commands ?
I am currently running with "ln -s /wa11 /wa1" so this isn't
the config I boote
I didn't fully understand your fstab, but is there a typo -- wa11 vs. wa1?
On Tuesday, August 06, 2019 11:09:32 AM Dennis Wicks wrote:
> Requested info attached:
>
> I *cannot* mount *any* partition on /wa1
> but I *can* mount *any* partition on any other mount point.
>
> Regards, and Thanks!
>
Dennis Wicks composed on 2019-08-06 10:09 (UTC-0500):
> I *cannot* mount *any* partition on /wa1
What is output from ls -ld /wa*/ ?
--
Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Hi,
Dennis Wicks wrote:
> I *cannot* mount *any* partition on /wa1
> but I *can* mount *any* partition on any other mount point.
So what do you get from these shell commands ?
ls -ld /wa1 /wa11
find /wa1
What happens if you create a new /wa1 ?
mv /wa1 /wa1_old
mkdir /wa1
mount /dev/
Requested info attached:
I *cannot* mount *any* partition on /wa1
but I *can* mount *any* partition on any other mount point.
Regards, and Thanks!
Dennis
Andrei POPESCU wrote on 8/6/19 1:06 AM:
On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
It seems that something in the mount process does
On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
>
> It seems that something in the mount process does not like "wa1" for a mount
> point. Anybody have similar recent problems?
Please show your fstab and the output of 'lsblk -f'.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
On Monday 05 September 2016 03:38:39 Anthony Baldwin wrote:
> I don't know what kind any of these USB ports are
Have a look at the port and/or the plug. White or black=USB2 and blue=USB3.
(We can safely ignore USB1). I have even come across USB2 not working in a
USB3 port, even though it shou
On Sonntag, 11. September 2016 11:43:17 PYT Tony Baldwin wrote:
> On 09/11/2016 08:59 AM, Eike Lantzsch wrote:
> > On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
> >> On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
> >>> On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
> On 09
On 09/11/2016 08:59 AM, Eike Lantzsch wrote:
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wro
On Sonntag, 11. September 2016 09:17:41 PYT Anthony Baldwin wrote:
> On 09/11/2016 08:54 AM, Eike Lantzsch wrote:
> > On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
> >> On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
> >>> On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
> On
On 09/11/2016 08:54 AM, Eike Lantzsch wrote:
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wro
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
> On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
> > On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
> >> On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
> >>> On 09/10/2016 03:28 PM, Tony Baldwin wrote:
> On 09/10/2016 03:07 PM,
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote:
> On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
> > On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
> >> On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
> >>> On 09/10/2016 03:28 PM, Tony Baldwin wrote:
> On 09/10/2016 03:07 PM,
On 09/11/2016 06:37 AM, Anthony Baldwin wrote:
On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wrote:
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit
On 09/10/2016 07:57 PM, Anthony Baldwin wrote:
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wrote:
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
I apologize, but, I've never quite figured o
On 09/10/2016 03:34 PM, Anthony Baldwin wrote:
On 09/10/2016 03:28 PM, Tony Baldwin wrote:
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
I apologize, but, I've never quite figured out what to do with dmesg,
or what to look for in
On 09/10/2016 03:28 PM, Tony Baldwin wrote:
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
I apologize, but, I've never quite figured out what to do with dmesg,
or what to look for in its output, etc..
it really just confuses me...
I
On 09/10/2016 03:07 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
I apologize, but, I've never quite figured out what to do with dmesg,
or what to look for in its output, etc..
it really just confuses me...
I saw this: 15.690807] EXT3-fs (sda1): warning
Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit :
> I apologize, but, I've never quite figured out what to do with dmesg,
> or what to look for in its output, etc..
> it really just confuses me...
> I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, running
> e2fsck is
On 09/10/2016 02:26 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Tony Baldwin a écrit :
The output of dmesg will tell you more.
perhaps some of this will be useful?
# fdisk -l
It is a little. But much less than the source of information I mentioned in
my first mail and tha
Le quintidi 25 fructidor, an CCXXIV, Tony Baldwin a écrit :
> >The output of dmesg will tell you more.
> perhaps some of this will be useful?
> # fdisk -l
It is a little. But much less than the source of information I mentioned in
my first mail and that you utterly ignored.
> /dev/sdb2 * 4
On 09/10/2016 01:53 PM, Nicolas George wrote:
Le quintidi 25 fructidor, an CCXXIV, Tony Baldwin a écrit :
ls: cannot access winhome: Input/output error
ls: cannot access myown: Permission denied
ls: cannot access win7: Input/output error
If you are lucky, fsck (or the windows equivalent) will
On 09/10/2016 01:45 PM, Tony Baldwin wrote:
Suddenly I can't mount my 2nd hdd, it's been fine, but after a reboot
today, I get I/O errors trying to mount the two partitions on it with
this script:
#!/bin/bash
if [ $(whoami) != "root" ]; then
echo "must be root, bitch"
exit
else
mou
Le quintidi 25 fructidor, an CCXXIV, Tony Baldwin a écrit :
> ls: cannot access winhome: Input/output error
> ls: cannot access myown: Permission denied
> ls: cannot access win7: Input/output error
If you are lucky, fsck (or the windows equivalent) will fix this.
If you are less lucky, you need t
Ivan Petrov writes:
> 06.09.2016 22:19, Joe Pfeiffer пишет:
>> Curt Howland writes:
>>
>>> I've never been able to mount any MTP phone to Linux. Different
>>> phones, different Android versions, different Linux installations,
>>> nada.
>>
>> I've only been able to do it using jmtpfs (I don't hav
06.09.2016 22:19, Joe Pfeiffer пишет:
Curt Howland writes:
I've never been able to mount any MTP phone to Linux. Different
phones, different Android versions, different Linux installations,
nada.
I've only been able to do it using jmtpfs (I don't have it set up to
automount using that).
W
On Tuesday 06 September 2016 09:19:07 Joe Pfeiffer wrote:
> Most commonly when I've seen a device fail to enumerate, the problem has
> been the cable (I know, you've already said you've tried multiple cables).
I second that opinion.
MTP only works with a 24/28 gauge USB cable on my daughter's And
Tony Baldwin writes:
> On 09/04/2016 09:22 PM, Carl Fink wrote:
>> On 09/04/2016 09:13 PM, Tony Baldwin wrote:
>>> I'm at a loss, friends:
>>> I have a phone (Motorola Droid Turbo), which functions as an MTP
>>> device, and auto-mounts on Win7, but not on Debian 8.
>>> AFAIK, I have all the requi
Curt Howland writes:
> I've never been able to mount any MTP phone to Linux. Different
> phones, different Android versions, different Linux installations,
> nada.
I've only been able to do it using jmtpfs (I don't have it set up to
automount using that).
--
"Erwin, have you seen the cat?" --
On Mon, 5 Sep 2016 17:09:38 +0200
Nicolas George wrote:
> Le decadi 20 fructidor, an CCXXIV, Curt Howland a écrit :
> > I've never been able to mount any MTP phone to Linux. Different
> > phones, different Android versions, different Linux installations,
> > nada.
>
> I have. With FUSE and gvf
Le decadi 20 fructidor, an CCXXIV, Tony Baldwin a écrit :
> Something has changed since yesterday (IN which I installeed jmtpfs).
> Now when I do ls usb, I see this:
> Bus 005 Device 012: ID 22b8:2ea4 Motorola PCS
> I'm also seeing possibly relevant (I don't know) stuff in dmesg, such as
> this:
>
On 09/05/2016 11:09 AM, Nicolas George wrote:
Le decadi 20 fructidor, an CCXXIV, Curt Howland a écrit :
I've never been able to mount any MTP phone to Linux. Different
phones, different Android versions, different Linux installations,
nada.
I have. With FUSE and gvfs, something like (the compu
Le decadi 20 fructidor, an CCXXIV, Curt Howland a écrit :
> I've never been able to mount any MTP phone to Linux. Different
> phones, different Android versions, different Linux installations,
> nada.
I have. With FUSE and gvfs, something like (the computer where I did it and
kept notes is curre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've never been able to mount any MTP phone to Linux. Different
phones, different Android versions, different Linux installations,
nada.
- --
You may my glories and my state dispose,
But not my griefs; still am I king of those.
--- William Sha
* On 2016 04 Sep 22:53 -0500, Neal P. Murphy wrote:
> Oh, wait. (Grasping at a straw...) Do you need pkg usb-modeswitch?
> There are some USB NADs (Network Access Device) for which udev uses
> usb-modeswitch to switch from the default mode that presents the
> Windows drivers in a filesystem to a di
On 09/05/2016 06:50 AM, Dan Purgert wrote:
Tony Baldwin wrote:
I'm at a loss, friends:
I have a phone (Motorola Droid Turbo), which functions as an MTP device,
and auto-mounts on Win7, but not on Debian 8.
[snip]
I don't know what else to do to try and diagnose or resolve the matter.
Anyone?
I
Tony Baldwin wrote:
> I'm at a loss, friends:
> I have a phone (Motorola Droid Turbo), which functions as an MTP device,
> and auto-mounts on Win7, but not on Debian 8.
> [snip]
> I don't know what else to do to try and diagnose or resolve the matter.
> Anyone?
Is the phone set to "USB for Charge
1 - 100 of 685 matches
Mail list logo
